Bill Baer

Senior Product Marketing Manager (SharePoint), Microsoft Certified Master for SharePoint, Microsoft Corporation

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

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

  • Comments 4
  • Likes

A solution is available to administrators of SharePoint Products and Technologies deployments experiencing the following application event after introducing WSS October public update KB934525.

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: NA
Computer: HOME
Description: The database WSS_Content on HOME\Microsoft##SSEE is not accessible to missing Windows Internal Database signatures.

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 is 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.

Comments
  • I've gotten some questions asked on the hotfix and public update I wanted to address here. Product Support

  • When I try to run

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

    I receive the following error (verbatim):  

    "Unprovision of service  failed. Additional information:  Access denied..  Access denied."

    I am running the command under my admin account.

    Bruce

  • My issues with the KB update/WSS 3.0 were directly related to a prior installation of GroupBoard:  

    GroupBoard KB article: http://support.microsoft.com/?id=941678

    Once I uninstalled GroupBoard, I was able to successfully run the Sharepoint configuration wizard and complete the upgrade...  previously the wizard would fail and all other solutions to the KB update error also failed.

    After configuration/upgrade completely successfully, my user site and admin sites are now displaying correctly.   There seem to be some performance issues but at least the content is there.

    Ironically, I wasn't even using GroupBoard on the earlier site, but I'm happy I was able to resolve this without going through more extensive steps.

  • Hello William,

    Same as Bruce, I got the same Access denied error.

    After the KB934525 our SPS became inaccessible at all..

    Regards,

    mnet

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment