Showing posts with label error3417. Show all posts
Showing posts with label error3417. Show all posts

Tuesday, March 27, 2012

Can't start SQL on 2005 Cluster

The SQL Server (MSSQLSERVER) service terminated with service-specific error
3417 (0xD59).
This is what I get on my 2005 Cluster when I try to start SQL on one of the
nodes. Another node is running fine, no problems what so ever.
Please help...Check out:
http://msdn2.microsoft.com/en-us/library/aa337262.aspx
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:185F94E0-9E8E-4048-A25B-7311CCDC9D96@.microsoft.com...
The SQL Server (MSSQLSERVER) service terminated with service-specific error
3417 (0xD59).
This is what I get on my 2005 Cluster when I try to start SQL on one of the
nodes. Another node is running fine, no problems what so ever.
Please help...|||I've found that a good way to inadvertently generate this error is to compre
ss the files on the drive that your instance is running on - not to be recom
mended as a rule.
When you attempt to start the instance the System event log gives the servic
e specific error 3417 as you've seen.
The Application event log was a bit more useful for me - "The file "D:\Progr
am Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf" is compressed b
ut does not reside in a read-only database or filegroup. The file must be de
compressed."
I decompressed the files and the service started fine - something to conside
r.
Mark
From http://www.developmentnow.com/g/118...>
-Cluster.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com