Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Service getting stopped due to improper clustering configuration Expand / Collapse
Author
Message
Posted Monday, September 9, 2013 8:06 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, January 15, 2014 10:56 PM
Points: 35, Visits: 277
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>) 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)"?
Post #1492799
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse