all groups > sql server connect > august 2007 >
You're in the

sql server connect

group:

unable to connect or start service



unable to connect or start service Mike
8/19/2007 11:09:06 AM
sql server connect: Background... Server raid failed, rebuilt raid ran chkdsk but now I am
unable to run SQL service.

I've tried to manually start service but receive the following message

The MSSQLSERVER service on the local computer started and then stopped. Some
services stop automatically if they have no work to do.

Here's all I have in the error logs

2007-08-19 10:56:39.98 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

2007-08-19 10:56:39.99 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-08-19 10:56:39.99 server All rights reserved.
2007-08-19 10:56:39.99 server Server Process ID is 1812.
2007-08-19 10:56:39.99 server Logging SQL Server messages in file
'f:\MSSQL\log\ERRORLOG'.
2007-08-19 10:56:40.01 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2007-08-19 10:56:40.15 server SQL Server configured for thread mode
processing.
2007-08-19 10:56:40.18 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2007-08-19 10:56:40.23 server Attempting to initialize Distributed
Transaction Coordinator.
2007-08-19 10:56:42.29 spid4 Starting up database 'master'.
2007-08-19 10:56:42.31 spid4 Error: 5172, Severity: 16, State: 15.
2007-08-19 10:56:42.31 spid4 Error: 5173, Severity: 16, State: 1.
2007-08-19 10:56:42.31 spid4 Error: 5180, Severity: 22, State: 1.


As result of this error I also receive thousands of entries for the
sharepoint server

#50070 unable to connect to database.

I would greatly appreciate any direction on how to fix this issue... Monday
morning is going to be nasty with a down server.


Thank you
Re: unable to connect or start service Vera Noest
8/19/2007 2:03:17 PM
The description for error 5172 is:
"The header for file '%ls' is not a valid database file header."

I'm afraid that your master database is corrupt.
Have a look at this thread on MSDN for a similar issue:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1346541&SiteID=
1

error 5173:
"One or more files do not match the primary file of the database. If
you are attempting to attach a database, retry the operation with the
correct files. If this is an existing database, the file may be
corrupted and should be restored from a backup."

error 5180:
"Could not open FCB for invalid file ID %d in database '%.*ls'."
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Mike" <mnelson@windermere.com> wrote on 19 aug 2007 in
microsoft.public.sqlserver.connect:

[quoted text, click to view]
AddThis Social Bookmark Button