January 20, 2010 at 5:12 am
Hi,
I tried to move system databases but end up in errors.
Everything i have document in a word file and i have attached.
Can anyone give me a fix ?
Thanks in Advance
January 20, 2010 at 5:58 am
You haven't given the most important information - the SQL error log. It's just a text file, no need for SQL to be running to access it. Find the error log (errorlog and errorlog.1) and see what they say.
Also, the event that you highlighted in event viewer is not from SQL. It's irrelevant.
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
January 21, 2010 at 2:10 am
Hi Gila,
Here is what is there in ERRORLOG. How to bring back my instance.
Any suggestions?
ERRORLOG.TXT
2010-01-21 13:06:30.61 Server Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (Intel X86)
Mar 29 2009 10:27:29
Copyright (c) 1988-2008 Microsoft Corporation
Standard Edition on Windows NT 5.1 <X86> (Build 2600: Service Pack 3)
2010-01-21 13:06:30.61 Server (c) 2005 Microsoft Corporation.
2010-01-21 13:06:30.61 Server All rights reserved.
2010-01-21 13:06:30.62 Server Server process ID is 4820.
2010-01-21 13:06:30.62 Server Authentication mode is MIXED.
2010-01-21 13:06:30.62 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2008\MSSQL\Log\ERRORLOG'.
2010-01-21 13:06:30.62 Server This instance of SQL Server last reported using a process ID of 916 at 1/20/2010 5:33:14 PM (local) 1/20/2010 12:03:14 PM (UTC). This is an informational message only; no user action is required.
2010-01-21 13:06:30.64 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2008\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2008\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2008\MSSQL\DATA\mastlog.ldf
2010-01-21 13:06:30.92 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2010-01-21 13:06:30.92 Server Detected 2 CPUs. This is an informational message; no user action is required.
2010-01-21 13:06:31.13 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2010-01-21 13:06:31.32 Server Node configuration: node 0: CPU mask: 0x00000003 Active CPU mask: 0x00000003. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2010-01-21 13:06:31.37 spid7s Starting up database 'master'.
2010-01-21 13:06:31.58 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQL2008'.
2010-01-21 13:06:31.61 spid7s SQL Trace ID 1 was started by login "sa".
2010-01-21 13:06:31.62 spid7s Starting up database 'mssqlsystemresource'.
2010-01-21 13:06:31.68 spid7s The resource database build version is 10.00.2531. This is an informational message only. No user action is required.
2010-01-21 13:06:31.90 spid7s Server name is 'MACHINENAME\SQL2008'. This is an informational message only. No user action is required.
2010-01-21 13:06:31.90 spid10s Error: 913, Severity: 16, State: 6.
2010-01-21 13:06:31.90 spid10s Could not find database ID 3. Database may not be activated yet or may be in transition. Reissue the query once the database is available. If you do not think this error is due to a database that is transitioning its state and this error continues to occur, contact your primary support provider. Please have available for review the Microsoft SQL Server error log and any additional information relevant to the circumstances when the error occurred.
2010-01-21 13:06:31.90 spid10s Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.
2010-01-21 13:06:31.90 spid10s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
ERRORLOG.1.TXT
2010-01-20 17:32:58.98 Server Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (Intel X86)
Mar 29 2009 10:27:29
Copyright (c) 1988-2008 Microsoft Corporation
Standard Edition on Windows NT 5.1 <X86> (Build 2600: Service Pack 3)
2010-01-20 17:32:58.98 Server (c) 2005 Microsoft Corporation.
2010-01-20 17:32:58.98 Server All rights reserved.
2010-01-20 17:32:58.98 Server Server process ID is 916.
2010-01-20 17:32:58.98 Server Authentication mode is MIXED.
2010-01-20 17:32:58.98 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2008\MSSQL\Log\ERRORLOG'.
2010-01-20 17:32:58.99 Server This instance of SQL Server last reported using a process ID of 5464 at 1/20/2010 5:24:31 PM (local) 1/20/2010 11:54:31 AM (UTC). This is an informational message only; no user action is required.
2010-01-20 17:32:58.99 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2008\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2008\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2008\MSSQL\DATA\mastlog.ldf
2010-01-20 17:32:58.99 Server Command Line Startup Parameters:
/T 3608
2010-01-20 17:32:59.02 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2010-01-20 17:32:59.02 Server Detected 2 CPUs. This is an informational message; no user action is required.
2010-01-20 17:32:59.22 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2010-01-20 17:32:59.40 Server Node configuration: node 0: CPU mask: 0x00000003 Active CPU mask: 0x00000003. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2010-01-20 17:32:59.44 Server Database Mirroring Transport is disabled in the endpoint configuration.
2010-01-20 17:32:59.45 spid7s Recovering only master database because traceflag 3608 was specified. This is an informational message only. No user action is required.
2010-01-20 17:32:59.45 spid7s Starting up database 'master'.
2010-01-20 17:32:59.50 spid7s Snapshot isolation or read committed snapshot is not available in database 'master' because SQL Server was started with one or more undocumented trace flags that prevent enabling database for versioning. Transaction started with snapshot isolation will fail and a query running under read committed snapshot will succeed but will resort back to lock based read committed.
2010-01-20 17:32:59.58 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQL2008'.
2010-01-20 17:32:59.60 spid7s SQL Trace ID 1 was started by login "sa".
2010-01-20 17:32:59.61 spid7s Server name is 'MACHINE-1\SQL2008'. This is an informational message only. No user action is required.
2010-01-20 17:32:59.64 spid7s Recovery is complete. This is an informational message only. No user action is required.
2010-01-20 17:33:00.21 Server A self-generated certificate was successfully loaded for encryption.
2010-01-20 17:33:00.26 Server Server is listening on [ 'any' <ipv4> 1229].
2010-01-20 17:33:00.28 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQL2008 ].
2010-01-20 17:33:00.29 Server Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQL2008\sql\query ].
2010-01-20 17:33:00.30 Server Server is listening on [ 127.0.0.1 <ipv4> 1230].
2010-01-20 17:33:00.30 Server Dedicated admin connection support was established for listening locally on port 1230.
2010-01-20 17:33:06.35 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/MACHINE-1.xxxx.xxxx.net:SQL2008 ] for the SQL Server service.
2010-01-20 17:33:06.35 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/MACHINE-1.xxx.xxxx.net:1229 ] for the SQL Server service.
2010-01-20 17:33:06.65 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2010-01-20 17:33:13.83 spid51 Starting up database 'mssqlsystemresource'.
2010-01-20 17:33:13.85 spid51 The resource database build version is 10.00.2531. This is an informational message only. No user action is required.
2010-01-20 17:33:13.90 spid51 Snapshot isolation or read committed snapshot is not available in database 'mssqlsystemresource' because SQL Server was started with one or more undocumented trace flags that prevent enabling database for versioning. Transaction started with snapshot isolation will fail and a query running under read committed snapshot will succeed but will resort back to lock based read committed.
2010-01-20 17:33:14.04 spid51 Clearing tempdb database.
2010-01-20 17:33:14.04 spid51 Error: 913, Severity: 16, State: 8.
2010-01-20 17:33:14.04 spid51 Could not find database ID 3. Database may not be activated yet or may be in transition. Reissue the query once the database is available. If you do not think this error is due to a database that is transitioning its state and this error continues to occur, contact your primary support provider. Please have available for review the Microsoft SQL Server error log and any additional information relevant to the circumstances when the error occurred.
2010-01-20 17:33:14.04 spid51 Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.
2010-01-20 17:33:14.04 spid51 SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2010-01-20 17:33:15.13 Logon Error: 17188, Severity: 16, State: 1.
2010-01-20 17:33:15.13 Logon SQL Server cannot accept new connections, because it is shutting down. The connection has been closed. [CLIENT: <local machine>]
2010-01-20 17:33:15.13 Logon Error: 17188, Severity: 16, State: 1.
2010-01-20 17:33:15.13 Logon SQL Server cannot accept new connections, because it is shutting down. The connection has been closed. [CLIENT: <local machine>]
2010-01-20 17:33:19.95 Server The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/MACHINE-1.xxxx.xxxx.net:SQL2008 ] for the SQL Server service.
2010-01-20 17:33:19.95 Server The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/MACHINE-1.xxxx.xxxx.net:1234 ] for the SQL Server service.
Thank You!
January 21, 2010 at 5:05 am
Looks like model is not where SQL is expecting it to be. Double check what you set model's location to when you moved it and whether the DB really is there. Also check that the SQL Server service account has adequate (full) permissions to directory and file.
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
January 21, 2010 at 5:34 am
Hi, I experieced a similar issue with SQL 2005. Try starting SQL Server in single user mode, detaching the MSDB database, reattach MODEL first, then reattach MSDB. I think the problem is trying to attach both these dbs at once
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply