Location is not Available

[Eejit]

Checked  all the post's and haven't seen this mentioned before.
Running Vista SP1 & SABnzbd+ 0.4.3
System runs great, watches folder, grabs nzb and starts download.
Completes download, checks, unpacks, moves and deletes unwanted files.

I have the Queue auto refresh interval set to 20 seconds.
If, after downloading, I check the file(s) and think its(they're) crap, I delete the file(s) and folder.
Now, I get a warning every 20 seconds the the folder cannot be found. If I'm using the web interface,
every time I change something, like move from History to Connections, the error message box comes up again.

It appears that even that SABnzbd has finished with the folder, it isn't releasing some link to it.

Hope that's succinct enough.

Eejit - The name say's it all !

[Eejit]

OK, this is strange. I cannot replicate the problem in order to give you the exact message.

What comes up is a Windows message box, the title being "Location is not Available"
With-in the message box, there is a full explanation as to the fact that the completed download directory,
the final one that the files are moved to, cannot be found. There is no mention of which program has caused this, it's just the fact
that on my system, it re-appeared every time the web interface was changed, or if that wasn't active, then every 20 seconds as per the refresh rate I have set.

I will try further to repeat this problem. Suffice to say, that this isn't the first time it's happened, but just recently I discovered which program was causing it.
I know your first thought will be that I deleted the folder before the move was completed, but I don't think this was/is the case.

Eejit - The name say's it all !

[Eejit]

This Error message has occured again, 8 hours after the History tab states that the download etc was completed.
I didn't delete the folder, just moved it to a new location.
The interesting thing is, is that the 'hook' into the folder has survived a re-boot.

The message is as follows:-
D:\New Downloads\Ubuntu refers to a location that is unavailable.
It could be on a hard drive on this computer, or on a network. Check to make sure that the
disk is properly inserted, or that you are connected to the Internet or your network, and then
try again. If it still cannot be located, the information might have been moved to a different
location.

Regards

Eejit

[shypike]

Is this your base "complete" folder? If so, why did you remove it?

Is this  the folder for a specific job?
Did you run a script for the job?

Are there any jobs in the history who's status is not "completed".

Does the log file refer to this folder?

[Eejit]

Is this your base "complete" folder? If so, why did you remove it?

Not entirely sure what you mean by this.  If you mean is this the folder where all downloads go originally, before any post-processing, then no.

Is this  the folder for a specific job?

Yes. "D:\New Downloads"  is the folder that all post-processing end's up. "D:\New Downloads\Ubuntu" was the folder for this specific job. The "Ubuntu" folder was moved to another drive and "D:\New Downloads" left alone.

Did you run a script for the job?

No script's per se, only those that are built in and can be switched on via the Config screen's. There are no third-party scripts.

Are there any jobs in the history who's status is not "completed".

None what-so-ever.

Does the log file refer to this folder?

Have checked all the log files and there is no mention of "D:\New Downloads" at all


Hope this helps

[shypike]

Given your answers, why are you sure SABnzbd causes the problem?

[Eejit]

Because the error message comes up every 20 seconds, the same time I have set for Queue auto refresh interval
and comes up everytime I move around the Web interface, IE if I am in History and move to Connections, then a new occurance of the error pops up.

[shypike]

Check the sabnzbd.ini file for a mention of the bad location.
Otherwise start SABnzbd up with the --clean commandline option (you'll loose any queue and history).
Other than that, I wouldn't know a solution.
I cannot imagine what the cause of the problem is.

[Eejit]

It's no big deal.
I take it no-body else has reported this issue and no-one has been able to replicate it
by moving the folder?

A strange one in-deed.