Sql Server 2005 not starting

Raj Thilak

Hi,
      I have my web application with backend as Sql Server 2005 CTP(Yukon).
Initially It works well.
I updated some security settings to the OS Windows Server 2003 and restarted the machine.
Now the Sql Server is not starting.When I manually started It logs error as
follows.

2005-10-13 03:39:57.85 Server      UpdateUptimeRegKey: Operating system error 5(Access is denied.) encountered.
2005-10-13 03:39:57.85 Server      Registry startup parameters:
2005-10-13 03:39:57.85 Server      -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2005-10-13 03:39:57.85 Server      -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2005-10-13 03:39:57.85 Server      -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2005-10-13 03:39:57.85 Server      Error: 17113, Severity: 16, State: 1.
2005-10-13 03:39:57.85 Server      Error 3(The system cannot find the path specified.) occurred while opening file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf' to obtain configuration information at startup. An invalid startup option might have caused the error. Verify your startup options, and correct or remove them if necessary.
2005-10-13 03:39:57.85 Server      Error: 17053, Severity: 16, State: 1.
2005-10-13 03:39:57.85 Server      UpdateUptimeRegKey: Operating system error 5(Access is denied.) encountered.
dinator (MS DTC). This is an informational message only. No user action is required.

In the event viewer I noticed the following error Message

1&2. Event ID 17182: TDSSNIClient initialization failed with error 0x7e, status code 0x3a. < xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

3. Event ID 17826: 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.

4. Event ID 17120: 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 help me
Thanks in Advance,
Raj Thilak

MarcD

Error 3(The system cannot find the path specified.) occurred while opening file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf' to obtain configuration information at startup. An invalid startup option might have caused the error. Verify your startup options, and correct or remove them if necessary.

Start there

Raj Thilak

Marc
Thank you for your reply .
I tried with Startup options by specifying it in commandline

sqlservr.exe -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG

that error has gone.I got the following error log

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

2005-10-13 06:30:57.93 spid5s Starting up database 'master'.

2005-10-13 06:30:58.01 spid5s SQL Trace ID 1 was started by login "sa".

2005-10-13 06:30:58.01 spid5s Starting up database 'mssqlsystemresource'.

2005-10-13 06:30:58.10 spid5s Server name is "#####". This is an informational message only. No user action is required.

2005-10-13 06:30:58.12 spid9s Starting up database 'model'.

2005-10-13 06:30:58.18 spid9s Clearing tempdb database.

2005-10-13 06:30:58.22 Server The certificate was successfully loaded for encryption.

2005-10-13 06:30:58.22 Server Error: 17182, Severity: 16, State: 1.

2005-10-13 06:30:58.22 Server TDSSNIClient initialization failed with error 0x7e, status code 0x60.

2005-10-13 06:30:58.22 Server Error: 17182, Severity: 16, State: 1.

2005-10-13 06:30:58.22 Server TDSSNIClient initialization failed with error 0x7e, status code 0x1.

2005-10-13 06:30:58.22 Server Error: 17826, Severity: 18, State: 3.

2005-10-13 06:30:58.22 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.

2005-10-13 06:30:58.22 Server Error: 17120, Severity: 16, State: 1.

2005-10-13 06:30:58.22 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.

----------------------------------------------------------------------------------------------------------
Any Solution for this.
Thanks
Thilak

Laurentiu Cristofor

What security options did you update on the machine Did you change the service account What is the SQL Server version printed by select @@version

Thanks
Laurentiu

sqlaviolette

I ran into the same problem. My service account did not have proper access rights. I changed it to LocalService and it works just fine. I s'pose the sql account needs read/write access to that data directory.

Good luck!

megachuck1

Just wanted to pass this on, as I was running into the same problem - arrrrgggh!

On another forum someone suggested that the VIA Protocol should be disabled (unless of course you use VIA Hardware.)

I did this and the MSSQL Server immediately connected!

Not even really sure what VIA is!

Cheers

Aseem Bansal

Thanks for your post.

I had the same problem and solution was to disable VIA.

I also don't know what is VIA :)

Regards

Aseem Bansal

Benjamin123

VIA seems to be the issue with me also.

just disabled it and I was off

Kamii47

Yah I have also Correct it by disabling VIA.
Could any body of microsoft sql server 2005 team explain why we are getting this error.

Nan Tu

VIA is special network interface that can perform faster and lighter weighted RDMA than TCP. It is used for high end server. It requires special VIA hardware and libraries to work. What you saw in the errorlog indicates VIA is enabled but via library fails to be loaded. If you do not have VIA setup for your machine. You shouldn't enable VIA.

-Nan

Kamii47

Then tell me how could I have a VIA setup.
I have sql server 2005 developer edition install on my machine.

longle37

Thanks guys...! I disabled VIA and everything seems to be fine now...

tobor

I turned this thing (VIA) on inadvertantly while trying to figure this out and it stopped my Sql Server 2005 ....
as soon as I disabled the VIA protocol again ... all was well, it started again without a hitch.

Greg P

yup, turned off via and a ok. thanks, greg

Sivaji Raju

Check what network protocols are enabled for SQL Server in the SQL Configuration Manager application. If the VIA protocol is enabled disable it and then try starting the SQL Server service again.

Hope this helps,
Sivaji Raju

Sql Server 2005 not starting

Re: Sql Server 2005 not starting

Re: Sql Server 2005 not starting

Re: Sql Server 2005 not starting

Re: Sql Server 2005 not starting

Re: Sql Server 2005 not starting

Re: Sql Server 2005 not starting

Re: Sql Server 2005 not starting

Re: Sql Server 2005 not starting

Re: Sql Server 2005 not starting

Re: Sql Server 2005 not starting

Re: Sql Server 2005 not starting

Re: Sql Server 2005 not starting

Re: Sql Server 2005 not starting

Re: Sql Server 2005 not starting