Hi, Please try to run ExBPA to have a health check of your Exchange organization. We may have to use ADSIedit.msc to remove the old server. Note: Please make backup first when you make any modification via ADSIedit.msc If it is the first Exchange server, then please ensure that you have moved public folder and set the default public folder on the new exchange. Please ensure that you have change the OAB generation server to the new Exchange Server. Xiu Zhang TechNet Community Support

Hello, Recently we have been having some major problems with an Exchange 2007 SP3 Setup running on Microsoft Windows Server 2008 SP2. So, long story short, we built a new system running Windows Server 2008 R2 SP1 with all the updates, installed Exchange Server 2007 SP3 on THAT system, transfered the mailboxs, and changed the settings so that all mail plus connections go to that box. So, no problems with access. Now we would like to remove the old box. So I am trying to run the Exchange 2007 uninstall wizard, either from the Add/Remove programs or from the command line. If I try from the Add/Remove programs, I get the pop-up of "ExSetupUI.exe has stopped working". If I try from the commandline using the command "Setup.com /mode:uninstall" is get the following bacl from the commandline: Exchange Server setup encountered an error. The logfile in the "ExchangeSetupLogs" directory shows this: [2/19/2012 3:59:48 PM] [0] ********************************************** [2/19/2012 3:59:48 PM] [0] Starting Microsoft Exchange 2007 Setup [2/19/2012 3:59:48 PM] [0] ********************************************** [2/19/2012 3:59:48 PM] [0] Operating System version: Microsoft Windows NT 6.0.6002 Service Pack 2. [2/19/2012 3:59:48 PM] [0] Setup version: 8.3.213.1. [2/19/2012 3:59:48 PM] [0] Logged on user: WESLEYSEM\administrator. [2/19/2012 3:59:48 PM] [0] Command Line Parameter Name='nologo', Value=''. [2/19/2012 3:59:48 PM] [0] Command Line Parameter Name='mode', Value='Uninstall'. [2/19/2012 3:59:48 PM] [0] Command Line Parameter Name='fromsetup', Value=''. [2/19/2012 3:59:48 PM] [0] ExSetup was started with the following command: '/NoLogo /mode:uninstall /FromSetup'. And the event viewer shows this entry: Faulting application exsetupui.exe, version 8.3.213.0, time stamp 0x4e4e1323, faulting module KERNEL32.dll, version 6.0.6002.18449, time stamp 0x4da47b2f, exception code 0xe0434f4d, fault offset 0x00000000000170cd, process id 0x%9, application start time 0x%10. What can I do to remove the old Exchange box? Thanks.Regards, Christopher K.

Did this (problem) server hold all the roles: CA, MB, HT (UM?) ? If so, you might attempt to remove one role at a time. That way, you could see if the problem has to do with a particular role. Short of resolving the problem, that will narrow things down. --- In a word or two, could you explain what the major problems were with the server you want to remove? That might provide a useful hint. --- Nothing else in the install (uninstall) log? Hopefully from MS (or from anywhere) will be able to interpret that cryptic error messagee.

Did this (problem) server hold all the roles: CA, MB, HT (UM?) ? Yes, no Unified Messaging. If so, you might attempt to remove one role at a time. That way, you could see if the problem has to do with a particular role. Short of resolving the problem, that will narrow things down. The thing is I can't even get that far. As soon as I try to run the program I get hit with the error so I can't even select a role to remove. In a word or two, could you explain what the major problems were with the server you want to remove? That might provide a useful hint. See here. Nothing else in the install (uninstall) log? Hopefully from MS (or from anywhere) will be able to interpret that cryptic error messagee. Unfortunately, no.Regards, Christopher K.

Hi, Please try to run ExBPA to have a health check of your Exchange organization. We may have to use ADSIedit.msc to remove the old server. Note: Please make backup first when you make any modification via ADSIedit.msc If it is the first Exchange server, then please ensure that you have moved public folder and set the default public folder on the new exchange. Please ensure that you have change the OAB generation server to the new Exchange Server. Xiu Zhang TechNet Community Support