robot
2024.10
true
Admin Guide
Last updated 21 de oct. de 2024

Package troubleshooting

Los paquetes publicados desde Studio no son visibles en UiPath Assistant

Descripción

Los paquetes publicados desde Studio no son visibles en UiPath Assistant.

Posible problema

The issue occurs when you use a mapped network drive for your packages. The mapped network drive is available to the user that created it, whereas the Robot Service operates on a system-wide level.

Exigencia de la verificación de la firma de paquetes

Descripción

When upgrading to a newer version from an older one, some automations may fail to execute, especially when package signature verification is enforced.

Posible problema

The packages folder holds both signed and unsigned versions of activity packages. When executing an automation, the Robot installs the lowest applicable version of that activity package, which may be the unsigned version. If package signature verification is enforced, then the automation execution fails. Otherwise, it executes as expected.

Soluciones

  • Asegúrate de que todos los paquetes usados en tus proyectos de automatización estén firmados.
  • Modify your automations so that they request the latest package version upon execution.

Los paquetes NuGet no son accesibles tras la migración

Descripción

Once the migration of a Robot from Service Mode to UserMode is complete, the XML files within the NuGet packages become inaccessible. Additionaly, the following error message is displayed: "Access to path C:\Users\john.doe\.nuget\packages\HelloWorld\1.0.0\lib\net45\Main.xaml is denied".

Posible problema

When the Robot operates in Service Mode, the Local System user, under which the robot service runs, downloads and installs packages in a specific folder. After switching to User Mode, the current user cannot access the NuGet packages in that folder anymore.

Solución 1

Deleting packages from the original folder allows the Robot to reinstall them in a folder the current user can access, enabling the Robot Service to access the packages as well.

Solución 2

While converting from Service Mode to User Mode, you can modify the location of the package folder. This allows the Robot to rebuild the directory and use it for future downloads.

El robot no puede descargar el paquete

Descripción

El robot no puede descargar el paquete porque falta el archivo .nupkg correspondiente al proyecto.

Posible problema

The package folder might already contain both:

  • a version of the package with the corresponding .nupkg project file, and
  • aversion without the .nupkg project file.

Solución

Remove the previously installed packages from the %UserProfile%.nuget\Packages folder and download them again.

¿Te ha resultado útil esta página?

Obtén la ayuda que necesitas
RPA para el aprendizaje - Cursos de automatización
Foro de la comunidad UiPath
Uipath Logo White
Confianza y seguridad
© 2005-2024 UiPath. Todos los derechos reservados.