SP2 woes
Installing SP2 failed with the following error: "This role cannot be installed because the following roles are not current: ClientAccessRole MailboxRole UnifiedMessagingRole AdminToolsRole"
Unfortunately by this point it had already disabled all the services and broken lots of things - and there wasn't any roll-back! I was trying to upgrade sp1 ru4 --> sp2.
I had already had an issue with this message: "You cannot resume setup by performing the action "BuildtoBuildUpgrade"". I "fixed" this by deleting the Watermark and Action keys from the HubTransportRole registry key. At least it let the setup continue but then I got into the current mess. In fact it is exactly the same as this guy's post about sp1 - but he doesn't seem to have found a fix: https://msmvps.com/blogs/ehlo/archive/2008/05/06/1614953.aspx
I manually re-enabled all the services. The mailboxes are accessible but it looks like CAS is broken ("Server Error in '/owa' Application"). I thought I might try uninstalling CAS, Hub and Unified Messaging, applying SP2 just with the Mailbox role, and then reinstalling the services - but I can't even uninstall these roles.Exchange Server component Unified Messaging Server Role failed.
Error: Error:
Unable to remove product with code cef60964-21ae-47e0-93c6-611aa8941b7f. Fatal error during installation. Error code is 1603. Last error reported by the .msi package is 'Could not find any previously installed compliant products on the machine for installing this product.'.
Exchange Server component Client Access Role failed.
Error: Error:
Process execution failed with exit code 5.
What can I do about this server? It is in a completely unstable state, and I don't seem to be able to roll back whatever changes the sp2 installation has made. We are considering executing the SCR failover plan at the moment. SCR has only just been installed and this is a rather more intensive "test" than we had in mind!
http://www.wapshere.com/missmiis
Answers
- I think I am probably beyond help on this issue now. So I am going to answer my own question with a warning to others: if you get the "You cannot resume setup by performing the action "BuildtoBuildUpgrade"" error DO NOT delete any Watermark or Action keys. Instead I would try uninstalling the problem role, then apply SP2, then reinstall the role. If your problem role is Mailbox then I'm sorry, you are probaly screwed, like me.
Carol
http://www.wapshere.com/missmiis- Marked As Answer byCarolWMVPTuesday, November 03, 2009 8:30 PM
All Replies
- Some more info,
I tried to install sp1 ru9 on this server, after the failed installation of sp2. Of course it didn't work, I didn't really expected it to, but thought it worth a try. The error is:
"The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program."
I successfully installed sp2 on a sp1ru9 server earlier today, so the AD changes have already been made.
We are not going to do the full DRP tonight as the backup has not yet been configured on the second server. So the current state is:
- All mailboxes on server1 - aka screwed up server.
- Hub role seems to be working properly on server 1 (we can send/receive internal and external mail)
- Outlook clients are connecting to server1 CAS.
- ISA has been redirected to server2 CAS, where OWA and ActiveSync are working.
So we have a service, but server1 is in an unstable state where I can't uninstall or patch anything.
http://www.wapshere.com/missmiis - Do you have a valid System State backup that you can revert to ?
- Yes we do, but I'm trying to figure out what would be least disruptive/risky. I've never done a system state restore of an exchange server. Would it be better just to reinstall the server with the /recoverserver switch?
Also, another thought, the system state restore would return us to the point where we were getting the "BuildtoBuildUpgrade" error - and I couldn't find any official troubleshooting suggestions for that one.
http://www.wapshere.com/missmiis - Hi,
Let's clarify the issue first.
We cannot install SP2 on Exchange Server,is that ture?
Then I'd like to know if all the server roles install on the same computer. Which role has been installed on problematic computer?
Please ensure that all the server roles are on the same version, SP1 with rollup4.
Please verify if you have deleted the following register
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\ClientAccessRole
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\HubTransportRole
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\MailboxRole
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\UnifiedMessagingRole
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\ClusteredMailboxServer
Regards,
Xiu - Hi.
Yes the problme is with the installation of SP2 which failed half-way through and did not do any kind of roll-back (despite failing cleanly, not crashing) so has left the server in an unstable state where I can neither patch it nor uninstall any roles.
The server has the following roles: Mail box, Hub, CAS, Unified Messaging.
No-one could recall any problems from when ru4 was installed.
The only thing I deleted from any of those keys was "Watermark" and "Action" from under HubTransportRole.
Thanks, Carol
http://www.wapshere.com/missmiis - On the problematic server could you try below one and see of that helps you?
ServiceControl.ps1 -AfterPatch
Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3| - It doesn't seem to recognise that switch. I get a usage statement and then:
Write-Progress : Cannot bind argument to parameter 'Activity' because it is null.
At C:\Program Files\Microsoft\Exchange Server\bin\ServiceControl.ps1:1017 char:25
+ write-Progress -Activity <<<< $activity -Id 0 -Status 'Completed' -Completed
http://www.wapshere.com/missmiis - Things are continuing to go from bad to worse with this server.
I found this KB which fixed the problem with not being able to uninstall the roles: http://support.microsoft.com/kb/951183/en-us
I uninstalled Hub, CAS and UM.
I DID NOT uninstall the Mailbox role or the Admin tools.
I then found that if I ran setup /m:upgrade with the SP2 setup it updated the Admin tools. I was a little surprised that it did not update, or mention, the Mailbox role.
I noticed after this that ConfiguredVersion and UnpackedVersion now matched for the Admin tools in the registry. They were still different for the Mailbox role.
I re-ran the SP2 setup meaning to reinstall the missing roles. The Mailbox role was still selected as being installed. I attempted to install the Hub role and was told about a pending reboot.
I rebooted - and everything got even more royally screwed than I could have imagined. SOMETHING DELETED THE SERVER FROM AD! I did not do this. I did not uninstall the Mailbox role. All the services are still there on the server, though of course they can't start.
Now I'm having all sorts of fun and games with OAB and free+busy. I had already replicated all the public folders but the generation servers are wrong. Turns out you can't do a Move on the OAB if the original server is missing.
Thank goodness in this whole mess the one thing that has actually worked is SCR, so we have been able to retain all data and keep users working with minimum downtime - but I still have days of work ahead to get this orignial server rebuilt and sort out all this mess in AD.
Why the heck has this happened with an official SP?? I could understand if we'd had a power loss half-way through the installation - but it ended cleanly, albeit with errors. Why no rollback??? This is really very, very poor and the worst experince I have had with a Microsoft SP in many years.
http://www.wapshere.com/missmiis - I think I am probably beyond help on this issue now. So I am going to answer my own question with a warning to others: if you get the "You cannot resume setup by performing the action "BuildtoBuildUpgrade"" error DO NOT delete any Watermark or Action keys. Instead I would try uninstalling the problem role, then apply SP2, then reinstall the role. If your problem role is Mailbox then I'm sorry, you are probaly screwed, like me.
Carol
http://www.wapshere.com/missmiis- Marked As Answer byCarolWMVPTuesday, November 03, 2009 8:30 PM
This post is a bit unsettling: on my Exchange server, W2K8 SP2 shows up as update in Windows update (I have it configured to alert me but not install automatically) - so I hesitate to install it after reading the above.
Does anyone see why a simple (?) SP installation could cause such consequences?
Was the RU not recent enough perhaps:
Unfortunately by this point it had already disabled all the services and broken lots of things - and there wasn't any roll-back! I was trying to upgrade sp1 ru4 --> sp2.
Is there a pre-requisite for installing SP2 on an Exchange server?
And should Exchange SP2 be installed after or before W2K8 SP2?- After spending some time on the phone with a nice chap from Microsoft this week - we don't as yet have any clear idea as to why this happened. The MS guy confirmed that my workaround to get the SP2 install running (deleting Action and Watermark) was in fact what they would have suggested themselves - even though he stressed it is not an "official recommendation".
I installed Windows SP2 on both exchange servers before installing Exchange SP2. On one of them (exchange sp1ru9) the sp2 installation went fine. Of course that was the DRP server - and it was the prod server that got destroyed.
They have no idea why the server object disappeared from AD, and I had lots of fun and games chasing down the public folder problems that caused. I checked for AD replication problems and found none.
What I did find though was thousands of errors on the DCs like this:
Event Type: Error
Event Source: NTDS General
Event Category: DS Schema
Event ID: 1136
Date: 06.11.2009
Time: 08:48:10
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: HERCULES
Description:
Active Directory failed to create an index for the following attribute.
Attribute identifier:
526354801
Attribute name:
msExchObjectID
A schema cache update will occur 5 minutes after the logging of this event and will attempt to create an index for the attribute.
Additional Data
Error value:
-1403 JET_errIndexDuplicate, Index is already defined
There were a number all relating to msExch atributes and they only started after SP2 was installed on the first server.
It appears there is some kind of problem if the language settings on your DCs are different to the language of the SP2 binaries. Though honestly - why anyone should assume that just because you install English Exchange, your DCs are also installed in english, I don't know!
The way to stop the error messages was as follows:
Please register the Schema Tool
1. Click Start , and then click Run .
2. Type regsvr32 schmmgmt.dll , and then click OK . A message should be displayed
stating that the registration was successful.
Change the settings
1. Click Start , click run , type mmc , and then click OK .
2. On the Console , menu click Add/Remove Snap-in .
3. Click Add .
4. Click Active Directory Schema .
5. Click Add .
6. Click Close to close the Add Standalone Snap-in dialog box.
7. Click OK to add the snap-in to the console.
8. expand the active directory Schema to where you see classes and attributes.
9. select attributes.
10. on the right side select the following attribute. msExchScopeFlags (do the same to the other related attributes) and select properties.
11. I would uncheck the box "index this attribute for containerized searches in the active directory"
12. After that hit apply then ok.
13. select the top of the snapin where it says active directory schema
14. right mouse click and select " Reload the schema"
15. then you can exit the schema snapin.
All I can recommend after the nightmare of this week is: hope for the best but prepare for the worst! We were lucky that we already had the DRP server set up and SCR working. While the users had two days of disruptions and niggles like free-busy not working, we had NO DATA LOSS!
Carol
http://www.wapshere.com/missmiis- Proposed As Answer byphineousphreak Wednesday, November 11, 2009 2:49 AM
- I was having the same issue.Here is what I did to get passed it.In the regsitry of the exchange server there are regsitry keys for the roles...for whatever reason during the installation process, the key for ConfiguredVersion does not get created.You need to go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\MailboxRole and add a key for ConfiguredVersion. Set it to the value in the UnpackedVersion.Restart the install and you should go straight to the roles configuration portion where setup failed the last time.It will move beyond this error and you should be good to go.Regards,PP
- Proposed As Answer byphineousphreak Wednesday, November 11, 2009 3:00 AM
