We were asked to look at a server recently that was reporting problems with the WID (Windows Internal Database) not starting. This is also known as Microsoft SQL Server Compact Edition or SQL Server Embedded. The SQL Server instance used by Windows Sharepoint Services was reporting some errors and in this case wouldn’t start.
The event log showed the following error.
Source: Service Control Manager
Event ID: 7024
Level: Error
Description:
The Windows Internal Database (MICROSOFT##SSEE) service terminated with service-specific error 3417 (0xD59).
The application event log also had a few of the following type of errors.
Source: MSSQL$MICROSOFT##SSEE
Event ID: 17204
Level: Error
Description:
The description for Event ID 17204 from source MSSQL$MICROSOFT##SSEE cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
FCB::Open failed
C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\mastlog.ldf
2
5(error not found)
One of the databases was corrupt and it turned out that the database needed to be removed and re-installed, but Windows Internal Database wasn’t listed in Programs and Features (Add/Remove Software in Windows 2003 Server). If this happens to you try these instructions.
Firstly, run the following command from a command-line if you run a 32 bit server;
and this one if you run a 64 bit server;
This will uninstall the Windows Internal Database. Next you have to re-install it. The easiest way to do this is to run the WSS 3 SP1 installation routine. Choose the ‘Basic’ installation option when installing WSS and WID will be reinstalled and used to store the WSS data.
Choose the basic option
