I am receiving an error saying that the directory has no write permissions. I have published to this directory plenty of times in the past. I have also ensured that my user has full access to the directory and that the directory is not read-only. Does anybody have any idea why this might have happened randomly after working for a long time? Thanks
My first check would be is to validate if the assumption of ‘the user has permissions’ is correct. Do a crosscheck, can you manually (so not publishing) able to access the location with write access? Can you create a test.txt file in that location?
Verify directory NTFS permissions and ensure user has full control. Clear %localappdata%\UiPath\.nuget cache and restart Studio. If using a network/shared drive, remap or switch to a local folder with write permissions.
Try setting the custom url to desktop file path or some folder path have read write access.
Where do I find this cache folder? I am using a network drive, I would prefer not to move it but I can if I need to.
Press Win + R, type %localappdata%\UiPath\.nuget, and hit Enter to open the cache folder.
Sorry for the delay. I tried this but there is .nuget folder at this path. I have hidden items selected, but I still do not see it. There is however a .cache folder…should I delete that? Thanks
This usually happens if the publish folder is kind of locked by another process (e.g. antivirus, or even Studio itself).
As the other suggestions you could try:
- Make sure no other process (OneDrive, antivirus scan, etc.) is holding the folder.
- Try clearing the temp files in
%localappdata%\UiPath\.tmp. - If nothing works, change the publish location once and then switch back.
I am able to create a test.txt file in that location. I am currently using a temporary UiPath license, would that have anything to do with this issue?
I am using a network share drive. It seems as though I am unable to save anywhere within the network drive.
I don’t think another process is holding the folder and I do not see a .tmp folder in that location. I published to my Desktop once, but I still cannot publish to the desired network share location.
I am currently using a temporary UiPath license, would that have anything to do with this error?
The license is not involved in this error/behavior.
You should use local paths where you have full control (Read, Write, Execute) and it is not automatically backup by third-party tools such as OneDrive.
According to this, it seems like you don’t have required permissions to the network drive.
Could you please confirm that you are trying to publish on network drive using the same account from where you tried to manually create a file on network drive?
Also, out of curiosity, I would like to ask why are you choosing to publish a package on a network drive instead of 1) orchestrator or 2) local folder?
Thanks for the clarification. I tried to publish to my Desktop but it is automatically backed up by OneDrive and I had issues when doing so.
I am using the same account to publish on the network drive as I was when I manually created a test file and saved to the network drive. I have never run into this issue before.
The network drive setup was used before me because the libraries being published need to be accessed by multiple users, so that multiple people can run the processes. We currently do not have an orchestrator instance set up.
I tried to publish to my Desktop but it did not work as expected. It could be because my Desktop is automatically backed up by OneDrive, or because I incorrectly published
Hi @jpreziuso
Thanks for sharing!
Regarding this, have you guys considered using Git repository for same? Using git would also help avoid network drive related issues plus would not create a large amount of libraries on network drive.
For this, can you please select location like C:\users\your username here\create any folder in there
It should work.
For instance, try creating a new folder directly in the root of the C: drive and attempt to publish your content there.
To check whether OneDrive is automatically synching up files from that location, create a test file inside the new folder. Then, open OneDrive and see if the file appears. If it does, OneDrive is still synching that location, which may be causing the issue. In that case, you’ll need to either adjust OneDrive settings to exclude that folder from synch or choose a different location that isn’t being monitored by OneDrive.