SABnzbd Forums

I have one 'special' category which only serves to unpack any downloads belonging to that category onto another drive, i.e. the folder for this category has an absolute path (e.g. "W:\") - thus no subdirectory under the default download directory...

this worked pretty much perfect in my previous version(s) but stopped working in 0.6.15; for any downloads in that category I now got the new error that the download-folder <name> couldn't be created - which is BS, there's nothing special about that drive, I can create any directory I want on that drive via explorer; this error even persists, when I started sabnzbd as admin...

please fix asap - I meanwhile go back to the latest version where this still worked (couldn't tell what version that was, gotta try ...)

<edit>
log says:

2012-03-01 00:05:43,374::INFO::[postproc:537] Par2 check finished on <name>

2012-03-01 00:05:43,375::INFO::[misc:722] Creating directories: W:\<name>

2012-03-01 00:05:43,375::ERROR::[misc:724] Erstellen von W:\<name> fehlgeschlagen

2012-03-01 00:05:43,375::ERROR::[postproc:453] Nachbearbeitung von <name> fehlgeschlagen (Konnte Download-Ordner W:\<name> nicht anlegen)

<edit2>
if that matters: "W:\" is a mapped network-drive (on my WDTVLiveHub); did work flawless on previous version(s)
Host is Win 7 Ultimate 64bit

Please let us know which version does work.
It will help clearing things up.

0.6.15 must have done something very nasty during installation - 'cause now I can't get this working with any older version at all (and I'm not going to reinstall windows to test this...)
- this also is the case when I intall the other version in a fresh/new directory

odd thing is: e.g. on a cmdline, I don't have any issues with drive "W:\" - e.g. I can do "mkdir W:\Test" without any problems; I too can e.g. extract the archives from the incomplete folder to W:\ via Explorer - only the scripting behind sabnzbd all of the sudden refuses W:\ now... :-(

what can I do to debug this further? - any verbose logging-options for sabnzbd available??

<edit>
maybe a hint to find what's causing this:
when I try to put the directory for all completed downloads on drive W:, I get following error (which I also get trying to access "W:" via its UNC name):

Wrong Parameter
Cannot create complete_dir folder W:\UseNet

logfile (as of sabnzbd 0.6.1) reads:

2012-03-01 14:30:19,542::INFO::[misc:342] complete_dir directory: \\192.168.1.30\UseNet does not exist, try to create it

2012-03-01 14:30:19,542::ERROR::[misc:344] Verzeichnis \\192.168.1.30\UseNet konnte nicht angelegt werden

2012-03-01 14:32:24,690::INFO::[misc:342] complete_dir directory: W:\UseNet does not exist, try to create it

2012-03-01 14:32:24,690::ERROR::[misc:344] Verzeichnis W:\UseNet konnte nicht angelegt werden

<edit2>
I just looked deeper in the logfile: accessing W: did work with 0.6.14 - but after installing 0.6.15 the previous version (and all others I tested) also fail :-(

<edit3>
even though I still couldn't re-animate my drive "W:\" within sabnzbd (also not after resetting/restarting everything in line (routers,switches,the box itself...) plus re-asserting the drive-letter W:), I kind of workarounded this:
instead of using "W:\" I am now using the UNC name "\\WDTVLIVEHUB\WDTVLiveHub" - maybe that's how it was supposed to be from the beginning?
-> with this, it's working again (and even with version 0.6.15) :-)

Sounds to me like the mapping of the W: drive to the UNC path is wrong.

well, no..

the mapping still is fine, sabnzbd is the *only* program not being able to access it - every other program works fine with the drive-letter

plus: I didn't change a thing when switching from 0.6.14 to 0.6.15 - only installed the new version, not even rebooted the WD TV, but after the installation the problem was there!

so, must be a bug in 0.6.15 - accessing via UNC is only a workaround, please fix it!

What happens if you go back to the previous version of SABnzbd?
Does it suddenly start working again?

I am having this same issue, although I have a few more variables to introduce. I installed a new unRAID server for storage today. I am using SMB security within unRAID. I am running both sabnzbd 0.6.15 and the latest SickBeard both as Windows 7 x64 services (UAC is turned off). In order to give the programs access to the unRAID shares, all services are being run by a user with an account on the unRAID box. SickBeard is perfectly happy with this new setup and can write to the unRAID share just fine. Sabnzbd refuses to recognize the media share that I have mapped as "M:" and gives the the unable to create folder error. I have tried everything I can think of, short of disabling SMB security on the unRAID box (that's not exactly a solution). I ran the "Permissions Fix" on the unraid box to make sure permissions were set correctly and have verified on multiple user accounts that they working fine. I downgraded to 0.6.14 and have the same issue.

As mentioned above, it appears sabnzbd is the only program that has issues with this drive mapping. I have confirmed that the user account that sabnzbd is running under has access to the share and can create/delete folders. The log file doesn't say much other than after unpacking it is unable to create the folder M:\Download\<Completed>. When I try to point the incomplete, complete and watched folders in Config->Folders to M:\Download, M:\Download\Temp and M:\Download\AutoImport, respectively, it thinks the folders don't exist (which they do), tries to create them and fails.

Any thoughts would be appreciated. I can supply any log files or additional information as needed.

*EDIT*
I turned off SMP security to see if it would fix the issue and it did not. Regardless of whether the share requires a username/password the problem persists.

Services have no access to mounted drive letters, use full UNC paths like \\server\share.
Make sure you have the "temporary download folder" on a local drive.

shypike wrote:Services have no access to mounted drive letters, use full UNC paths like \\server\share.
Make sure you have the "temporary download folder" on a local drive.

How do I get sabnzbd to accept a Unc path? It errors out when I try. It was my understanding that it had to be a drive letter because par2 doesn't recognize unc.

The "temporary download folder" should be local, so a drive letter is always available.
That's the one used by par2.
All other folders ("complete", category folders) can have UNC paths.

<sigh> I should have stepped away from this issue and wrote this post hours before I did.

I had already tried changing the temp folder to a local directory and changing the download directory to the UNC share, but neglected to change it under categories so it was still pointing to the drive mapping. :-/

Working great now. Thank you very much.