Sunday, January 20, 2013 8:55 AM
i have a problem on my production SQL SERVER due to this error raised randomly on SQL SERVER 2008 Cluster and caused failover to node B
DCOM was unable to communicate with the computer"clustername.domain.local" using any of the configured protocols<o:p></o:p>
and this error is hitting every sec and can't figuer the reason .. ..
- Windows Server 2008 IA
- SQL Server 2008 x64 SP 2 cluster active\active
any clue would be appricaited
More error in the cluster events ..
The description for Event ID 1069 from source Microsoft-Windows-FailoverClustering cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.Even ID 1069
- Edited by SQL Kitchen Sunday, January 20, 2013 8:57 AM
Sunday, January 20, 2013 2:42 PMAnswerer
Sunday, January 20, 2013 5:31 PM
The error indicates to me that there was perhaps a brief period problematic connectivity to node a on your cluster -which indecently may be real connectivity issues or simply the fact that the node was having other issues that impacted its connectivity.
Your next steps are to search throught the event logs (app, security and system) around the time of the failover and also to search through your cluster logs to get more detail. Dont forget to use event log filtering to eradicate some of the unwanted noise.
Also as a final note, dont forget to check the sql fci event logs.
If the issue is related to corruption as the error also points to, then you may have to look towards repair or rebuild.
Regards,Contact me through (twitter|blog|SQLCloud)
Please click "Propose As Answer" if a post solves your problem
or "Vote As Helpful" if a post has been useful to you
Watch my sessions at the PASS Summit 2012
Monday, January 21, 2013 10:51 AM
thanks for your replies ,
regarding monitiring tools i have 2 diff tool connect to cluste to collect events (RSA envision & SCOM 2007 ),
the number of generated evets are huge actually , do you think this may be the root cause of this issue ..
one more thing , we had similar connectivity issue with backup and the the third tool (symantec backup) suddenly stoped connect to cluster and the problem solved after update the client with FQN of the master server
- Edited by SQL Kitchen Monday, January 21, 2013 10:51 AM
Friday, February 22, 2013 7:16 PM
Since this looks to be a Non-SQL Issue, you can take a look at the links below which were provided by Sean Liming on Windows Forum