19-09-19 07:02 AM
when using the Get User Name/Get Machine name function in the Utility - Environment VBO, sometime we will get the captioned error, after reboot, the issue resovled, any one know the root cause and how to solve it permanently?
24-09-19 02:23 AM
24-09-19 06:30 AM
10-08-24 09:36 PM
Hi YunHaoCao, were you able to solve this? We are seeing it after migrating to an AWS architecture. The dlls seem to be part of an object or process creation in the temp folder and are expected to exist and then are auto cleaned by blue prism. Happens at random and the processes tend to rerun fine.
Example:
Could not load file or assembly 'file:///C:\Users\<user>\AppData\Local\Temp\1\<random>\<random>.dll' or one of its dependencies. The system cannot find the file specified.
3 weeks ago - last edited 3 weeks ago
Hello,
This could be related to an issue we just solved.
Please check your anti-virus software. We solved this issue after we found that our Sophos Antivirus was stealthily blocking access to the AppData\Local\Temp folder. Below is a screen shot from our environment. Somewhere along the way, Sophos rules may have been updated causing it to treat any write operations to \temp as a malicious threat. Worst part about this is that there were no warnings or popups warning us about the threat. If you have a different AV software, then you may want to ask your security team to add Blue Prism as an exception to the rules so that you don't get cut off from the AppData\Local\Temp folder.
Also to note: This is a situation with VBOs that contain the code stage. That's why it would appear to work when running once process (because it maybe using a VBO with no code stage), when you have errors with other processes at the same time!
I hope this is truly the situation on your end. Check your Antivirus/security software first before embarking on needless testing. We spent nearly three days on it, and no fixes in the code seemed to help. There is most likely nothing wrong with Blue Prism or the VBOs.