Error Id 5042 Cluster Node Was Not Found
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Cluster Will Not Failover to New Node Previous Versions of Exchange > Exchange Previous Versions - Setup, Deployment, Updates, and Migration Question 0 Sign in to vote I added a new node to my Exchange 2003 SP2 clustered environment. I know that all of my settings are correct. When I try to failover one of my virtual groups, it gives me an error: An error occurred attempting to move the ' ' group. The cluster node was not found. Error ID: 5042 (000013b2). Here is the quirky part to this whole problem. My virtual exchange groups won't failover, but my cluster and quorum group failover with no problem. Can someone help me resolve this issue? Thanks in advance Batekhead Monday, October 13, 2008 4:09 PM Reply | Quote Answers 0 Sign in to vote Issue description: Exchange group cannot failover to another node, but cluster group and quorum group failover well Exchange group may have all nodes as potential owners, but how about the resources in it? They need to get this all matched up. “Properties” of exchange group lists all nodes, and each resource within that group needs to match that list as well. Please check them all, unmatched lists will cause the same symptom: Use
Join INTELLIGENT WORK FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from https://social.technet.microsoft.com/Forums/exchange/en-US/5e89b723-7732-487e-98d6-892f25ef9b51/cluster-will-not-failover-to-new-node?forum=exchangesvrdeploylegacy Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Microsoft: Microsoft Cluster Server (MSCS) Forum at Tek-Tips HomeForumsMIS/ITOperating Systems - Hardware IndependentMicrosoft: Microsoft Cluster Server (MSCS) Forum Cluster won't http://www.tek-tips.com/viewthread.cfm?qid=1358362 failover - error 5042 thread737-1358362 Forum Search FAQs Links MVPs Cluster won't failover - error 5042 Cluster won't failover - error 5042 umbletech (IS/IT--Management) (OP) 18 Apr 07 22:21 Win2003 sp1 ent cluster exchange 2003 sp2AAP clusterJust installed a number of patches on my passive node - node 3 was on node1.Then tried to failover evs1 to it.Got:an error occurred while trying to move group evs1-the node was not found error id 5042. Re-started the cluster service on node 3.Moved evs2 over to it with no problem.Then moved evs1 over to node 2 to see if it was a problem with the group.That worked.Then tried to move evs2 back to node 1. Got the same error. I searched the hotfix list http://support.microsoft.com/kb/923830 for 5042 - nothing.I can't see anything relevant in the system or application logs.Is clusdiag worth a shot?Help very much appreciated - a cluster that won't failover isn't too comforting. RE: Cluster won't failover - error 5042 mrdenny (Programmer) 19 Apr 07 01:02 glusdiag probably could
Explained Cluster MOVE Möve Re: Can not Switch to 3rd node: error ID 5042: cluster node was http://microsoft.newsgroups.archived.at/public.sqlserver.clustering/200808/0808284928.html not fo Subject: Re: Can not Switch to 3rd node: error ID 5042: cluster node was not fo Posted by: Geoff N. Hiten (SQLCraftsm…@gmail.com) Date: Fri, 29 Aug 2008 Are you able to move the cluster group to node 3? If so, take all resources offline inthe SQL group, move them error id to Node 3 and bring them online one at a time to see which resource fails. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "George"