Solved

MSSQL$Sharepoint service is Stopped -- AGAIN !?

Posted on 2009-07-02
2
640 Views
Last Modified: 2012-05-07
A little over a month ago, my SBS 2003 server was unable to start the Sharepoint services. Based on the responses from this forum, I followed the recommendation to de-install and re-install Sharepoint services, apply all the patches, etc.  It was working fine from May 31 until yesterday.  Suddenly, at 8:04 am, the MSSQL$Sharepoint service stopped and everytime I try to start it, it generates the same database error as it was a month ago.  I get the floowing error every 5 seconds (again). Why would this error suddenly return ?   We're not really using any Sharepoint services features, so would I be safe just deinstalling Sharepoint Services and not reinstalling ?

Event Type:      Error
Event Source:      Windows SharePoint Services 2.0
Event Category:      None
Event ID:      1000
Date:            7/2/2009
Time:            9:55:51 AM
User:            N/A
Computer:      xyzSERVER
Description:
#50070: Unable to connect to the database STS_Config on xyzSERVER\SharePoint.  Check the database connection information and make sure that the database server is running.

 
0
Comment
Question by:adladladl
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 143

Expert Comment

by:Guy Hengel [angelIII / a3]
ID: 24773382
can you post the ERRORLOG file of your sql server instance?
it should be in the LOG folder of that named instance software folder.
0
 

Accepted Solution

by:
adladladl earned 0 total points
ID: 24787599
I already :un-installed" SHarepoint services 'cause I was getting tired of all the errors being logged so the ERRORLOG is gone.
But, last time I had this error, this was the contents of the ERRORLOG:

2009-03-11 21:46:54.68 server    Microsoft SQL Server  2000 - 8.00.2055 (Intel X86)
 Dec 16 2008 19:46:53
 Copyright (c) 1988-2003 Microsoft Corporation
 Desktop Engine (Windows) on Windows NT 5.2 (Build 3790: Service Pack 1)
2009-03-11 21:46:54.68 server    Copyright (C) 1988-2002 Microsoft Corporation.
2009-03-11 21:46:54.68 server    All rights reserved.
2009-03-11 21:46:54.68 server    Server Process ID is 7780.
2009-03-11 21:46:54.68 server    Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\LOG\ERRORLOG'.
2009-03-11 21:46:54.81 server    SQL Server is starting at priority class 'normal'(4 CPUs detected).
2009-03-11 21:46:55.04 server    SQL Server configured for thread mode processing.
2009-03-11 21:46:55.04 server    Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2009-03-11 21:46:55.10 spid3     Starting up database 'master'.
2009-03-11 21:46:58.00 spid3     0 transactions rolled back in database 'master' (1).
2009-03-11 21:46:58.00 spid3     Recovery is checkpointing database 'master' (1)
2009-03-11 21:46:59.48 server    Using 'SSNETLIB.DLL' version '8.0.2039'.
2009-03-11 21:46:59.48 spid5     Starting up database 'model'.
2009-03-11 21:46:59.64 spid3     Server name is 'xyzSERVER\SHAREPOINT'.
2009-03-11 21:46:59.64 spid3     Skipping startup of clean database id 4
2009-03-11 21:46:59.64 spid3     Skipping startup of clean database id 5
2009-03-11 21:46:59.64 spid3     Skipping startup of clean database id 6
2009-03-11 21:46:59.64 spid3     Skipping startup of clean database id 7
2009-03-11 21:47:01.26 server    SQL server listening on Shared Memory.
2009-03-11 21:47:01.26 server    SQL Server is ready for client connections
2009-03-11 21:47:01.42 spid5     Clearing tempdb database.
2009-03-11 21:47:03.42 spid5     Starting up database 'tempdb'.
2009-03-11 21:47:03.76 spid3     Recovery complete.
2009-03-11 21:47:04.34 spid3     Cannot validate object 'master'.'dbo'.'sp_ActiveDirectory_Obj'.
2009-03-11 21:47:04.35 spid3     Database 'master' has invalid schema.
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I've often see, or have been asked, the question about the difference between the Exchange 2010 SP1 version, available as part of Small Business Server (SBS) 2011, and the “normal” Exchange 2010 SP1 Standard. The answer to the question is relativ…
Because virtualization becomes more and more common, and, with Microsoft Hyper-V included in Windows Server at no additional costs, and, most server hardware nowadays is more than capable of running a physical Small Business Server (SBS) 2008 or 201…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question