Uninstall / Reinstall / Repair the Windows Internal Database (WID) aka Sql Server Embedded Edition (SSEE)
If you do a basic or standalone install in WSS 3.0, you will be using the Windows Internal Database. This database is a variation of SQL Express. The advantage is the 4GB limit has been removed. This makes it a better option than SQL Express.
Now... if you have to reinstall your WSS or something get hosed along the way, the database can be your worst nightmare!!! Your install can fail at step 1, 2, or 5. This is how you get past the demons!!!
These files are stored @ C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL
If you only have WSS installed on this machine, turn off the SSEE Service and wack these guys.
Now, you will need to uninstall the WID. Open up a cmd window and paste in the correct line below.
x86:
msiexec /x {CEB5780F-1A70-44A9-850F-DE6C4F6AA8FB} CALLERID=ocsetup.exe
x64:
msiexec /x {BDD79957-5801-4A2D-B09E-852E7FA64D01} CALLERID=ocsetup.exe
Make sure WSS is uninstalled. Reboot. And reinstall. You will now be able to make it through step 10!!!
I hope you found this post early in your struggle. Many people tend to kill their OS and start over. Now you don't have to.
Friday, September 5, 2008
Subscribe to:
Post Comments (Atom)


6 comments:
I just want to say that after trying to fix a bad install for 2 days, your solution worked. Thanks so much.
I needed to add the following steps to your solution:
http://support.microsoft.com/kb/919945
thanks much... this really helped me out. I was trying to reinstall WSS on a server that was repaired and was receiving this weird error about the WID. thanks again...
Thanks a lot for sharing this. Now it's finally configuring sharepoint again!
Just wanted to add a note in case anyone else finding this has the same problem.
In my case I'm trying to reinstall WSS on a Win7 OS (there's a hack out there, which worked great the first time) and get the "Failed to start the database service mssql$Microsoft##SSEE" error when running the configuration tool post-install. However:
a) I don't have any C:\Windows\SYSMSI directory (no, it's not hidden)
b) I don't have any SSEE service
c) Your msiexec command says the application isn't installed
To answer my own problem, the answer was on: http://www.annoyances.org/exec/forum/win2003/t1185630167
In short: Reinstall WSS as being part of a new Server Farm, even though it's really stand-alone.
Post a Comment