Hey All
I tried a google of this error but no joy. Anyway i just recently installed SABnzbd (great software), but yesterday i logged off my account on WHS and logged back on and my queue and history had cleared from SAB (!).
Looked at logs and it gives this:
Loading C:\Documents and Settings\Saqib\Local Settings\Application Data\sabnzbd\admin\running.sab failed
Anyone know what this refers to?
Running.sab failed?
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: Running.sab failed?
The "running.sab" has no meaning, it's just a left-behind logging from a removed feature.
If you ran SABnzbd from a remote desktop session to WHS and you logged off,
the WHS will have forcefully terminated SABnzbd.
That's not good for the queue.
You should either start it from the official WHS console with a plugin like AdvancedAdmin
or you should install it as a service.
For the latter see: http://wiki.sabnzbd.org/how-to-install-on-whs
You can probably salvage your lost jobs on the Status page, tab "Queue repair".
If you ran SABnzbd from a remote desktop session to WHS and you logged off,
the WHS will have forcefully terminated SABnzbd.
That's not good for the queue.
You should either start it from the official WHS console with a plugin like AdvancedAdmin
or you should install it as a service.
For the latter see: http://wiki.sabnzbd.org/how-to-install-on-whs
You can probably salvage your lost jobs on the Status page, tab "Queue repair".
Re: Running.sab failed?
thanks for the reply. You're right, i did run it using an RDP session however when installing it, i did instal it as a service...