![]() ![]() 09:42:06.99 Server Using dynamic lock allocation. Reinstall sqlctr.ini for this instance, and ensure that the instance login account has correct registry permissions. 09:42:06.95 Server Performance counter shared memory setup failed with error -1. SQL Server performance counters are disabled. 09:42:06.95 Server Error in mapping SQL Server performance object/counter indexes to object/counter names. This is an informational message no user action is required. 09:42:06.78 Server SQL Server is starting at normal priority base (=7). 09:42:06.78 Server -l C:\Program Files (x86)\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\mastlog.ldf 09:42:06.78 Server -e C:\Program Files (x86)\Microsoft SQL Server\MSSQL.2\MSSQL\LOG\ERRORLOG 09:42:06.78 Server -d C:\Program Files (x86)\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\master.mdf 09:42:06.78 Server Registry startup parameters: This is an informational message only no user action is required. 09:42:06.78 Server This instance of SQL Server last reported using a process ID of 1340 at 09:26:16 (local) 08:26:16 (UTC). ![]() 09:42:06.78 Server Logging SQL Server messages in file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL.2\MSSQL\LOG\ERRORLOG'. 09:42:06.78 Server Authentication mode is MIXED. The SQL Server (DVTEL) service could not be started. ![]() The SQL Server (DVTEL) service is starting. ![]() For more info, review the system event log. On starting the server from the configuration manager: Could not start the SQL Server (DVTEL) on Local Computer. Running sqlcmd -S DVTEL (where DVTEL is one of the SQL Server Services found in Configuration Manager) fails with a connection timeout. Running sqlcmd and typing SELECT * FROM sys.configurationsp (return) (as per link 1) results in no output. I have found plenty of instructions by Googling the error message (see below) such as this and this, but they all seem to involve being able to run SQL commands in the first place. I have a MS SQL 2005 Server which is refusing to start and for which I don't have a password (including the 'sa' password), apparently because the master database is corrupt (see log). Apologies for any duplication but I feel like I'm falling at the first hurdle. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |