Search This Blog

Sunday, 15 July 2012

Sharepoint WSS 3.0 - Microsoft##SSEE is not accessible to missing Windows Internal Database signatures.

I woke up Saturday morning to find that our Sharepoint WSS 3.0 site was no longer available, so here is what you can do if you have the same issue. The process is documented in this Microsoft KB article

HTTP 404 Error


So here is the problem with my companyweb site, a HTTP 404 page not found error.

Event Logs


A quick check of the event logs finds this message. Event ID 6800 The database ShareWebDB on SBIZ\Microsoft##SSEE is not accessible to missing Windows Internal Database signatures. What this really means is that a Windows Security Update for Sharepoint has been applied but it cannot complete untl the Sharepoint Configuration Wizard is ran, so this leaves you in limbo. This is why we use monitoring to tell when our websites are offline. We use GFI Remote Management, they are a UK business and we think their software is awesome so go find out.



The MIcrosoft KB states we need to use the STSADM tool, this is located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensitons\12\bin

Stop Provisioning


The first step is to stop the provisioning service. stsadm -o provisionservice -action stop -servicetype spwebservice -servicename ""

The second step is to start the provisioning service. stsadm -o provisionservice -action start -servicetype spwebservice -servicename ""

Upgrade the Sharepoint Site


Now the Sharepoint Site is ready to be upgraded. psconfig -cmd upgrade -inplace b2b -wait -force

Is it one of those days?


As ever, things do not always go to plan. So when I tried to upgrade the Sharepoint Site, I was presented with this error. What this means is that the upgrade failed and we should consult the logs to find out why. Well it turns out what you need to do is restart the Windows Internal Database Services first.

GUI Version


I ran the GUI version of the Sharepoint Configuration Wizard so I could see each step and this time the upgrade completed.

Confirm Upgrade


Once the upgrade is completed, you can confirm this in the Windows Event Log, the event ID is 101.


  1. I recently stumbled across the exact same problem and i followed this solution, however it did not work for me after that, so i kept searching and found this other solution:

    1. Stop the Windows SharePoint Services Timer service.
    2. On the SharePoint Server where Central Administration Site is hosted browse to C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\
    3. Move all the xml files to another location.
    4. Also backup the cache.ini file. Then Edit the cache.ini and replace the current value with "1".
    5. Restart the Windows SharePoint Services Timer service. New xml files will start appearing in the guid folder.
    6. Verify the cache.ini now contains its previous value (or verify that the value is no longer "1"; any non-1 value is fine).
    7. Run the command from the sharepoint server "stsadm -o setproperty -pn command-line-upgrade-running -pv no" (without quotes)
    8. Run the command from the sharepoint server "stsadm -o execadmsvcjobs" (without quotes)
    9. Run the command from the sharepoint server "psconfig -cmd upgrade -inplace b2b -wait -force" (without Quotes)

    Rerstart the Windows Internal Database Service and then ran the wizard again. And it worked!

  2. Thanks for the additional Jimmy, one size nevers fits all does it? So its good to get another approach!


  3. The command line upgrade worked perfect for me thank you for the help!!!

  4. Worked for me too - many thanks