Partager via

Troubleshooting WSS Event 1000 DB Connectivity Problems

  • Article

Troubleshooting WSS Event 1000 DB Connectivity Problems

 I recently needed to trigger some data collection on a SQL Server when my Share Point Web Front End started experiencing the dreaded error as follows:

Type: Error
Source: Windows SharePoint Services 2.0
Category: None
Event ID: 1000
Description:
#50070: Unable to connect to the database ConfigurationDatabase. Check the database connection information and make sure that the database server is running.

For more information, see https://support.microsoft.com/default.aspx?scid=kb;en-us;833183

I used the following steps to help out.

1. Create Remote.vbs as follows:

========== remote.vbs [ Exec remote process via WMI]================

strComputer = WScript.Arguments.Item(0)

strCommand = WScript.Arguments.Item(1)

Set objWMIService = GetObject("winmgmts:" _

   & "{impersonationLevel=impersonate}!\\" & strComputer & _

   "\root\cimv2:Win32_Process")

errReturn = objWMIService.Create(strCommand,null,null,intProcessID)

If errReturn = 0 Then

    WScript.Echo strCommand & " was started with a process ID of " _

    & intProcessID & "."

Else

    WScript.Echo strCommand & " could not be started due to error " & _

    errReturn & "."

End If

========== remote.vbs [ Exec remote process via WMI]================

2. Create WFE_InvokeSomethingOnSQL.CMD on WFE which should be something like this

cscript remote.vbs MYDBSERVER C:\DoSomethingOnSQL.cmd

3. Create DoSomethingOnSQL.CMD on SQL on the drive and path specified in WFE_InvokeSomethingOnSQL.CMD:

REM ========[ BEGIN DoSomethingOnSQL.CMD ]==============================

REM ==================================================================

REM

REM

SET MYLOG=MyLog.Log

ECHO ================================================== >> %MYLOG%

ECHO Something Run at %DATE%%TIME% >> %MYLOG%

ECHO ================================================== >> %MYLOG%

Something.exe /someargument /TEMP.LOG

TYPE TEMP.LOG >> %MYLOG%

REM

REM

REM ========[ END DoSomethingOnSQL.CMD ]==============================

REM ================================================================

4. Add the trigger event on the Web Front End.

eventtriggers /create /s WFE-SERVER /tr Event1000Trigger /l APPLICATION /eid 1000 /t ERROR /so "Windows SharePoint Services 2.0" /d "Trigger to call DoSomthing.CMD to be run on SQL Server when Event ID 1000 is encountered" /tk “C:\WFE_InvokeSomethingOnSQL.CMD”

Hope this helps you as well!

- Keith

Comments

  • Anonymous
    August 31, 2005
    The comment has been removed
  • Anonymous
    September 07, 2005
    Jonathan,

    Steps 1,2 and 4 are placed on the WFE's
    Step 3 is for the remote SQL Server
    (Sorry I didn't make that clear :)

    The end result, is that it's still on-going :)
    There are multiple reasons for this, and some could just be network hiccups, etc.

    There certainly not "Nothing" :) Somethings going on in your environment...The "Nothing" may be network hiccups, etc...but they should still be investigated...Especially if the on happening all the time.

    The config I'm testing on is a large farm, but these could happen on any configuration.
  • Anonymous
    March 30, 2006

    EventTriggers is my new best friend.  
    Many moons ago, I blogged about using EventTriggers...
  • Anonymous
    May 23, 2006
    Chris Gideon has posted a great article with a list of the most common reasons why you'll see the dreaded...