Winrar Script not working

[shadymg]

Using Windows 7 x64 and the following script:
"C:\Program Files\WinRAR\WinRAR.exe" e -ibck -iadm "%f\%n\*.*" "D:\Downloads\Extracted"

I have a very odd problem. If i manually add a torrent, then the script works and the rars get extracted to the Extracted folder above.

Now the weird part. If a torrent begins as one of my RSS notifications, then Winrar stops with an error "The Process cannot access the file because it is being used by another process." And of course, the extraction does not work.

Troubleshooting:
- If i open the rar folder locations and extract manually, then it works
- if i delete one of hte *.rXX files in teh folder, then re-check the file in qbittorrent and let it complete the download again, then the script works

Am i missing something obvious???

[Djlatino]

How has this not been attended to? Qbittorrent can't run external programs even if it tried with its left nut dragging on an unpaved road. This part of the client has been a constant issue, and it doesn't make sense as to why it would be.

Fix it NOW in 2015, even though this bug goes all the way back to the summer of 2014.

[tekko]

I went through the winrar manual, the switch "-IADM" is for SFX archive. Do u really need it? Is there any difference without it? It might not even be related at all, just a thought...

[ciaobaby]

If the script or application starts it is NOTHING at all to do with qBittorrent.

[Djlatino]

[quote="ciaobaby"]
If the script or application starts it is NOTHING at all to do with qBittorrent.
[/quote]
Can you elaborate as to why the error might occur where the process cannot access file? This has something to do with the occurrence of using RSS rather than manual downloading. Whether you change the parameters of WinRAR to extract, it doesn't matter, this issue still occurs. It seems to happen to 7zip as well.

[ciaobaby]

Check what the values of "%f & %n" are under both conditions.


test by not using *.* as the filespec as you only need to specify the primary archive file rather than attempting to open them all

[Djlatino]

[quote="ciaobaby"]
Check what the values of "%f & %n" are under both conditions.


test by not using *.* as the filespec as you only need to specify the primary archive file rather than attempting to open them all
[/quote]
I noticed if you out %f/%n, it adds an extract slash, so I tried %f%n and the directory is fine, but I get the same error nevertheless. I try -o%f%n/thegoodz and I get the same issue. Whether I specify the file (i.e. *.mkv), I always get some kind of error, or it doesn't extract at all.

I honestly feel for you, since I know this is an external issue, but maybe it's cause the torrent is just getting moved for seeding or something? I might be ignorant on the topic but adding a 3-5 second delay of when the command could be executed may alleviate errors. Just an idea though.

[ciaobaby]

(i.e. *.mkv),

Which of course WOULD and SHOULD result in an error as .mkv is a container format not an archive format. This is why I suggested that *.* is NOT a suitable filespec for an 'extract' operation, as "non-archive" file types ARE going to cause an error. So if the folder contains files OTHER THAN archives (zip, rar, arj, gz, bz, 7z, etc.) it WILL throw an error than may be reported as a inaccessible file name.

IF the folder contains a 'split' archive and the script/application tries to open more than one of the archive tree when it gets to one that is already open it is likely to 'bomb out'.

Before deciding the is the fault of qBT, all other possibilities have to be eliminated empirically.

[shadymg]

okay, i'm just at a loss. same exact script, sometimes it works, sometimes it doesn't. I'm at a loss. Given the randomness, how can i not blame qbittorrent? does anyone have a script that they use that works 100%?

EDIT: Some further clarity as i think i've narrowed down all the problems:
1. Whether i add a file manually via web browser, through the RSS window on qbittorrent, or it's automatically added by RSS, then the result is the ACCESS ERROR

2. If i open the location, delete one of the rar files (say *.r08), then force re-check, then VOILA, Winrar rocks and rolls without an error and the file's extracted properly.

So...this has to be a qbittorrent problem, no????

[ciaobaby]

So...this has to be a qbittorrent problem, no?

Given  this ...

If i open the location, delete one of the rar files (say *.r08),

.. No.

[shadymg]

*sigh* so i'll go back to the original question then--does anyone have a winrar script that works 100% of the time they can share?

[ciaobaby]

have you tried with *.rar instead of potentially locking all the files in the folder by using *.*??

[shadymg]

yes, i had tried with both *.* and *.rar

I ended up 100% GIVING UP on the running an app after download, just too much inconsistency for my liking. I was able to find an app somebody made called "Torrent Monitor" and it works flawless - http://forum.kodi.tv/showthread.php?tid=175578

[Djlatino]

(i.e. *.mkv),

Which of course WOULD and SHOULD result in an error as .mkv is a container format not an archive format. This is why I suggested that *.* is NOT a suitable filespec for an 'extract' operation, as "non-archive" file types ARE going to cause an error. So if the folder contains files OTHER THAN archives (zip, rar, arj, gz, bz, 7z, etc.) it WILL throw an error than may be reported as a inaccessible file name.

IF the folder contains a 'split' archive and the script/application tries to open more than one of the archive tree when it gets to one that is already open it is likely to 'bomb out'.

Before deciding the is the fault of qBT, all other possibilities have to be eliminated empirically.

Thanks! You educated me, believe it or not. But as mentioned above, specifying *.rar regardless will throw an the OP error, unfortunately. Torrent Monitor, something I was going to be using, but I also found filebot, www.filebot.net/forums/viewtopic.php?f=4&t=2131 if anyone wants to get it a go.

[Djlatino]

Just an update, it seems that torrent monitor gives an error with Qbitorrent when trying to extract, but not when I try it with deluge or utorrent.

ciaobaby, sorry bro, this is a Qbit issue.