Seeing an issue where the excel activity is failing to save a file to a network share due to “Someone else is working in <servername\Folder\File> right now. Please try again later”. This appears to be impacting only intermittently and root cause has not been identified. I have found the following potential work around and I am implementing some testing to see if this resolves the issue.
No we confirmed the file was and is not locked while attempting to interact with it. The registry change has allowed us to continue with the Excel activities within UiPath and this appears to be something related to how the activities are interacting with files on a network location.
This has resolved our issue, however, it reduces the capabilities of working with network share files. Open to anyone that is experiencing this issue and found RCA.
Can you explain in what way it reduces capabilities?
We also had the same issue and implemented the work around and that seems to have resolved it, still working on RCA, considering nothing has changed in our environment I’m leaning towards a Microsoft /Security patch that was introduced.
While the effect of the registry key has not been publicly documented by Microsoft, the “Robustified UNC” feature affects the security mechanisms used when opening a file from or saving a file to a network share in Office applications.
Disabling the “Robustified UNC” feature could also solve issues such as documents not opening when double clicked from a network share (while Word does open) or hangs or slow performance when opening/saving files that are located on a network share.