Do we need to restart Octopus service to make network folder permission take effect?


We tested deploying packages to staging location (a network shared folder) via Octopus, and it worked great.

Now we try to deploy to prod location, which is also a network shared folder. We granted the user account that runs the deployment job the “modify” permission to the new location.

However, we keep receiving access denied error when deploying to the new location:

System.UnauthorizedAccessException: (5) Access is denied: [\?\UNC\team\env\Builds]

Do we need to restart the Octopus service to make the network folder permission take effect?



Hi Ge,

Thanks for getting in touch!

I would indeed recommend restarting the Octopus server service so that it will apply the new permissions structure. We have seen cases where the underlying OS will need to be restarted for permissions to take affect, however hopefully this won’t be the case in this scenario.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.