Unable to start MSSQLSERVER service on SQL 2005 1

[mgale1]

Dear Tek-tips,

I am trying to run SQL Server 2005 Evaluation Edition on Windows Server 2003 Entreprise Edition SP1.

Until yesterday everything was running fine but today I am unable to start the MSSQLSERVER service. The Analysis Services Service and the Integration Services Service starts up fine - but annoyingly not the MSSQLSERVER service. None of my colleagues can think of any environmental changes that may have caused the service to stop and not restart.

I have tried starting the service under both the local system account and under a dedicated account (local Administrator) but neither work.

The SQL Server Error log gives me this information.
--------------------------------------------------------
2006-02-02 09:58:29.68 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Evaluation Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

2006-02-02 09:58:29.68 Server (c) 2005 Microsoft Corporation.
2006-02-02 09:58:29.68 Server All rights reserved.
2006-02-02 09:58:29.68 Server Server process ID is 4320.
2006-02-02 09:58:29.68 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2006-02-02 09:58:29.68 Server This instance of SQL Server last reported using a process ID of 5624 at 2/2/2006 9:57:13 AM (local) 2/2/2006 9:57:13 AM (UTC). This is an informational message only; no user action is required.
2006-02-02 09:58:29.68 Server Registry startup parameters:
2006-02-02 09:58:29.68 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2006-02-02 09:58:29.68 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2006-02-02 09:58:29.68 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2006-02-02 09:58:29.70 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2006-02-02 09:58:29.70 Server Detected 4 CPUs. This is an informational message; no user action is required.
2006-02-02 09:58:29.85 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.
2006-02-02 09:58:29.88 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2006-02-02 09:58:30.92 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2006-02-02 09:58:30.92 Server Database Mirroring Transport is disabled in the endpoint configuration.
2006-02-02 09:58:30.92 spid5s Starting up database 'master'.
2006-02-02 09:58:31.06 spid5s SQL Trace ID 1 was started by login "sa".
2006-02-02 09:58:31.09 spid5s Starting up database 'mssqlsystemresource'.
2006-02-02 09:58:31.29 spid5s Server name is 'NMR044BRADBS370'. This is an informational message only. No user action is required.
2006-02-02 09:58:31.29 spid9s Starting up database 'model'.
2006-02-02 09:58:31.37 spid9s Clearing tempdb database.
2006-02-02 09:58:31.73 Server A self-generated certificate was successfully loaded for encryption.
2006-02-02 09:58:31.73 Server Error: 17182, Severity: 16, State: 1.
2006-02-02 09:58:31.73 Server TDSSNIClient initialization failed with error 0x7e, status code 0x60.
2006-02-02 09:58:31.73 Server Error: 17182, Severity: 16, State: 1.
2006-02-02 09:58:31.73 Server TDSSNIClient initialization failed with error 0x7e, status code 0x1.
2006-02-02 09:58:31.73 Server Error: 17826, Severity: 18, State: 3.
2006-02-02 09:58:31.73 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.
2006-02-02 09:58:31.73 Server Error: 17120, Severity: 16, State: 1.
2006-02-02 09:58:31.73 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.

--------------------------------------------------------

Can anyone offer any help on this? Anyone seem this before and found a way to resolve it. Please help.

Thanks in advance.

 

[mutley1]

Have you used a VIA protocoal anywhere? If you have and don't need it, remove it.

http://msdn2.microsoft.com/ms191229.aspx

Also, have any access rights changed for the account running the SQL Service (as in might not have access to data files if it has changes at all since last start of services).

Good Luck,

M.

 

[mgale1]

Thanks mutley1,

I switched off the VIA protocol and the service started first time of asking.

You're a STAR!!!!

 

[mutley1]

You're welcome,

M.