Exchange 2007 Sp1 SCC: failed to un setup /upgradecms
Dear all, after upgrading the two node of the cluster i'm going to launch: setup /upgradecms I see this on both nodes of the cluster: Welcome to Microsoft Exchange Server 2007 Unattended Setup Preparing Exchange Setup The following server roles will be upgraded Clustered Mailbox Server Performing Microsoft Exchange Server Prerequisite Check Clustered Mailbox Role Checks ......................... FAILED The installed version of the Exchange Server 2007 clustered mailbox server role is the same or newer than the version you are attempting to upgrade to. Installed version: 8.1.240.6 The Exchange Server Setup operation did not complete. For more information, visit http://support.microsoft.com and enter the Error ID. Exchange Server setup encountered an error. Then if I start the cluster group I see this error on event log: Event Type:ErrorEvent Source:MSExchange ClusterEvent Category:ExRes Event ID:1025Description:Exchange Information Store Instance (EXMS01): The Clustered Mailbox Server needs to be upgraded before it can be brought online. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Data: 0000: d7 13 00 00 ... Doing start from the Exchange Console same error: Summary: 1 item(s). 0 succeeded, 1 failed. Elapsed time: 00:00:00 Start 'EXMS01'Failed Error:The Start-ClusteredMailboxServer operation failed the version check. Node EXCLS01 has version 8.1.10240.6, while clustered mailbox server EXMS01 - Exchange 2007 Mailbox Cluster has version 8.0.10685.25. Exchange Management Shell command attempted:start-ClusteredMailboxServer -Identity 'EXMS01' Elapsed Time: 00:00:00 Any idea on how to upgrade Custered Mailbox Server? Thanks, Yan
December 12th, 2007 2:27am

i have exactly the same problem.Did you ever find a solution how to fix this?If so, please let me know. I can't find Information about that problem.Thanks in advance.Christian
Free Windows Admin Tool Kit Click here and download it now
January 15th, 2008 11:31pm

Hello everybody, i have the problem, too. Does nobody knows the solution? It`s very important, because we develop SP1 in a big company, which needs a redundant mail system. Without a functionally cluster, we will get critical problems in the next time. Please help us. Thanks, Nico
January 16th, 2008 5:55pm

What procedure did you guysfollow performingthe SP1 upgrades on the physicalnodes (Not refering to the CMS upgrade)? Per http://technet.microsoft.com/en-us/library/bb691226.aspxfor SCC upgrades of SP1: 1. Upgrade Passive Node (Node B)with SP1. 2. RestartNode B. 3. FromNode Bwhich is now the Active, Stop CMS resources and move CMS to Node B. 3. Upgrade CMS. 4. Repeat steps 1 on Node A. This is the high level from the article. Hope this helps!
Free Windows Admin Tool Kit Click here and download it now
January 16th, 2008 10:29pm

I did exacty the steps from the technet article. After wehad the problems described earlier. Any suggestions? thanks, Christian
January 17th, 2008 5:38pm

I had exactly the same problem and I actually had a Sev A open with MS re this. We finally got it sorted, what we had to do was edit the properties on the CMS object using ADSI edit in AD. The problem is (with ours anyway) was that although the install went through Ok it didnt find an object it was looking for on a DC, if still however continued to up the version of the CMS as part of the SP1 install. The following steps work:- 1. Ensure you have a RTM version of Exchange 2007 handy and ideally a test lab where you can at least compare RTM versions of CMS with Exchange 2007 SP1 CMS. 2. removed Exchange 2007 from cluster Node A and then did a reinstall from RTM CD. Then failed CMS back to Node A. 3. removed Exchange 2007 from cluster Node B and then did a reinstall from RTM CD.. 4. Edited CMS object in AD Configuration container to in effect revert version back to Exchange 2007 RTM CMS and not Sp1. There are quite a few version numbers associated with the CMS. 5. Applied Exchange 2007 Sp1 to Node A of cluster. 6. Applied Exchange 2007 Sp1 to NodeB of cluster 7. Then did the upgrade CMS swicth, this worked. However what I would say is if this is a production system get a Microsoft call open, they went through the pain with me and I would imagine they could sort you out very qucikly, it's not for the faint hearted. HTH
Free Windows Admin Tool Kit Click here and download it now
January 18th, 2008 2:48pm

can you tell me the exact attributes which had to be changed back to RTM Version? Is it serialnumber? I have an attribut called serialnumber with this value: Version 8.1 (Build 3240.6) Should I change this value? Or do you mean that attributes are missing? Thanks, Christian
January 18th, 2008 3:51pm

Problem is solved. All you need to do is changing the serialnumber attribute on the CMS Container to: Version 8.0 (Build 0685) Then setup /upgradecms will complete successfull. Hope I could help all people who have this problem.
Free Windows Admin Tool Kit Click here and download it now
January 18th, 2008 4:08pm

Had this identical problem myself. It was late on a Friday night so I gave up, tried it again on Monday morning and it worked fine. I'm wondering if I was making changes too quickly and AD hadn't replicated...
January 19th, 2008 8:53pm

Just had this same issue with the EX071SP1 to SP2 upgrade. Proper syntax is: setup.com /cmsupgrade
Free Windows Admin Tool Kit Click here and download it now
September 22nd, 2009 9:31am

Good first time heard about it...... Good Learning
September 22nd, 2009 4:59pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics