SharePoint Services 3.0 Event ID 3670

I was suffering of event id 3670 & failure Audit id 18456 since last 2 days and wanted to get away from it. I was searching all the forums and blogs regarding that and couldn't find a resolution for the error. All the blogs and forums are mentioning to reinstall and attach the content DB.


My Scenario is,

Installed Windows SharePoint Services 3.0 with SP2
Installed SQL Management Studio for DB administration
Windows 2003 Standard R2 with SP 2
.Net Framework 3.5


I have installed the above mentioned applications and service packs for document archival in WSS 3.0. The default installation path for the WSS 3.0 DBs are in your windows folder location where C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data

So I wanted to change the DB location and I used SQL management studio to change it. I have copied all the DBs from C:\ drive to my F:\ drive where it has more space to accommodate the DB growth. After copying the DBs, by opening the SQL management studio, I have attached all the DBs (Please stop the Windows SharePoint Timer Services from Services before copying or attaching the DBs) except SharePoint_AdminContent_XXXXXXXX.

Once the attachment of DBs (without SharePoint_AdminContent_XXXXXXXX), I started the Windows SharePoint Timer Services and start working on my WSS 3.0 sites and uploading documents.

Later some days, I just want to do some admin task in Central Administration Web Site and I couldn’t access the site at all. Then I went through the Event viewer and found out following Errors loaded in my Event Viewer;

SQL Database 'SharePoint_Config_af70289d-9151-473c-b0df-8fe74e809ac0' on SQL Server instance 'SERVER\Microsoft##SSEE' not found. Additional error information from SQL Server is included below.
Cannot open database "SharePoint_Config_af70289d-9151-473c-b0df-8fe74e809ac0" requested by the login. The login failed.

With Failure Event as following

Event Type: Failure Audit
Event Source: MSSQL$MICROSOFT##SSEE
Event Category: (4)
Event ID: 18456
Date: 4/21/2009
Time: 2:37:36 PM
User: PBTF\apbyrum
Computer: THOTH
Description:
The description for Event ID ( 18456 ) in Source ( MSSQL$MICROSOFT##SSEE ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: PBTF\APByrum, [CLIENT: ].

My Event viewer was full with above errors and wanted a resolution badly.

Solution

• Detach the 'SharePoint_Config_af70289d-9151-473c-b0df-8fe74e809ac0 DB from copied location (from F:\ Drive location). While detaching the DB, please select “Drop Connections” and click OK

• Attach the 'SharePoint_Config_af70289d-9151-473c-b0df-8fe74e809ac0 DB from original location (from C:\Window location)

• Attach the SharePoint_AdminContent_97c95945-3cec-49c7-8eb9-25bb2a6f5b98

After doing above tasks and I could be able to access the Central Administration site and there were no errors in my event id.

Hope the above information will be useful for guys who need some tips to troubleshoot. This above resolution works for my scenario without a doubt.

Cheers !!!

How to connect SQL Embedded Edition using SQL Management Studio

If you have installed WSS 3.0 with Embedded SQL edition and you wanted to get connected to the instances with MS SQL Managemen Studio for manageing the DB, Please follow the below steps to reach there.

Here is how we connect to the Embedded SQL instance:

We can create a Server Alias for the "MICROSOFT##SSEE" named instance.

1. Run "cliconfg" on the box from the command line or from Start --> Run

2. In the "SQL Server Client Network Utility" console, click the Alias tab.

3. Create a new Server alias.

4. Server alias: \MICROSOFT##SSEE

5. Replace with the exact server.
Network libraries: Named Pipes
Server name: .\MICROSOFT##SSEE
Pipe name: \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query

6. Then open SQL 2005 management studio, input \MICROSOFT##SSEE as Server Name.

Now you can use SQL 2005 management studio to connect to the SQL data for SharePoint site successfully.

Hope above information is helpful

Cheers !!