Issue with the UiAutomation library on PROD

Help Assistant
,
1

Hi Team,

currently i am facing an issue i.e.

"Could not load file or assembly ‘UiPath.UiAutomation.Activities, Version=24.11.1.0, Culture=neutral, PublicKeyToken=null’. The system cannot find the file specified.

at Fissure_sealants_Bot_1.Main.GetImplementation()
at System.Activities.Activity.OnInternalCacheMetadata(Boolean createEmptyBindings)
at System.Activities.Activity.InternalCacheMetadata(Boolean createEmptyBindings, IList1& validationErrors) at System.Activities.ActivityUtilities.ProcessActivity(ChildActivity childActivity, ChildActivity& nextActivity, Stack1& activitiesRemaining, ActivityCallStack parentChain, IList1& validationErrors, ProcessActivityTreeOptions options, ProcessActivityCallback callback) at System.Activities.ActivityUtilities.ProcessActivityTreeCore(ChildActivity currentActivity, ActivityCallStack parentChain, ProcessActivityTreeOptions options, ProcessActivityCallback callback, IList1& validationErrors)
at System.Activities.ActivityUtilities.CacheRootMetadata(Activity activity, LocationReferenceEnvironment hostEnvironment, ProcessActivityTreeOptions options, ProcessActivityCallback callback, IList`1& validationErrors)
at System.Activities.Hosting.WorkflowInstance.ValidateWorkflow(WorkflowInstanceExtensionManager extensionManager)
at System.Activities.Hosting.WorkflowInstance.RegisterExtensionManager(WorkflowInstanceExtensionManager extensionManager)
at System.Activities.WorkflowApplication.EnsureInitialized()
at System.Activities.WorkflowApplication.Enqueue(InstanceOperation operation, Boolean push)
at System.Activities.WorkflowApplication.SimpleOperationAsyncResult.Run(TimeSpan timeout)
at System.Activities.WorkflowApplication.BeginRun(AsyncCallback callback, Object state)
at UiPath.Executor.RobotRunner.RunWorkflow() in D:\a\1\s\Robot\UiPath.Executor.Core\RobotRunner.cs:line 702 "

I have all the folder version present in UiPath.uiautomation.activities
but still facing this issue other Bot automation are working but i am facing this issue with this bot only.

I have developed this on another system and deployed it to prod system and this is creating issue in PROD only and on Dev machine project is working fine.

Forum Engagement Daily Reports
2

Hi @Akarshan_Sonkar

I think this is mainly a version mismatch between Dev and Prod.
Even if the package folder exists, the PROD robot is probably running a different UiAutomation/Robot version.I would make sure Dev and Prod have the same Robot version, clear NuGet cache on PROD, restore packages, and redeploy.

3

Hi @Akarshan_Sonkar

because when the PROD machine does not have the same UiPath.UiAutomation.Activities version that your project was published with. Even if the folder exists, the exact version (24.11.1.0) is not loaded by the Robot.

Install or update the UiPath.UIAutomation.Activities package in the PROD environment to the same version used during development, then republish. Also check that your project.json file contains the correct dependency and that no higher/lower version conflict exists. This usually happens when the project was developed on another system with newer dependencies not available on the PROD machine.

If helpful, mark as solution. Happy automation with UiPath

4

I have noticed one more thing that whenever i run bot through UiPath assistant on both DEV and PROD machine i am facing the same issue but no issue with the Studio run.

5

I have verified the project.json which was deployed on PROD machine
as shown in the screenshot
Path : C:\Users\admin.nuget\packages{{BotName}}{{Version}}\content
but still facing the same issue.

image
image366×122 61.5 KB

6

HI @Akarshan_Sonkar ,

Since the process runs fine in Studio but fails via Assistant, this indicates a possible Robot runtime dependency loading issue. Studio uses design-time packages, while Assistant uses Robot runtime packages.

In similar cases, clearing the local NuGet cache, reinstalling the exact UiPath.UIAutomation.Activities version, restarting the Robot service, and recreating the process in Orchestrator resolved the issue.

It may be related to runtime dependency mismatch rather than project.json itself.

If Solution works for you , Please mark as Solution
Happy Automation with UiPath.

Thanks