SABnzbd Forums

Prior to 0.6.10 I can't reproduce the problem.

So this means that 0.6.9 is working and 0.6.10 is not?

Between these two releases there has been only one change that could be related.
Render ambiguous Windows paths like "D:" and "D:folder" as "D:\" and "D:\folder".
If that causes the problem, it indicates that you are currently using incorrect path names.
So paths with missing backslashes.

I am at version 0.6.15 and I am running into this. I just started with usenets and was doing a Sickbeard/SABnzbd install.

I am running this on win7, 64-bit, on a share to a WinXP Pro machine. I am running this on the admin account for Win7, I even started SAB as administrator. In WinXP under sharing permissions, I give everyone Full control, Change, and read access.

Try to input: N:\Usenet\Incomplete

I get: Incorrect parameter Cannot create download_dir folder N:\Usenet\Incomplete

according to the logs:
2012-04-07 17:37:39,657::INFO::[misc:331] download_dir directory: N:\Usenet\Incomplete does not exist, try to create it
2012-04-07 17:37:39,657::ERROR::[misc:333] Cannot create directory N:\Usenet\Incomplete

But, the folder exists, so not sure why it cannot read the directory?

Shypike, you mention that UNC paths are fully supported:

UNC paths (\\server\share) are fully supported, and work fine for most NAS systems connected to Windows.

but when I input: \\KIMCHI\Downloads\Usenet\Incomplete

I get: Incorrect parameter UNC path "\\KIMCHI\Downloads\Usenet\Incomplete" not allowed here

So I am not sure how to get around this without using my local hard drive?

I also tried the SymLink that was posted earlier.

KrakaJap wrote:This happened to me with the current 6.9. Same user running the sab service has the same access to a network share. Using windows explorer works just fine but sab throws back an error. The good guys on chat suggested that I use mapped folder to network share with "subst" which didn't work but that gave me the idea to use a symbolic link instead. Worked like a charm! Now this isn't my ideal solution (personal preference) but it will work fine until another solution presents itself.

example:
FreeNAS mapped to Z: on my win7 desktop (which sab can no longer access) - F: is a physical drive on my desktop.
symbolic link (from a command prompt): mklink /d F:\NAS \\freenas\NAS
"F:\NAS" becomes the symbolic link to the same network share that Z: is mapped to and sab can write to it just fine.

Didn't work either

And lastly, I have uninstalled and tried 0.6.9, but still got the same problem

hmm, I rebooted my machine, and it worked after that. Not sure why.