Page 1 of 1

Can't save downloads to network drive path

Posted: September 5th, 2011, 6:05 pm
by lavelle568
Hi there:

Using: Win7 64 (and giganews)

This was working, and suddenly it's not. Not sure what changed - I can't save anything to my network drive path set in the categories section of the config:

Code: Select all

2011-09-05 18:46:06,421::INFO::[misc:718] Creating directories: M:\files\media\videos\Red State 2011 PPV 720p HDTV x264 MOMENTUM

2011-09-05 18:46:06,423::ERROR::[misc:720] Failed making (M:\files\media\videos\Red State 2011 PPV 720p HDTV x264 MOMENTUM)

2011-09-05 18:46:06,423::ERROR::[postproc:444] Post Processing Failed for Red State 2011 PPV 720p HDTV x264 MOMENTUM (Cannot create final folder M:\files\media\videos\Red State 2011 PPV 720p HDTV x264 MOMENTUM)
I can save to my local drive just fine. This started showing when I upgraded to sabnzbdplus 0.6.8 - I already tried the preview versions down to 0.6.5 (which I was running up until recently), and it still occurs.

My apologies if this is an issue addressed on the forum already - I tried searching for this issue and found some solutions (one of which was re-enter the path in the categories config) but nothing has worked so far.

Thanks in advance!

Re: Can't save downloads to network drive path

Posted: September 6th, 2011, 1:25 am
by shypike
Is your M: drive still mounted?

Re: Can't save downloads to network drive path

Posted: September 6th, 2011, 8:40 am
by lavelle568
Yes, I can access it via Explorer; I can create, access, and delete files and folders.

Re: Can't save downloads to network drive path

Posted: September 6th, 2011, 9:51 am
by shypike
It's Windows, so did you reboot your system first?
Other than access rights problems and other Windows issues, I cannot think of anything.
All paths are the same as far as SABnzbd is concerned.
Does SABnzbd run under the same user account as when you use the Explorer?

Re: Can't save downloads to network drive path

Posted: September 7th, 2011, 7:58 am
by lavelle568
Rebooted, disconnected the drive mapping and made a fresh one. Works!

Again, apologies - it being a Windows system, I should have at least rebooted it a few times :)