ERROR: Internal : Could not find a part of the path '...\AppData\Local\Temp\...'

[NicolasToniolo499]

Hello everyone,

I'm experiencing a recurring issue that affects only 1 out of the 4 machines we use

Initially, it only happened on Saturdays while a specific automation was running. At first, we disabled that automation, but the issue later started occurring on a different day with another automation, and now it's happening every day.

The problem always occurs while a bot is running, usually in the middle of the process. I checked whether the machine was being rebooted, but it hasn't been restarted since July, while this issue started around mid-August.

This appears to be the same issue discussed in the following thread:

RE: Internal error: could not find a part of the p... - SS&C Blue Prism Community

However, none of the proposed solutions resolved the problem in our environment.

Has anyone experienced something similar or identified the root cause? Any insights, recommendations, or troubleshooting steps would be greatly appreciated.

Thanks in advance!

[hossein.azimi]

Hello Nicolas

Thank you for contacting Blue prism community.

Since the issue affects only one of the four machines and occurs across different automations, it appears more likely to be machine-specific than process-specific.

The error indicates that Blue Prism attempted to access a temporary path under:

C:\Users\Blue.Prism\AppData\Local\Temp

but the folder or file no longer existed. I recommend checking whether antivirus/EDR, Windows Storage Sense, a scheduled cleanup task, or profile-management software is deleting temporary files while the bot is running.

It would also be useful to compare the affected machine with a working machine, particularly:

●　TEMP and TMP environment variables
●　Permissions on the user’s Temp folder
●　Available disk space
●　Scheduled maintenance or cleanup tasks
●　Antivirus/EDR quarantine and activity logs
●　Windows User Profile Service events

Microsoft Process Monitor can also help identify which process deletes or accesses the missing path. Filter it for the affected Temp directory and PATH NOT FOUND or NAME NOT FOUND results.

As the machine has not been restarted for a long period, a controlled reboot may temporarily restore the Temp structure, but I would collect the relevant logs first because rebooting alone may hide the original cause.

Regards
Hossein Azimi (APJ Team)