Event ID 4523 - ClusSvc. Help
- Hi all
I'm getting the following message in event viewer ever 5 minutes.
Event ID: 4523
Source: ClusSvc
Category: Membership Mgr
Majority Node Set resource has failed a status check for file share '\\Tom\mns_fsw_dir_exch64'. The error code was '53'. Please ensure that the file share is configured properly and that the cluster service account has write permission on the file share.
Now i do understand the error and i know why i'm getting it.
Tom no longer exists, it was removed (not sure why) before i got here. Tom comes up in exchange 2007 console in client access and hub transport but obviously doesn't do anything. I've looked through the cluster admin setting for Tom but i've not found anything.
Any ideas how to fix this problem?
Thanks
Jason
Answers
You can verify if the Tom exists in AD by using ADSI Editor
Expand to Configuration Container->CN=Configuration, DC= Domain_Name ,DC=com->CN=Services ->CN=Microsoft Exchange->CN= Your_Organization_Name->CN=Administrative Groups ->CN= Your_Administrative_Group_Name->CN=Servers
Under the “CN=Servers” node, you can see the installed exchange servers. This is the place to remove the server if the server hasn’t been removed successfully and the configuration entries still in the AD. Please do a full backup for the server and AD if you want to perform this method
And, the recommended method is to use RecoverServer switch to recover the Tom server, and then remove it with regularly way again.
James Luo
TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx)
If you have any feedback on our support, please contact tngfb@microsoft.com- Marked As Answer byJames-LuoMSFT, ModeratorFriday, November 13, 2009 1:23 AM
- Proposed As Answer byJames-LuoMSFT, ModeratorTuesday, November 10, 2009 2:37 AM
All Replies
- In the "cluster core resources" area of the Failover Cluster Management mmc you'll find the FSW resource. Delete or modify it here.
But if you DO delete it, ensure you create another one or change the quorum model as necessary.
Mike Crowley A+, Network+, Security+, MCT, MCSE, MCTS, MCITP: Enterprise Administrator / Messaging Administrator
- Proposed As Answer byMike Crowley Tuesday, November 03, 2009 1:16 PM
- An error 4523 is "The network path was not found." So it's having trouble connecting to the share. Recheck the steps you took to set it up and ensure that you granted the proper permissions.
probabaly you need to configure the share againhttp://technet.microsoft.com/en-us/library/bb124922.aspx
http://support.microsoft.com/kb/921181
Raj - Rajnish, thanks for the followup to many of my threads! :) If you'll read the comments above, Jason clearly states that the computer in question is no longer around.
- lol you've lost me :)
I can get into cluster Administrator. i'm not sure how to access the failover cluster management mmc
Please not that tom isn't on the cluster as a machines, its not any where apart from on exchange in 2 windows and in this error message.
Jason - Aha, is this Windows 2003? Windows 2008 has the failover cluster management mmc 2003 its called cluster administrator. Point is, within the cluster xxx mmc there is an option for quorum settings. If your cluster uses a file share wittness (FSW) then you'll have a resource defined for the file share itself. If this server is gone (tom) you can simply delete the resource and that error will go away. BUT you should have a FSW if you have a 2 node cluster without shared quorum disk. So you'll want to configure another server to act as the FSW if this is the case.
- oh dear :)
well i've looked through every setting and tom is listed nowhere! On "file share" tom isn't listed and the "local quorum" settings don't list tom either.
stupid error but something somewhere is sending it - so under "file share" you have another server listed, and this resource is online? (let me see if i can find a 2003 cluster to look at and post back).
I assume that your cluster is CCR, please correct me if I have misunderstood it
Please refer this article to check your current FSW setting
Also, please run ExBPA against the CMS for health check
- Right well i've been messing.
Tom is basically nowhere except for in exchange. In exchange management console it is listing Tom under the server configuration and is in client access and hub transport. Tom is in these 2 places along with the server that we do have which runs the webmail (harry). I'm guessing that tom used to provide the owa services either with harry or on its own but was just not removed properly when it was removed.
I'm guessing that if i remove tom from exchange all together then i won't get the error message anymore but i have no idea how to remove it!
Jason You can verify if the Tom exists in AD by using ADSI Editor
Expand to Configuration Container->CN=Configuration, DC= Domain_Name ,DC=com->CN=Services ->CN=Microsoft Exchange->CN= Your_Organization_Name->CN=Administrative Groups ->CN= Your_Administrative_Group_Name->CN=Servers
Under the “CN=Servers” node, you can see the installed exchange servers. This is the place to remove the server if the server hasn’t been removed successfully and the configuration entries still in the AD. Please do a full backup for the server and AD if you want to perform this method
And, the recommended method is to use RecoverServer switch to recover the Tom server, and then remove it with regularly way again.
James Luo
TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx)
If you have any feedback on our support, please contact tngfb@microsoft.com- Marked As Answer byJames-LuoMSFT, ModeratorFriday, November 13, 2009 1:23 AM
- Proposed As Answer byJames-LuoMSFT, ModeratorTuesday, November 10, 2009 2:37 AM
- Any update?
James Luo
TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx)
If you have any feedback on our support, please contact tngfb@microsoft.com
