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

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 compress the files on the drive that your instance is running on - not to be recommended as a rule.
When you attempt to start the instance the System event log gives the service specific error 3417 as you've seen.
The Application event log was a bit more useful for me - "The file "D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf" is compressed but does not reside in a read-only database or filegroup. The file must be decompressed."
I decompressed the files and the service started fine - something to consider.
Mar
From http://www.developmentnow.com/g/118_2006_10_0_0_840331/Cant-start-SQL-on-2005-Cluster.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com|||thanks for upstai
From http://www.developmentnow.com/g/118_2006_10_0_0_840331/Cant-start-SQL-on-2005-Cluster.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com

Can't re-attach database to sql server 2000

Hi,

My last post was terminated without the error message. To recap, I am unable to re-attach a database to a SQL server 2000 server after I detached it and attached it to a 2005 Server. When I detached it from the 2005 server and tried to re-attach it to the 2000 server I got the following error message:

" Error 5123: CREATE FILE encountered operating system error 5(Access denied) while attempting to create the physical file ..."

I tried using both the 2005 Server Management Studio and the 2000 Enterprise manager to do the re-attachement but got the same error message.

Any ideas on how I can reattach the files?

Thanks for your help.

Ken McLean

You can′t. During attaching the database to the SQL 2k5, the internal structure is migrated to SQL Server 2005 specific requirements which are not understanable for the SQL 2000 instance. This is one way only.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de