• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1350
  • Last Modified:

Unable to load SQL database after restore from tape

I have had to restore a Windows 2000 server from backup tape using Veritas Backup Exec 9.1. I have two hard drive partitions (C and T). Since restoring both partitions and the system state I am now receiving the following problems. I am running Windows 2000 Standard Server and SQL 2000.

Windows Services displays the following
SQLServerAgent - will not start at all
MSSQLServer - is in stopping state
MSSQL$Redmap - is in stopping state
BackupClientSvc - is in stopping state

Enterprise Manager lists both SQL databases (Local and DT2000Server\Redmap) however both are stopped and showing Connection Failed, check SQL Server Registration Properties.

I have found that I do not have any .BAK files for the above databases, however I do appear to have the corresponding mdf and ldf files if that is of any help in restoring.

Any help with getting these databases up and running again would be appreciated.
0
HPT_4214
Asked:
HPT_4214
  • 3
  • 2
2 Solutions
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
to start troubleshooting:
please check the errorlog file in sql server \log folder
please check the nt eventlog for errors of sql server

0
 
HPT_4214Author Commented:
The latest ErrorLog file is listed below.

2007-08-09 18:45:43.87 server    Copyright (C) 1988-2002 Microsoft Corporation.
2007-08-09 18:45:43.87 server    All rights reserved.
2007-08-09 18:45:43.87 server    Server Process ID is 1176.
2007-08-09 18:45:43.87 server    Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG'.
2007-08-09 18:45:44.04 server    SQL Server is starting at priority class 'normal'(1 CPU detected).
2007-08-09 18:46:03.20 server    SQL Server configured for thread mode processing.
2007-08-09 18:46:03.26 server    Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2007-08-09 18:46:08.57 spid3     Starting up database 'master'.
2007-08-09 18:46:13.40 spid3     0 transactions rolled back in database 'master' (1).
2007-08-09 18:46:13.70 spid3     Converting database 'master' from version 536 to the current version 539.
2007-08-09 18:46:14.10 spid3     Error: 50000, Severity: 22, State: 127
2007-08-09 18:46:14.10 spid3     sp_msupg_upgradecatalog detected inconsistent versioning!.
2007-08-09 18:46:14.14 spid3     Process ID 3 has raised user error 50000, severity 22. SQL Server is terminating this process.
2007-08-09 18:46:14.20 server    Using 'SSNETLIB.DLL' version '8.0.2039'.
2007-08-09 18:46:14.20 spid5     Cannot open database 'master' version 536. Upgrade the database to the latest version.
2007-08-09 18:46:14.21 spid6     Cannot open database 'master' version 536. Upgrade the database to the latest version.
2007-08-09 18:46:14.21 spid6     Failed setup PSS for system task thread. Terminating server.: Operating system error ???????? encountered.
2007-08-09 18:46:14.23 spid3     Server name is 'DT2000SERVER'.
2007-08-09 18:46:15.46 spid8     Starting up database 'msdb'.
2007-08-09 18:46:15.71 server    SQL server listening on 192.192.173.5: 1433.
2007-08-09 18:46:15.71 server    SQL server listening on 127.0.0.1: 1433.
2007-08-09 18:46:15.82 spid9     Starting up database 'wataystone'.
2007-08-09 18:46:15.87 spid10    Starting up database 'Watkins Taylor Stone'.

The only entry I can see in the NT Eventviewer listed below.
Sourve Service Control manager - Event ID 7001
The SQLSERVERAGENT service depends on the MSSQLSERVER service which failed to start because of the following error:
%%0


0
 
HPT_4214Author Commented:
After attempting to start the Local database in Enterprise Manager am receiving the following not sure if this is of any further assistance.

A connection could not be established to (Local).
Reason: SQL Server does not exist of access denied.
ConnectionOpen(Connect())..
Please verify the SQL Server is running and check your SQL Server registration properties (by right0-clicking on the (Local) node) and try again.

Still the services do not start, however all have now changed to the stopped state, not stopping as per earlier post.
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
>2007-08-09 18:46:13.70 spid3     Converting database 'master' from version 536 to the current version 539.
>2007-08-09 18:46:14.10 spid3     Error: 50000, Severity: 22, State: 127
>2007-08-09 18:46:14.10 spid3     sp_msupg_upgradecatalog detected inconsistent versioning!.

the problem is described by this: the master database (at least) had a bad version, for example you need to reapply a hotfix that was installed previously.
you could also check to rebuild the master database (check out the rebuild master database tool)
0
 
natokaCommented:
this problem can also be caused by insufficient access rights for the account that runs the server.

Perhaps starting in single user mode might help you see the problem, like:
http://www.cryer.co.uk/brian/sqlserver/howto_start_single_user_mode.htm
0
 
HPT_4214Author Commented:
We solved this issue ourselves with help from a software supplier, issue was related to their software. Thanks for all your help.
0

Featured Post

Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now