Link to home
Start Free TrialLog in
Avatar of vijyant
vijyant

asked on

cluster issue

One of my DHCP cluster is crash after seeing the MPS report i could see event id 1000 source clusrv

and in cluster log i could see
an unexpected fatal error
at line 954 of source module D:\nt\private\cluster\service\dm\dmsync.c. The error code was -1073741811.
00000d08.00000cf8::2006/06/19-19:09:18.390


any idea i need to do RCA on this
ASKER CERTIFIED SOLUTION
Avatar of pjedmond
pjedmond
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of engineer_dell
engineer_dell

The Domain Local Policy may be overwriting the computer's local policy and local permissions may be getting overwritten. You should add that node to the Domain security policy and you should be able to reset the quorum and get back in business.

This link has got the answer but solution is not free, you may want to look at it,

http://www.eventid.net/display.asp?eventid=1000&eventno=3737&source=CluSvc&phase=1

Regards,

Engineer_Dell  
Hey,

Try this,

The Cluster database is a hive in the registry located at:
HKEY_LOCAL_MACHINE\Cluster
The file for the Cluster registry hive is located on disk by default at the following location:
%SystemRoot%\Cluster\Clusdb
Note that because the Cluster key is a separate hive, you cannot use the Emergency Repair Disk (ERD) to recover Clusdb.

Try each of the following items to fix the problem: • Check the file permissions for the Clusdb file. Make sure that the domain account under which the Cluster runs has full access.
• Verify that the Clusdb file is not set to Read-Only.
• Restore the file from a backup. (Note that this file is cluster specific.)
• If one of the nodes is still working, uninstall Microsoft Cluster Server (MSCS) from and reinstall MSCS to the failed node. Choose Join an existing cluster. This procedure may cause problems with some cluster resources. You may have to re-create the resources or reinstall programs. Contact Microsoft Product Support Services for assistance with reinstalling Microsoft products.

http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q217/1/57.asp&NoWebContent=1

Good Luck !!

Engineer_Dell
I think that you'll find that the error has occurred after the dminit element of the communication (Which appears to have been successful). The error is occurring in the synchroniasation process based on the fact the error states that it is in:

source module D:\nt\private\cluster\service\dm\dmsync.c