Zugg Software :: View topic - [237/302B/303Ba] Unable to start application due to missing dynamic libraries.

Posted: Tue Dec 30, 2008 11:13 pm

Everything was working last session. Today, I attempt to start CMUD and I get the following:

Posted: Tue Dec 30, 2008 11:45 pm

The SQLite dll is included with CMUD and should still be there. You can try uninstalling and reinstalling. Or if you have the sqlite3.dll you can copy and rename that as well.

Posted: Wed Dec 31, 2008 8:30 am

Yes, they were/are there and I did uninstall/re-installed the application (each version), as I noted on my post. I posted because the problem is obviously version-independent. CMUD does not find the libraries in spite of the fact that the dlls are there. I also think that uninstall/re-installing is a bit drastic as far a fixes go and it doesn't work. The only way I got it to work again was by doing a shutdown and then a start (re-start did not do the fix, or the problem requires more than one restart, which is also drastic as well). Fixing it this way is not a solution, it's a kludge.

Apprentice Joined: 18 Feb 2007 Posts: 190

prolly some of your other apps registered sqlite.dll systemwide and/or dirty uninstall left references to wrong version/nonexistant location

Posted: Mon Jan 05, 2009 6:26 pm

You are using Vista. Vista seems to have a problem locking DLLs in memory now and then. I've seen this happen myself with several different applications that use SQLite, and also with some other DLLs. I have no idea what causes it, but rebooting the computer always seems to fix the problem here. It doesn't happen on any of my WinXP systems, so I'm not sure what changed in Vista to cause this, but as intoK mentioned, it could also be related to some other software that is different between the two computers.

The error message that CMUD gives is actually pretty poor. The problem isn't that CMUD cannot find the sqlite.dll. The problem is that *any* error in the initialization of SQLite that causes any sort of crash prevents the library from being loaded and then triggers this message. So it's probably finding the file, but is probably getting an error trying to load the library. My investigation into this problem seems to show that sometimes Vista cannot load SQLite.DLL into memory and gives an access violation when trying to load it, usually because it's already in memory but is somehow corrupted.

So it's also possible this is an SQLite problem. What's interesting is that the problem only seems to happen for me with the SQLite.dll (v2.8) file and not with the SQLite3.dll file. So maybe it's something they already fixed in SQLite v3?