windows sabnzbd cannot create final folder on synology nas

[sholnay]

Hi everyone

Version: 0.7.3
OS: Windows 8.1
Install-type: Windows Installer
Skin: Plush
Firewall Software: Windows firewall
Are you using IPV6? My ISP uses ipv6, though my issue is all local and my home network uses IPV4
Is the issue reproducible? Yes

I have a windows computer (windows 8.1) which runs sabnzbd (0.7.3).

I have configured sabnzbd to run as a service (as per the following instructions: http://wiki.sabnzbd.org/sabnzbd-as-a-windows-service).

I have setup sabnzbd to save completed files to my synology nas (DS414). Incomplete downloads are stored locally on the windows computer first, then transferred upon completion to the NAS location. My categories are setup using network paths, not drives (ie: \\server\share\location\)

When a file is completed on sabnzbd, the process fails when transferring to my NAS with the following error:
Post Processing Failed for "media-file" (Cannot create final folder \\server\media\movies\"media-file")

"media" is a shared directory on the nas, I have given admin and one other user full access to this directory and all sub directories (via the synology nas control panel - linux based).

On my windows computer, I have set my sabnzbd service to run as my local admin user, and I have setup my local admin user on my windows machine to connect to my synology nas with appropriate credentials using Credential Manager. When browsing my synology server via file explorer on the local admin account on the windows machine which is running sabnzbd, I have no problem browsing, creating files, deleting files.

There has to be some sort of permission that I am missing somewhere? I can't figure it out for the life of me. Any thoughts or suggestions or a nudge in the right direction?

There are some notes at the bottom of the sabnzbd service wiki page:

• - The SABHelper Service must run as "Local System" or any account that has administrative privileges.

• This is set to run as local service.

• - By default the service runs as "Local System". This allows full access to the internal harddisk, but not to network shares.

• - If you need network shares, you should tell the Service Manager to use an appropriate user account.

• I have set the sabnzbd service to run as my local windows user - when I have logged in to my windows user via windows, I have set the credentials for the network share appropriately and am able to browse the network location and read/write/execute files from it.

• - When using network shares, you must use network (UNC) paths ("\\server\share") instead of drive letters ("p:\")

.

• I have done this.

I feel like I have done all of the above suggestions but still feel I might have done something wrong? I can provide screenshots and more info as necessary. Thanks for any and all help!

[shypike]

First of all, we're now at release 0.7.20, so please upgrade first.
Make sure that the username/password of the user you set for the service
matches the username/password you set for that share on the NAS.

[sholnay]

Thanks for the reply, I really appreciate it!

I have updated sabnzbd and the current running version is now 0.7.20

There are two services, the sabhelper and the sabnzbd service.

sabhelper is running as "Local System" as per instructions under the wiki page linked in my original post.
sabnzbd service is running as a specific user: USER. This user is a windows user under the windows machine. I have verified that the password is correct. I have verified that the windows user has access to the NAS under the same login credentials as the windows user (on the NAS, I created a new user that matches, username and password, the same windows user).

I can't think of what else to check - I have every user matching, every password matching.

[shypike]

Can you do a test?
Set the final folder to a local folder.
Then create a little script that examines the accessibility of
the network drive. Just write output to the console.
Run that script as an end-of-job script and download something.

[sholnay]

This is a great suggestion, however, I haven't written scripts in a long while so I wasn't exactly sure the best way to "examine the accessibility" of the network drive. I tried a few things that came to mind.

So, I thought about just creating a directory from the script: mkdir \\server\share\folder\newfolder

When I'm logged in to my windows machine as USER and I run the above (either as a bat file or from the command prompt), the folder is created.
When I set this script to run after dl on sabnzbd, I get the following script output:

C:\Program Files (x86)\SABnzbd>mkdir \\server\share\folder\newfolder
The parameter is incorrect.

I also have a network drive mapped "S:" to \\server\share and I tried the same thing in the script (it works fine when run in cmd prompt or via bat file): mkdir S:\folder\newfolder with the following output:

C:\Program Files (x86)\SABnzbd>mkdir S:\folder\newfolder
The system cannot find the drive specified.

I also tried mkdir "\\server\share\folder\newfolder" (using quotes) and got the following:
C:\Program Files (x86)\SABnzbd>mkdir "\\server\share\folder\newfolder"
The network path was not found.

I have tried multiple combinations of service log-on users. I have tried running both sabhelper and sabnzbd as "Local System" and I have tried running both as USER, and I have tried each combination of those two. One note: when I run sabnzbd as LocalSystem, my free space shows as 0GB, when running as USER, it shows the correct free space of my primary server (the server defined in the default config).

The last bit of tinkering I did above got me thinking. Let me expand on my setup:
I have two NAS servers. One is a Windows home server and one is the Synology (linux). I plan to retire the windows home server and migrate everything to the synology. This has all be part of that process. The current windows home server works fine with sabnzbd.

A curious thing I'm seeing: when I am in the sabnzbd> Config> Folders screen, and I update the "Completed Download Folder" parameter, I am able to type my windows home server network path and see it dynamically list out the server contents. So, when I type in "\\WHS\downloads\" sabnzbd will pop up suggested locations below with \\WHS\downloads\completed, \\WHS\downloads\incomplete.. etc.
When I do the same thing with my synology nas, no such suggested paths are offered - leaving me to think this is related to the issue - sabnzbd just cant seem to see the network shares but I can't for the life of me figure out how to get it to see them! Gah.

Sorry for the long reply, again, thank you in advance for reading and helping!

[shypike]

Drive letters won't work for a service.
Each (normal) user session will have its own drive mappings.
A service will not get a drive letter, unless it maps one by itself, which SABnzbd doesn't do
(there is no need).
Given that SABnzbd can see shares on the WHS server, but not on the NAS,
strongly suggests there are access rights problems on the NAS
which have nothing to do with SABnzbd.

First try running SABnzbd as a normal user program instead of a service
and access the NAS through the UNS notation, not a drive letter.

[sholnay]

Ok a couple things that I have figured out.

I stopped the sabnzbd services and I ran the exe directly. I previously had this set to run as administrator and found that that was causing access issues to the nas - so I ran it as my local USER and it connects without issue to the NAS (and creates/saves folders/files without problem).

I double checked that the sabnzbd system process and helper are not running as administrator - it still cannot "talk" to the NAS as a system process. Very strange. I might resort to just running sabnzbd directly as a local user rather than running the process.

edit: just to note - I only use UNC for sabnzbd paths. I was only using shared drive mapping letters above for testing purposes to see if it might have yielded any more information.