SABnzbd Forums

Last night I updated from 0.4.9 to 0.5.0. Update went fine, but SAB wouldn't start. I could see it show up in Task Manager for about half a sec, then it would close again. I've tried every trick I could Google, from using a 'run' command to the console to deleting the .ini but nothing worked. Not on :8080 and not on :8081. Rebooting my pc seemed to help, but this morning it wouldn't start no matter what.

I finally downloaded 0.4.9 again, removed 0.5.0 and went back to 0.4.9. Works like a charm!

Version: 0.5.0
OS: Windows Vista
Install-type: Windows Installer
Firewall Software: Bitdefender internet security 2010

I have no idea at all what the problem could be - nothing changed on my PC / Windows and 0.5.0. simply won't run (service starts and closed within a second) while 0.4.9 works like a charm from the getgo ...  ???

You told "BitDefender" to leave SABnzbd alone?
What happens if you run SABnzbd-console.exe from a command prompt?

Yes, Bitdefender showed a popup about the file having changed after the update, I obviously allowed it. I also tried deleting the SAB-rule, disabled Bitdefender startup etc..

When I tried to run the console it did the exact same thing: started and stopped within a second. No error, nothing.

And again, without making any adjustments whatsoever, 0.4.9 works like a charm while 0.5.0 simply won't do anything more then start and die within a second ...

Sounds like a corrupt installer.
Have you tried our Windows ZIP distribution?
At least you can tell WinZip or Unrar to check the integrity.

I've just tried that, but I get the exact same result: service starts, shows up in task manager for a split second and then stops. 
Started 0.4.9 directly after that, no problems there.

Seems like some change between the two versions is not working here ... But I have no idea what it could be.

I'll just stay with the 0.4.9 version for now.

As a last test, could you try this:

Create a new folder somewhere and leave it empty.
Start SABnzbd from the command line: This should bring up the Configuration Wizard.

Just to test that it doesn't just choke on your existing INI file.
It shouldn't, but you never know.

I know it doesn't, I copied the 0.5.0 INI file to the 0.4.9 folder (too lazy to go through all the settings, and it's a good testcase as well).
So both versions have the exact same INI file, and only 0.4.9 works.

I'm facing the same problem.
Don't see any errors or logs.
I have reinstalled version 0.4.12 and this one is working fine.

I'm having the exact same problem than OP: 4.9 works like a charm, 0.5 launches for half a second then disappears, no error... Tried to reboot, removes, reinstalls: several times. Nothing helps.

Using Win 7 64 Bits. However, the "sabnzbd-console.exe" returnes the following error:

Looks lke a corrupt installation, because it means files are missing.
Uninstall, re-download the installer and install again.

Or you have a crazy virus scanner.

shypike wrote: Uninstall, re-download the installer and install again.

Did you read this thread? That's been done, and more then once ... Even tried a different package but still no go.

I think shypike was referring to the post above.

@Mar10e, try the following:

Open up command prompt (start > run > cmd)
If Vista 64bit enter the following:
C:\Program Files (x86)\SABnzbd\SABnzbd-console.exe > c:\output.txt
otherwise enter:
C:\Program Files\SABnzbd\SABnzbd-console.exe > c:\output.txt
Open up c:\output.txt and see if you received anything of interest.

@Nesousx
Looks like C:\Program Files (x86)\SABnzbd\lib\sqlite3.dll is missing.
As shypike says, do a full uninstall, delete the SABnzbd folder (first the folder in program files, if not everything in the settings.) and run the installer again

Hi,

Have the same problems on Windows 7 64 bits and Bitdefender. When deactivating the antivirus shield of Bitdefender, it all works! I tried adding Sabnzbd in the exclude list but that doesn't seem to help yet. Working on it. Hope this will contribute towards a solution.

Martin

Please pass on your complaints to BitDefender.

We test for compatibility with Windows and Microsoft security tools.
Not with all sorts of crazy security suites.

Ok, now you know it's a Bitdefender issue.

Martin