You are getting this error in the Application log of the computer that is running Sharepoint Services 3: “The database WSS_Content on ComputerName\Microsoft##SSEE is not accessible to missing Windows Internal Database signatures”

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

This is because SPWebService instance failed to finish provisioning and the status of that service is marked as provisioning.

Workaround:

1. Start -> Run type cmd and OK
2. cd C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>
3. Start & Stop the SPWebService

• stsadm -o provisionservice -action stop -servicetype spwebservice -servicename “”

• stsadm -o provisionservice -action start -servicetype spwebservice -servicename “”

4. After the SPWebService started

• stsadm -o upgrade -forceupgrade -inplace
• psconfig -cmd upgrade -inplace b2b -wait -force

There are also cases reporting that the issue can occur prior to installation of GroupBoard KB installation

Ref: http://support.microsoft.com/?id=941678