SABnzbd Forums

I got a questions about getting sabnzbd 0.50rc3 working on WinXP.  Whenever I run the executable, nothing happens.  The program does not execute and, of course, task manager does not show it.  When I run the console it gives me the following complaint, "Sorry, requires Python module sqlite3 (pysqlite2 in python2.4)."

I had no problems getting 0.4.12 working, but I'd like to get 0.5rc3 working instead.  Any suggestions?

Just saw this reported on IRC. Which install method did you use? Source? The installer? The binary zip?

I used the installer for both the 0.4.12 final and 0.5rc3 versions, and only 0.4.12 seemed to install correctly.

I've tried to do a clean install of 0.5rc3 and also a upgrade install from 0.4.12 to 0.5rc3, both resulting in the same error message.

I installed v0.50rc3 on my WinXP Pro SP3 system today and it's working perfectly. This the first time any version of SABnzbd was installed on my system. So, obviously a clean install works. Perhaps this python file was installed by some other package on my system? Or perhaps something weird happened on yours?

Oh, yes. I used the installer version.

WillowD wrote:Perhaps this python file was installed by some other package on my system?

I've tried the install package on two different systems and on one virtual machine with no luck.  One of my systems has Python 2.6 and 3.1 installed too.  Strage stuff.

I got it working by downloading the sqlite3.dll from sqlite.org and replacing the one that came with the sabnzbd install directory (SABnzbd\lib).

The most likely cause is that your system has a version of Python installed
and that the system search path includes the DLLs from that Python.
This could confuse SABnzbd's runtime system.
I think you should make sure that sqlite3.dll isn't found via the PATH environment variable.

However, I have never seen this on my own systems that contain multiple Python versions.

If it was ignoring the dll to begin with then that wouldn't explain why replacing the dll in the sabnzbd/lib dir would fix the issue.

Anyways, I checked my user and system paths and uninstalled any python installs that I had.  Not sure what the issue was, but I'm glad to have gotten it working.

Very weird.
We'll tackle this problem too, but not for 0.5.0 Final.
I must first find out why it helps to replace the DLL.