SABnzbd Forums

1.0.3

Should I just install it on top?

Yes, works fine.
Going back to 0.7.20 would be a bit more tricky.

I just downgraded and tried downloading the same release. I got the same error.

Hmm, the last resort is to downgrade to 0.7.20.
That release will not recognize your current queue (if not empty).
But, I suspect there is something wrong with access rights on your system.
Is this on Windows 10 (and if so, the Anniversary update)?

Hmm, but why is it happening only for this movie? No, this still is on Win8.1.

kevindd992002 wrote:Hmm, but why is it happening only for this movie? No, this still is on Win8.1.

What happens when you do a manual "unrar.exe ... " on the problematic rar file?
What happens when you do a unrar with winrar on the problematic rar file?
Can you PM or mail the .NZB file?

I don't have the files anymore since CP deleted them already. Should I redownload it while keeping the automatic unrar'ing of CP to disabled?

Here's the NZB: https://www.dropbox.com/s/jw1tka1p1d1ru ... D.nzb?dl=0

Can you download the NZB yourself with SABnzbd, and without CP's involvement?

I'll do the same, and post back the results.

Ok, I'll do that now. Thanks.

FWIW: no problems downloading and unpacking it on my Linux.
I have to try on Windows.

How is your plain-SAB download going?

sander wrote:FWIW: no problems downloading and unpacking it on my Linux.
I have to try on Windows.

How is your plain-SAB download going?

It failed again but this time I really don't have disk space. Let me free up some space first and do a retry. If it works, I'll try downloading it with CP to compare. I swear I had 20GB worth of free space (as indicated in both my computer and SAB's GUI) when I first reported this problem a few days back.

Ok, retrying the failed download in the queue was successful this time. I don't know what is different this time but it did work. 20GB of free disk space is more than enough to accommodate unrar'ing a 7GB movie release. Anyway, I don't want to waste your time in determining the root cause but thanks for all the help

've just started seeing these after updating to 1.1.0, never seen it before.

As other posts, this happens on particular NZB only, if I shift the troublesome NZB down the queue, other NZB get saved no problem so not a permission or other disk error in my opinion.

I'm not the most technical person so don't know how much I can do to help, but just wanted to let you know I'm now seeing this for the first time ever.