Link to home
Start Free TrialLog in
Avatar of DaveQuance
DaveQuanceFlag for United States of America

asked on

Exchange 2007 SP2 Single Node Cluster (SP3 upgrade failed)

When trying to upgrade a single node Exchange 2007 cluster, I'm erroring out at 63% of configuring the Mailbox Server role with this error:

An error occurred. The error code was 3221684294. The message was The remote server has been paused or is in the process of being started.

I performed the stop-clusteredmailboxserver, took the "cluster group" offline, then ran setup.com /mode:upgrade

I'm not finding much info on how to resolve it but the mailbox databases are down right now. I'm still looking but am in the middle of a downtime window, so if anyone can point me in the right direction quickly, that would be of great help.

OS: Windows 2008 SP2 (on VMware, not sure which version)

Edit: Cleared the excerpt and attached it as a file
ExchangeSetupLog-Excerpt.txt
Avatar of DaveQuance
DaveQuance
Flag of United States of America image

ASKER

I'm wondering if it might be AD related, the only other error I'm finding is (the firewall is disabled on this server as well):

MSExchange ADAccess 2152
Process ExSetup.exe (PID=2524). An remote procedure call (RPC) request to the Microsoft Exchange Active Directory Topology service failed with error 1753 (Error 6d9 from HrGetServersForRole). Make sure that the Remote Procedure Call (RPC) service is running. In addition, make sure that the network ports that are used by RPC are not blocked by a firewall.
SOLUTION
Avatar of Mahesh
Mahesh
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I'd been looking at the registry related items in posts mentioned in your link and will probably try those soon. I've been apprehensive to reboot the server. I did some DNS checking and restarting of DNS client/server and now when I try the setup, it fails to even get information. Due to my waning window I opened a Microsoft case (figuring it'll take them 2 hours to call me back anyway, so if I haven't figured it out by then I'll welcome the call).

setup.com /mode:upgrade

Welcome to Microsoft Exchange Server 2007 Unattended Setup

Preparing Exchange Setup


 An error occurred when setup was getting the configuration information of the current server. Setup can not continue. Please restart Exchange Server 2007 Setup to retry.


Setup log shows:
[11/16/2013 4:07:20 AM] [0] This machine is part of a Windows failover cluster.
[11/16/2013 4:07:20 AM] [0] The Windows Cluster service encountered an error during function OpenCluster:.
[11/16/2013 4:07:20 AM] [0] There are no more endpoints available from the endpoint mapper
[11/16/2013 4:07:20 AM] [0] An error occurred when setup was getting the configuration information of the current server. Setup can not continue. Please restart Exchange Server 2007 Setup to retry.
[11/16/2013 4:07:20 AM] [0] End of Setup
Chimney offloading was already disabled on global (I disabled it on the main interface, but  not the iSCSI one). I also disabled RSS. NetDMA is a registry change though, so I'm holding off on it for now since I think it will require a reboot.

At this point though, I need to get through the new error before I can find out if these changes help.
The errors in those last two links seem to point to a different issue. My current one seems to be cluster related (and the setup being unable to pull configuration information from it).
A reboot got passed the new error but the old is still there (NetDMA is disabled now too). The MS person is on the line now and recommending we do the /UpgradeCMS first. The cluster is being forced to start but it's taking an abnormally long time to start.

I'll update if there is more progress.
When all is done I'll give a every step I performed. Right now I've gotten the mailbox server upgraded but the setup.com /UpgradeCMS is failing (any thoughts?):

[11/16/2013 7:02:43 AM] [2] Unexpected Error
[11/16/2013 7:02:43 AM] [2] Error of unknown type occurred while performing exsetdata operation; the original error code was 0xc1037b45.
[11/16/2013 7:02:43 AM] [2] Ending processing.
[11/16/2013 7:02:43 AM] [1] The following 1 error(s) occurred during task execution:
[11/16/2013 7:02:43 AM] [1] 0.  ErrorRecord: Error of unknown type occurred while performing exsetdata operation; the original error code was 0xc1037b45.
[11/16/2013 7:02:43 AM] [1] 0.  ErrorRecord: Microsoft.Exchange.Management.Tasks.ExsetdataUnknownException: Error of unknown type occurred while performing exsetdata operation; the original error code was 0xc1037b45.
[11/16/2013 7:02:43 AM] [1] Error of unknown type occurred while performing exsetdata operation; the original error code was 0xc1037b45.
[11/16/2013 7:02:43 AM] [1] Setup is halting task execution because of one or more errors in a critical task.
[11/16/2013 7:02:43 AM] [1] Finished executing component tasks.
[11/16/2013 7:02:43 AM] [1] Ending processing.
[11/16/2013 7:02:43 AM] [0] The Exchange Server Setup operation did not complete. For more information, visit http://support.microsoft.com and enter the Error ID.
Sorry friend,
Unable to found solution
please find similar, post resolved by MicroSoft
https://www.experts-exchange.com/questions/27548078/Exchange-2007-SP3-install-failing-on-an-active-passive-cluster.html
Microsoft has been quiet for a long while... not feeling a great deal of confidence.  My searches are only bringing up references to *creating* clusters, or adding nodes. I haven't found any where the issue occurred during an /upgradeCMS. I might be asking for an escalation soon.

Thank you for your efforts though. Maybe MS will come up with something soon.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Result ended up being a lost cause where a more extreme method was used to accomplish the end goal, so it wasn't *solved* per se. The only progress that did come through, the exact reason it went through is unclear (likely the cluster group remaining online).

I appreciate MaheshPM's efforts. The post I marked, that leads to the Chimney, RSS, etc. references, likely contributed positively to the progress I did make before giving up.