FAILED UPDATE SP2 EXCHNAGE
- Hello,
I have a problem with the cluster (SCC) Exchange 2007 SP1 on Server 2008
SP2.
System until recently has always worked well, both on a node
is another.
Today I tried (following the procedure Technet) to update Exchange 2007
with Service Pack 2.
May I have 2 Problems:
1) in the middle of the installation procedure has been blocked with
following error: The Windows Cluster service encountered an error during
function ClusterOpenEnum
2) now when I try to move resources on this node to store information
not part
A thousand thanks in advance
All Replies
- Hello,
I have a problem with the cluster (SCC) Exchange 2007 SP1 on Server 2008
SP2.
System until recently has always worked well, both on a node
is another.
Today I tried (following the procedure Technet) to update Exchange 2007
with Service Pack 2.
May I have 2 Problems:
1) in the middle of the installation procedure has been blocked with
following error: The Windows Cluster service encountered an error during
function ClusterOpenEnum
2) now when I try to move resources on this node to store information
not part
A thousand thanks in advance- Merged byJames-LuoMSFT, ModeratorMonday, October 05, 2009 5:43 AMduplicate
Hi
here it is go through it .
http://blogs.technet.com/timmcmic/archive/2009/01/21/the-windows-cluster-service-encountered-and-error-during-function-opencluster.aspx
regards
SYED Arsalan.
syed.arsalanHow’s the issue currently? Does the link from Syed work for you?
Resources:
Upgrading Clustered Mailbox Servers to Exchange 2007 SP1 or SP2
Hello,
thanks for the support.
I have already performed the recommended steps in the link above, but nothing we can do that update to sp2 still fail.
The strange thing is that despite not complete successfully update all files in the folder in exchnage program files have been changed.
Now when I go into the Exchange Managenmt Console and run the command move to passive clustered mailbox node I receive this error:
Error:
The installation on node 'Node2' is inconsistent.
ConfiguredVersion = 8.1.240.6, 8.2.176.2 = UnpackedVersion. An upgrade might not
have completed successfully.
Exchange Management Shell command attempted:
move-ClusteredMailboxServer-Identity 's50'-MoveComment 'test'
-TargetMachine 'Node2'
Thanks- Make sure your sites/services lists the correct subnet for each site. Make sure you have adequate rights to perform the same
Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3| What’s the edition of the management tool that you tried to perform CMS movement, 32-bit or 64-bit? I assume that exchange servers are all 64-bit, really?
If you are using 32-bit management tools, the issue will relate to 32-bit registry. The 32-bit application will use 32-bit registry when you run it against the 64-bit servers. The Move-ClusteredMailboxServer will check both unpackedversion, configuredversion, and fail to set the unpackedversion key.
Workarounds:
1. Manually add the Unpacked data keys in the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Exchange\v8.0. This workaround should be low impact, as this only needs to be done for major builds and not for incremental or rollup builds. If future service packs are applied this key may also need to be updated
2. Manage the servers on the 64-bit machines
- Proposed As Answer byJames-LuoMSFT, ModeratorFriday, October 09, 2009 1:29 AM
- Any update?
Hello,
thanks for the support.
I have already performed the recommended steps in the link above, but nothing we can do that update to sp2 still fail.
The strange thing is that despite not complete successfully update all files in the folder in exchnage program files have been changed.
Now when I go into the Exchange Managenmt Console and run the command move to passive clustered mailbox node I receive this error:
Error:
The installation on node 'Node2' is inconsistent.
ConfiguredVersion = 8.1.240.6, 8.2.176.2 = UnpackedVersion. An upgrade might not
have completed successfully.
Exchange Management Shell command attempted:
move-ClusteredMailboxServer-Identity 's50'-MoveComment 'test'
-TargetMachine 'Node2'
Thanks
Have a look in the following registry key HKLM\software\exchange\v8.0\mailboxrole, if you have an action value and a watermark value this will indicate that the exchange install failed or was interrupted. The watermark value is used to install exchange from where it left off so perform the install again...- hi,
i do have the same problem.
i dont have the key "v8.0" in "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Exchange\".
do i have to copy the whole "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0" tree into the "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Exchange\" tree?
kind regards
reinhard
- hi,
i copied now the whole subtree from "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0" to "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Exchange\" but it did not help.
i deletet the "watermark" dword as well but it did not help.
are there any updates for this???
i can not remove that software and can not upgrade and it is not working in the current state.
i don't want to install the whole cluster server again with all his services.
i need help, please.
regards
reinhard
I:\download\sp2>Setup.com /mode:Upgrade Welcome to Microsoft Exchange Server 2007 Unattended Setup Preparing Exchange Setup The following server roles will be upgraded Mailbox Role Management Tools Performing Microsoft Exchange Server Prerequisite Check Mailbox Role Checks ......................... COMPLETED Configuring Microsoft Exchange Server Mailbox Server Role ......................... FAILED The Windows Cluster service encountered an error during function ClusterOpenEnum. The Exchange Server Setup operation did not complete. For more information, visit http://support.mic rosoft.com and enter the Error ID. Exchange Server setup encountered an error. I:\download\sp2>
