November 23, 2011 at 3:23 pm
Hello.
I'm currently trying to get a instance of sharepoint up and running after a server recovery. All the files have been restored including permissions. The MSSQL$SHAREPOINT service starts and then stops straight away. The error log looks like this
2011-11-23 22:07:12.15 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 2)
2011-11-23 22:07:12.16 server Copyright (C) 1988-2002 Microsoft Corporation.
2011-11-23 22:07:12.18 server All rights reserved.
2011-11-23 22:07:12.18 server Server Process ID is 7544.
2011-11-23 22:07:12.18 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\LOG\ERRORLOG'.
2011-11-23 22:07:12.21 server SQL Server is starting at priority class 'normal'(2 CPUs detected).
2011-11-23 22:07:12.37 server SQL Server configured for thread mode processing.
2011-11-23 22:07:12.37 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2011-11-23 22:07:12.44 spid4 Starting up database 'master'.
2011-11-23 22:07:12.57 spid4 1 transactions rolled back in database 'master' (1).
2011-11-23 22:07:12.57 spid4 Recovery is checkpointing database 'master' (1)
2011-11-23 22:07:12.69 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2011-11-23 22:07:12.69 spid5 Starting up database 'model'.
2011-11-23 22:07:12.71 spid4 Server name is 'INTEGRITY\SHAREPOINT'.
2011-11-23 22:07:12.74 spid8 Starting up database 'msdb'.
2011-11-23 22:07:12.76 spid9 Starting up database 'STS_Config'.
2011-11-23 22:07:12.76 server SQL server listening on Shared Memory.
2011-11-23 22:07:12.76 server SQL Server is ready for client connections
2011-11-23 22:07:12.76 spid10 Starting up database 'STS_INTEGRITY_1'.
2011-11-23 22:07:12.98 spid8 1 transactions rolled back in database 'msdb' (4).
2011-11-23 22:07:12.99 spid10 1 transactions rolled back in database 'STS_INTEGRITY_1' (6).
2011-11-23 22:07:13.01 spid10 Recovery is checkpointing database 'STS_INTEGRITY_1' (6)
2011-11-23 22:07:13.01 spid9 1 transactions rolled back in database 'STS_Config' (5).
2011-11-23 22:07:13.02 spid5 1 transactions rolled back in database 'model' (3).
2011-11-23 22:07:13.02 spid8 Recovery is checkpointing database 'msdb' (4)
2011-11-23 22:07:13.02 spid5 Recovery is checkpointing database 'model' (3)
2011-11-23 22:07:13.02 spid9 Recovery is checkpointing database 'STS_Config' (5)
2011-11-23 22:07:13.34 spid5 Clearing tempdb database.
2011-11-23 22:07:14.46 spid5 Starting up database 'tempdb'.
2011-11-23 22:07:15.07 spid4 Recovery complete.
2011-11-23 22:07:15.12 spid4 System database checksum file has invalid signature.
I've searched around the internet and cant find any solution. I have tried restoring the files in C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\Data with no luck. It is an SBS server and there are other databases running, so I don't want to restore the other folders as those DB's are starting and running.
Any help or suggestions would be greatly appreciated!
Thanks
James
November 24, 2011 at 2:37 am
You can try this: http://dbaspot.com/sqlserver-tools/226265-checksum-problem-system-database.html
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 24, 2011 at 3:51 am
Thanks for the reply! I have looked at that post already. I have tried restoring the files from backup. The problem is that they are from windows backup and not a SQL backup. I'm guessing that this is why I'm having the issues. Is there anyway that the database can be recovered?
November 24, 2011 at 3:51 am
Thanks for the reply! I have looked at that post already. I have tried restoring the files from backup. The problem is that they are from windows backup and not a SQL backup. I'm guessing that this is why I'm having the issues. Is there anyway that the database can be recovered?
November 24, 2011 at 5:15 am
I'd suggest Microsoft support, but SQL 2000 has been out of support for 3 years or so.
Maybe reinstall SQL and reattach the user databases, but I don't know if that will help. Probably a good idea at this point if you get a competent SQL consultant in to help.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply