SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Service getting stopped due to improper clustering configuration


SQL Service getting stopped due to improper clustering configuration

Author
Message
viduvs
viduvs
SSC Journeyman
SSC Journeyman (98 reputation)SSC Journeyman (98 reputation)SSC Journeyman (98 reputation)SSC Journeyman (98 reputation)SSC Journeyman (98 reputation)SSC Journeyman (98 reputation)SSC Journeyman (98 reputation)SSC Journeyman (98 reputation)

Group: General Forum Members
Points: 98 Visits: 284
We had a SQL Server (SQL Server 2005 - Win2K3) deployed on the physical hardware in the clustering environment.
After that the Clustered nodes migrated to the virtual environment..
Recently we had some storage issue so that infrastructure team did not start the cluster service on 2nd node..
So SQL Server was running on 1st node without clustering (though the clustering was not removed).
A day after that I could see SQL Service was abruptly stopped.
No trace of any error in SQL Server error logs, however the following error could be seen in the events logs,

"The SQL Server (<Name of the instance>Wink service terminated with service-specific error 3449 (0xD79). and the SQL service has been stopped"

I could see the following errors in the event logs before the above error:

- The system failed to flush data to the transaction log. Corruption may occur.
- {Delayed Write Failed} Windows was unable to save all the data for the file . The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
- The Cluster Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
- Cluster service suffered an unexpected fatal error at line 1766 of source module <name of the file>. The error code was 6.
- Cluster node <name fo the 2nd node> was removed from the active server cluster membership. Cluster service may have been stopped on the node, the node may have failed, or the node may have lost communication with the other active server cluster nodes.
- The join of node <name fo the 2nd node> to the server cluster timed out and was aborted.

Can SQL Server stop functioning because of improper configuration of clustering environment or can it be caused because of any other reason?

Can anyone please tell what can cause the error "3449 (0xD79)"?
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search