The database <databasename> on <Server>Microsoft##SSEE is not accessible to missing Windows Internal Database signatures


One of the more frequent issues we are seeing with the installation of our most recent WSS v3 hotfix, KB934525, is the error message "The database <databasename> on server\Microsoft##SSEE is not accessible to missing Windows Internal Database signatures" being logged in the server event log.


(SSEE = SQL Server Embedded Edition, which is what you get when you install WSS 3.0 without using a seperate SQL instance. SSEE is also know as WYUKON, WSSEE, WID or Windows Internal Database).


Event Type:      Error
Event Source:    Windows SharePoint Services 3
Event Category:  Topology
Event ID:        6800
Date:            10/17/2007
Time:            8:09:40 PM
User:            N/A
Computer:        HOME
Description:
The database WSS_Content on <SERVER_NAME>\Microsoft##SSEE is not accessible to missing Windows Internal Database signatures.


To verify if you are experiencing this problem, look for something like the following from Services in Server page in Central Administration.  Note how Windows SharePoint Services Web Application is showing Starting but no stop option.   



If you experiencing this issue, you should also have entries like the following in the upgrade.log log file:


[SPServerSequence] [DEBUG] [10/22/2007 7:44:21 AM]: Web service Instance SPWebServiceInstance Parent=SPServer Name=<URL> not added. Status = Provisioning


A solution is available to administrators experiencing the issue.



  1. Run the following STSADM operations to stop and start the SPWebService:


    • stsadm -o provisionservice -action stop -servicetype spwebservice -servicename ""

    • stsadm -o provisionservice -action start -servicetype spwebservice -servicename ""

  2. Instantiate the upgrade by executing psconfig.exe or psconfigui.exe

The cause of this issue appears to be because the SPWebService instance failed to finish provisioning. The status of that service is marked as provisioning. However, it has done enough provisioning work so that the user sites are working and/or during upgrade, the upgrade code skipped any web service instances that are not online, upgrading the administration sites; however, skipping the user sites.

screenshot001.jpg

Skip to main content