Sonarr version (exact version): 126.96.36.1998
Mono version (if Sonarr is not running on Windows):
(Make sure debug logging is enabled in settings and post the full log to hastebin/pastebin/dropbox/google drive or something similar, do not post them directly here. Post in .txt not .doc, .rtf or some other formatted document)
Description of issue:
In another thread, I discovered a feature was missing, so I didn’t have the latest v3 installed. I saw the app THOUGHT it had the latest version, but manually checking, sure enough, v3.0.0 is older than v3.0.1 so I downloaded v188.8.131.528, installed. The app proceeded to ‘upgrade’ back to 3.0.0…348!
The branch is set to phantom (not listed in the wiki) so I tried master, but that also upgrades to v 3…348. What should branch be set to and/or what should I do to fix this?
I can bet you there are others with this issue if there is a logic error.
I reported this before, and perhaps this is a problem that is only related to the fact that I am stuck in never-land.
upon upgrading, I choose “run as a service” which is what I need since the data files are stored on another server (host VM server.) Upon installation completion, I see this error shown in the app:
This is an erroneous error. the ACTUAL problem is the app does not have ACCESS to the folders. I implore the development team to add an error trap that checks for access denied on any/all file writes/ reads, and depending on where these are found, and how the system is set up you could REALLY help users debug their systems.
The Logon account gets set back to local service account (see screenshot) from a user or computer account manually added which is what you do when using NAS storage.)
In the past, I had BOTH of these problems (NTFS permissions issues, service account was changed.) Adding some error checking logic would have saved me months of digging through files /errors to know the problem was simple NTFS and share permission errors.
The root cause of the NTFS permissions were I had some directories that I moved manually in windows that had copied NTFS permissions over as opposed to inheriting permissions which is normally what happens in windows. Therefore, the service account I created did not have access to the folder, and this caused SOME TV series to not be able to be updated or change the file name structure for these folders that the system could not access. Dispite my blond moments lately (doah!) I have deep knowledge of windows 10 (previous windows Active Directory Architect) and with home edition, to set up a service account for NAS storage is quite complicated ( see https://social.technet.microsoft.com/Forums/en-US/e06a5a26-7b25-467f-acc6-09c215f8071f/windows-10-how-to-create-local-service-accounts-for-iis-sql-btsync-and-other-services?forum=win10itprosecurity to get an idea of what is needed to get this working )
In any case, I digress, but my real #2 issue here is that the install should NOT touch the service account, if configured, when upgrading.