Note that there are some explanatory texts on larger screens.

plurals
  1. POWhen using py2exe, PyQt application cannot load SQlite database
    primarykey
    data
    text
    <p>My PyQt application works fine when running on Linux, when in my Windows build environment, or frozen on the machine where it was build with py2exe. But after moving the frozen executable and its supporting files to another machine it can't load the database driver.</p> <p>It worked fine when I had Python2.5 and an earlier version of PyQt and py2exe. But after upgrading my toolchain I get these errors: <br/></p> <ul> <li>dbname.open returns false</li> <li>lastError(dbname) is "Driver not loaded"</li> </ul> <p>I have an sqldrivers folder where I put qsqlite4.dll. This was necessary with the previous build environment, but moving or renaming that DLL doesn't change any behavior. I think that's the DLL that Qt can't find, but I haven't been able to tell Qt where to look.</p> <p>I am currently running these versions:</p> <ul> <li>python-2.6.3<br/></li> <li>PyQt-Py2.6-gpl-4.6-1<br/></li> <li>py2exe-0.6.9.win32-py2.6</li> </ul> <p>Profiling in Dependency Walker gives me this error:<br/> LoadLibraryW("\application\sqldrivers\qsqlite4.dll") returned NULL. Error: This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem (14001).<br /> When I ask Dependency Walker for details about Qsqlite4.dll it says:<br /> Error: The Side-by-Side configuration information for "\application\sqldrivers\QSQLITE4.DLL" contains errors. </p> <p>That would explain why the DLL won't load, but I'm still unclear how to fix it. Closer inspection shows that error for most of the DLLs I call. Do I need to include a manifest for each Qt DLL I load?</p> <p>Thanks in advance.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload