January 19, 2010 at 9:15 am
I am testing a disaster recovery process but am unable to restart any 2008 systems in single user mode so that I can restore the master db. The sql server instance is stopped when I issue the command. I have tried this on three systems so far with no luck please help.
D:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn>sqlservr.ex
e -m
2010-01-19 11:09:35.82 Server Error: 17058, Severity: 16, State: 1.
2010-01-19 11:09:35.82 Server initerrlog: Could not open error log file ''.
Operating system error = 3(The system cannot find the path specified.).
2010-01-19 11:09:36.12 Server Error: 17058, Severity: 16, State: 1.
2010-01-19 11:09:36.12 Server initerrlog: Could not open error log file ''.
Operating system error = 3(The system cannot find the path specified.).
2010-01-19 11:09:36.42 Server Error: 17058, Severity: 16, State: 1.
2010-01-19 11:09:36.42 Server initerrlog: Could not open error log file ''.
Operating system error = 3(The system cannot find the path specified.).
2010-01-19 11:09:36.72 Server Error: 17058, Severity: 16, State: 1.
2010-01-19 11:09:36.72 Server initerrlog: Could not open error log file ''.
Operating system error = 3(The system cannot find the path specified.).
2010-01-19 11:09:37.03 Server Error: 17058, Severity: 16, State: 1.
2010-01-19 11:09:37.03 Server initerrlog: Could not open error log file ''.
Operating system error = 3(The system cannot find the path specified.).
2010-01-19 11:09:37.33 Server Error: 17058, Severity: 16, State: 1.
2010-01-19 11:09:37.33 Server initerrlog: Could not open error log file ''.
Operating system error = 3(The system cannot find the path specified.).
2010-01-19 11:09:37.63 Server Error: 17058, Severity: 16, State: 1.
2010-01-19 11:09:37.63 Server initerrlog: Could not open error log file ''.
Operating system error = 3(The system cannot find the path specified.).
2010-01-19 11:09:37.93 Server Error: 17058, Severity: 16, State: 1.
2010-01-19 11:09:37.93 Server initerrlog: Could not open error log file ''.
Operating system error = 3(The system cannot find the path specified.).
2010-01-19 11:09:38.24 Server Error: 17058, Severity: 16, State: 1.
2010-01-19 11:09:38.24 Server initerrlog: Could not open error log file ''.
Operating system error = 3(The system cannot find the path specified.).
2010-01-19 11:09:38.54 Server Error: 17058, Severity: 16, State: 1.
2010-01-19 11:09:38.54 Server initerrlog: Could not open error log file ''.
Operating system error = 3(The system cannot find the path specified.).
January 19, 2010 at 10:05 am
I take it you restored to another server? Are the drive letters available the same on the restored server as what was on the original?
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
January 20, 2010 at 12:29 am
January 20, 2010 at 6:43 am
I copied the parameters from the SQL Configuration Manager and now I get so other weird messages.
D:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn>sqlservr.exe -m -sMSSQLSERVER -d"D:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\master.mdf" -e"D:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG" -l"D:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\mastlog.ldf"
2010-01-20 08:22:00.45 Server Microsoft SQL Server 2008 (SP1) - 10.0.2746.0
(X64)
Nov 9 2009 16:37:47
Copyright (c) 1988-2008 Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: ) (VM)
2010-01-20 08:22:00.45 Server (c) 2005 Microsoft Corporation.
2010-01-20 08:22:00.45 Server All rights reserved.
2010-01-20 08:22:00.45 Server Server process ID is 3840.
2010-01-20 08:22:00.45 Server System Manufacturer: 'Microsoft Corporation', System Model: 'Virtual Machine'.
2010-01-20 08:22:00.45 Server Authentication mode is MIXED.
2010-01-20 08:22:00.45 Server Logging SQL Server messages in file 'D:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2010-01-20 08:22:00.45 Server This instance of SQL Server last reported using a process ID of 2004 at 1/20/2010 8:21:49 AM (local) 1/20/2010 1:21:49 PM UTC). This is an informational message only; no user action is required.
2010-01-20 08:22:00.45 Server Error: 17053, Severity: 16, State: 1.
2010-01-20 08:22:00.45 Server UpdateUptimeRegKey: Operating system error 5(Access is denied.) encountered.
2010-01-20 08:22:00.45 Server Command Line Startup Parameters:
-m
-s MSSQLSERVER
-d D:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\master.mdf
-e D:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l D:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2010-01-20 08:22:00.47 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2010-01-20 08:22:00.47 Server Detected 1 CPUs. This is an informational message; no user action is required.
2010-01-20 08:22:00.50 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2010-01-20 08:22:00.50 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 08:22:00.52 Server Node configuration: node 0: CPU mask: 0x0000000000000001 Active CPU mask: 0x0000000000000001. 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 08:22:00.54 Server Database Mirroring Transport is disabled in the endpoint configuration.
2010-01-20 08:22:00.54 spid7s Warning ******************
2010-01-20 08:22:00.54 spid7s SQL Server started in single-user mode. This an informational message only. No user action is required.
2010-01-20 08:22:00.55 spid7s Starting up database 'master'.
2010-01-20 08:22:00.61 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2010-01-20 08:22:00.71 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2010-01-20 08:22:00.77 spid7s SQL Trace ID 1 was started by login "sa".
2010-01-20 08:22:00.88 spid7s Starting up database 'mssqlsystemresource'.
2010-01-20 08:22:00.89 spid7s The resource database build version is 10.00.2746. This is an informational message only. No user action is required.
2010-01-20 08:22:01.40 spid7s Error: 15466, Severity: 16, State: 1.
2010-01-20 08:22:01.40 spid7s An error occurred during decryption. RegOpenKeyEx of "Software\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSS
QLServer" failed.
2010-01-20 08:22:01.43 spid7s Failed to check for new installation or a renamed server at startup. The logic for this check has failed unexpectedly. Run setup again, or fix the problematic registry key.
2010-01-20 08:22:01.43 Server Error: 17182, Severity: 16, State: 1.
2010-01-20 08:22:01.43 Server TDSSNIClient initialization failed with error 0x5, status code 0x51. Reason: Unable to configure MDAC-compatibility Named Pipes protocol pipe name in registry. Access is denied.
2010-01-20 08:22:01.43 spid9s Starting up database 'model'.
2010-01-20 08:22:01.43 Server Error: 17182, Severity: 16, State: 1.
2010-01-20 08:22:01.43 Server TDSSNIClient initialization failed with error 0x5, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Access is denied.
2010-01-20 08:22:01.43 Server Error: 17826, Severity: 18, State: 3.
2010-01-20 08:22:01.43 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2010-01-20 08:22:01.44 Server Error: 17120, Severity: 16, State: 1.
2010-01-20 08:22:01.44 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
January 20, 2010 at 9:27 am
2010-01-20 08:22:00.45 Server UpdateUptimeRegKey: Operating system error 5(Access is denied.) encountered.
2010-01-20 08:22:01.43 spid7s Failed to check for new installation or a renamed server at startup. The logic for this check has failed unexpectedly. Run setup again, or fix the problematic registry key.
2010-01-20 08:22:01.43 Server Error: 17182, Severity: 16, State: 1.
2010-01-20 08:22:01.43 Server TDSSNIClient initialization failed with error 0x5, status code 0x51. Reason: Unable to configure MDAC-compatibility Named Pipes protocol pipe name in registry. Access is denied.
This tells me the account being used for the service does not have write/modify permissions to the registry in some way. It wants to update the UpdateUptimeRegKey.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
January 21, 2010 at 3:52 am
Hi ,
Stop all the services related to SQL. Eg: SQL server,Agent,Analysis,Integration etc.
Got to Command promt.
Type as :
Step 1 : net stop mssqlserver
Step 2 : net start mssqlserver /f /T3608
Mssqlserver is your Instancename.
Once the Services started , type SQLCMD to check the connectivity as a single user mode.
Hope it will help you.
Regards,
Saravanan
January 21, 2010 at 6:12 am
I faced this EXACT issue two weeks ago. The resolution I found myself was that when you goto CMD prompt do not just open it, right click and say RUN AS ADMINISTRATOR. Then start SQL Server as you state. It will work that way. Security on WIn2008 is tighter and you have to do the RUN AS ADMIN for it to work correctly.
January 21, 2010 at 6:24 am
Thanks that was the problem.
January 21, 2010 at 6:34 am
Markus,
We do all activities in administrator login. So i dint get this issue. Any way thks.
Regards,
Saravanan
January 21, 2010 at 6:57 am
I know. The ID I was using is a full admin to the server too so I did not understand. However, when you open it up as RUN AS Admin it works.
March 7, 2013 at 2:02 pm
Markus (1/21/2010)
I faced this EXACT issue two weeks ago. The resolution I found myself was that when you goto CMD prompt do not just open it, right click and say RUN AS ADMINISTRATOR. Then start SQL Server as you state. It will work that way. Security on WIn2008 is tighter and you have to do the RUN AS ADMIN for it to work correctly.
This worked for me, too. Thanks!!
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply