Access error on unpack

[winniwinter]

Hello,

I'm pretty new with the sabnzbd server. But I already really enjoy it.

At the moment I'm getting errors when unpacking files after the download is completed:

2011-01-21 01:07:02,079::INFO::[newsunpack:185] Unrar starting on D:\shares\Videos\TEMP\incomplete\31884873
2011-01-21 01:07:02,079::INFO::[newsunpack:384] Extracting rarfile D:\shares\Videos\TEMP\incomplete\31884873\gas06dvd5ut.rar (belonging to gas06dvd5ut) to D:\shares\Videos\TEMP\TV\_UNPACK_31884873
2011-01-21 01:07:02,391::ERROR::[newsunpack:397] Fehler "[Error 5] Zugriff verweigert" beim Ausführen von rar_unpack auf 31884873
2011-01-21 01:07:02,391::INFO::[newsunpack:189] Unrar finished on D:\shares\Videos\TEMP\incomplete\31884873
2011-01-21 01:07:02,407::INFO::[postproc:317] unpack_magic finished on 31884873
2011-01-21 01:07:03,095::INFO::[postproc:470] Cleaning up 31884873

System Information:
OS: WHS
Version: SABnzbd+ 0.5.6
Theme: Splush
Firewall: Comodo
IPV6: no
error reprocudable: yes. Occurs on every attempt of unpacking files

I installed the server as a deamon. The User has Admin rights. If I connect remotly to my WHS and login with this user I am able to unpack the files manually with the unrar.exe
At first I thought it's maybe the firewall so I disabled it but I still got the error.
Since the User has admin privileges he also should be able to unpack the files to the folder.


Pls help  ???

[shypike]

You should never ever write to d:\shares !
Your final destination folder should always be something like this: \\server\share
Otherwise you'll ruin your WHS storage.

You temporary folders should be in a separate folder in D:\, like d:\usenet

[winniwinter]

ok thx for your information,

I changed the paths to UNC.


But still the same error:

2011-01-21 10:43:23,923::INFO::[misc:837] Creating directories: \\winniserver\Videos\TEMP\Music
2011-01-21 10:43:23,923::INFO::[misc:837] Creating directories: \\winniserver\Videos\TEMP\Music\XXX - XXX
2011-01-21 10:43:23,938::INFO::[postproc:315] Running unpack_magic on XXX - XXX
2011-01-21 10:43:23,938::INFO::[newsunpack:185] Unrar starting on D:\usenet\XXX - XXX
2011-01-21 10:43:23,938::INFO::[newsunpack:384] Extracting rarfile D:\usenet\XXX - XXX\XXX_XXX.part1.rar (belonging to XXX - XXX) to \\winniserver\Videos\TEMP\Music\_UNPACK_XXX - XXX)
2011-01-21 10:43:23,970::ERROR::[newsunpack:397] Fehler "[Error 5] Zugriff verweigert" beim Ausführen von rar_unpack auf XXX - XXX
2011-01-21 10:43:23,970::INFO::[newsunpack:189] Unrar finished on D:\usenet\XXX - XXX
2011-01-21 10:43:23,970::INFO::[postproc:317] unpack_magic finished on XXX - XXX
2011-01-21 10:43:24,704::INFO::[postproc:470] Cleaning up XXX - XXX

[shypike]

Well, you still need to take care that the access rights are OK.
Under which user account do you run SABnzbd and does that account have access rights to the shares?

Are you running SABnzbd as a Windows Service?
If so, SABnzbd must run under a user account that has write access to the used shares.
That account cannot be "Local System".

[winniwinter]

I have a user called WHS. This one has access rights to all shares. This is also the user the service runs with.

As I said. I already logged in remotly with this user and started the unrar.exe manually. This works fine.

[winniwinter]

still having this issue 

2011-01-27 16:15:47,625::INFO::[postproc:134] Saving postproc queue
2011-01-27 16:15:47,625::INFO::[postproc:243] Starting PostProcessing on Creed - Weathered (2001) => Repair:True, Unpack:True, Delete:False, Script:None
2011-01-27 16:15:47,625::INFO::[postproc:247] Par2 check starting on Creed - Weathered (2001)
2011-01-27 16:15:47,625::INFO::[postproc:254] Running repair on set Creed-Weathered-Retail-2001-Recycled_INT
2011-01-27 16:15:47,625::INFO::[newsunpack:674] Scanning "D:\usenet\Creed - Weathered (2001)\Creed-Weathered-Retail-2001-Recycled_INT.vol00+01.par2"
2011-01-27 16:15:47,780::ERROR::[newsunpack:698] Fehler "[Error 5] Zugriff verweigert" beim Ausführen von par2_repair auf Creed-Weathered-Retail-2001-Recycled_INT
2011-01-27 16:15:47,780::INFO::[newsunpack:699] Traceback:
Traceback (most recent call last):
  File "sabnzbd\newsunpack.pyo", line 679, in par2_repair
  File "sabnzbd\newsunpack.pyo", line 1009, in PAR_Verify
WindowsError: [Error 5] Zugriff verweigert

[shypike]

User WHS may have access to all shares, but has it access to the actual D: drive?
My guess is that it hasn't.

[winniwinter]

all users of group Administrators have access to D:\
Since the WHS user is in this group I would say he has the access rights. Thats why I am at the end of my nerves.

[shypike]

What if you run it under the real "administrator" account?

[winniwinter]

already tried that yesterday. still same error

[winniwinter]

Ok, on one file the par2 repair was working. But the unpacking failed again.

Next Test. Repair directly failed. In log I find this message:

2011-01-28 18:09:23,030::ERROR::[newsunpack:698] Fehler "[Error 5] Zugriff verweigert" beim Ausführen von par2_repair auf ich13108
2011-01-28 18:09:23,030::INFO::[newsunpack:699] Traceback:
Traceback (most recent call last):
  File "sabnzbd\newsunpack.pyo", line 679, in par2_repair
  File "sabnzbd\newsunpack.pyo", line 1009, in PAR_Verify
WindowsError: [Error 5] Zugriff verweigert

Program started with user Administrator, Firewall is off

[shypike]

I'm sorry to say that I have no idea what is going on.
On Windows, SABnzbd doesn't bother with access rights at all.
It just assumes that rights are properly set and that new files and folders
inherit right from their parent folders.
This is the normal situation on Windows.
Can you find any additional info in the Windows security event log?
Access violations are logged by Windows.

[winniwinter]

I don't beleive anymore that it is a windows access right problem. Now I downloaded a file that could be successfully repaird, moved, unpacked.

It seems that the error occurs randomly

[winniwinter]

I deactivated the fast par2 check. Now I had no error. But why???

[shypike]

You mean QuickCheck?
That's very strange, because when QuickCheck is on,
the piece of code that reports the error isn't active when
a download had no errors and didn't need par2 repair.

The alternative is that you try the latest Alpha version of release 0.6.0
I can add you to the test group if you want.
This release has the added advantage that you can run it as a true Windows Service.