Sonarr version (exact version): 220.127.116.1138
OS: Windows 10 Pro Version 1909
Debug logs: https://drive.google.com/open?id=1F_8EOFSCuKvIuQCpB3Om3meatwDkxwRH
Description of issue:
I’m having a strange permissions issue when sonarr is switched on (not sure if it is also to do with the Windows 10 v1909 update) where my root folder stops having permission to access the share network-wide (meaning on other PCs and even on the local server via shared path (my file server is separated from Sonarr)). Any ideas? As though the limit of the amount of users has been maxed out? The SMB share actually lives on a Windows Server 2012 R2 server, as i have a Hyper-V setup.
Sonarr then says after a minute or two running, that it cannot find that same root folder.
Then, checking mapped network share, I have no permission to access the folder. It is isolated only to the shared folder that Sonarr needs access to. Other services have their own, accessible shares (Radarr, Lidarr) respectfully.
I have leave Sonarr shut down until it is rectified, as I can access the shared folder while Sonarr is off (so that media services can still access the share in the interim).
I have Sonarr running as a service with a specified user account as per the shared folder recommendations in the Wiki…
The SMB share permissions are set to everyone with full rights and the running as a windows service account is seeing the UNC paths correctly in the Sonarr app. and has been transferring fine previously…
I have mentioned my issue in the Discord Sonarr support channel.
I have updated my Intel l350 LAN drivers from version 21.x.x.x to version 18.104.22.168 as per a suggestion about driver relation on the Discord Support channel.
It seems to occur after some import(s)
As soon as an import completes.
Also corrupts files, terminated mid-transfer by this issue.
I still prefer to use the app as a service method, as it allows for a headless environment.