Support Forum

Prior to 0.6.10 I can't reproduce the problem.

Well I've been using SABnzbd for many versions with the same OS and NAS, and only until these last few releases did I start to have the problem. And r/w access to the NAS via windows explorer has always worked.

Thanks for the replies though.

Yes, I just upgraded to 0.6.14 and this problem popped up. I also experienced it with 0.6.12.

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...

I too started having this problem with 0.5.2... the other change I made was from a 100mb nice to 1gb nic, but I doubt that would have anything to do with it. Running XP SP2. Connecting to Supernews with SSL. Tried both ssl ports. It allows for 30, but I had to set SABnzbd to 20 connections to get th...

did a "sabnzbd.exe --clean" that took care of my busted job in the queue.

Hi Switch, Thanks for replying. I did try turning off the multicore, but it did not help. After I restarted sabnzbd, I saw it try to retrieve some pars, but some were missing from the server. This NZB post was probably a bit to old. So I understand the missing articles will not allow this job to pro...

I think I'm having the same issue with 0.5.0 running on XP. I have a job that looks complete and is in the "verifying" stage and says "starting repair", but it's not doing any repairs as far as I can tell. I'm not sure how to delete this out of my queue now. It does not delete th...