firefox 5.0.1 fails to start with sqlite3.dll missing message
ff 5.0.1 started losing all my bookmarks. I imported them and the next day they were gone again. I had other strange things happening so I decided to go back to ff 3. I uninstalled ff5.0.1 and removed the ProgramFiles directory. I installed ff3 and it worked ok. I used it to upgrade to I believe 3.0.19 ok. I then upgraded to 3.6. The upgrade appeared ok but it would not start. I got an sqlite3.dll missing message. Nothing I have done has gotten ff to start. I have uninstalled and reinstalled 5.0.1 and still be sqlite3.dll missing message. I searched my C drive for sqlite3.dll and found several stored with other applications. The FF directory had an mozsqlite3.dll but not just sqlite3.dll.
At this point I can't start FF.
Toutes les réponses (4)
I tried to start FF 5.0.1 today, hoping something had changed, afterall this is on windows, but no luck.
However I got a different message. I got "Entry Point Not Found" and "The procedure entry point sqlite3_shutdown could not be located in the dynamic link library sqlite3.dll". This was immediately on start atempt.
Try downloading Firefox again, then uninstall Firefox, remove the program directory, and install it all over again.
I have done this several times with different versions with no success. FF 3 worked initially but even it will not work.
Does anyone know what FF is really looking for and where it should be? There is an mozsqlite3.dll in the FF directory.
I did a clean uninstall of FF and installed a clean download of FF 3.6.19. When I tried to start it I got an xulrunner version error message, first time I have seen this. While looking up xulrunner stuff I found info that this can be caused by security program like Zone Alarm Extreme Security which I am running. They said that the security program can sometimes prevent changes to the application.ini file. One suggestion was to install FF into a different directory using the custom install. I installed FF 5.0.1 into "Mozilla Firefox5" and FF now works!!
I can only assume that Zone Alarm was getting in the way.