Unexpected Termination (0xC0000005) with SAP after migrating to Windows compatibility

Help Robot
1

Hello,

I’m using UiPath Studio 24.10.9, and I have recently upgraded my machine to Windows 11 and migrated projects from Windows Legacy to Windows compatibility.
After the migration, I’m encountering an issue while running a process that interacts with SAP. The job suddenly stops and throws the following error:

=> The child process was terminated unexpectedly with exit code 0xC0000005.

Upon checking the Windows Event Log, I found the following error related to the crash:
=> UiPath.Executor 24.10.9.0
Duplicate assembly: C:\Users\Administrator.nuget\packages\UiPath.mail.activities\1.18.2\lib\net6.0-windows7.0\Office.dll

Here are the versions of the packages I’m using:
UiPath.Excel.Activities: 2.16.2
UiPath.Mail.Activities: 1.18.2
UiPath.System.Activities: 22.4.5
UiPath.UIAutomation.Activities: 23.10.11
UiPath.WebAPI.Activities: 1.16.2

Can you help me understand the cause of this issue, and how I can resolve it?

Thank you!

2

@heyjinp,

Make sure you are upgrading the dependency packages to latest possible version. Update and try.

3

@heyjinp

Try to remove the .nuget folder and let it get created again ..once you run the process it automatically gets created so please try the same

cheers

4

Thank you.

Actually, I found the information about dependency versions while searching through the forum, and after updating to the latest applicable versions, the process now works fine.

However, what I’m still curious about is that the issue occurred only on one specific robot, while other robots had no problems running the same workflow — even before the update.

I’m trying to figure out what could cause this kind of behavior. Could it be due to something specific to that machine, such as local cache, user profile, or environment?

Any suggestions would be appreciated.

5

Ah, thank you!
I’ll give that a try and see if it makes a difference.

Cheers!

1 Like
6

Glad to hear that @heyjinp,

0xC0000005 is a critical access violation error , which typically means the process tried to access memory it shouldn’t have. This is a Windows-level exception and can be caused by several issues like incompatible packages, .Net versions installed on the machine and many more.

1 Like