I am currectly installing Ex 2010 in a domain with ex 2003. The goal is to replace the 2003 server. The first attempt to install ex2010 was successfull but the crashed and could not be recovered. The entire w2008r2 server was redone from scratch. Had problems with each role install but through knowledge bases was able to get Hub and Client roles installed. Mailbox role will not install. after a server reboot, setup fails after selecting install exchange. It never gets to the role selection screen. I get the following from event viewer and then after that is the exchange setup log for the setup attempt. Fault bucket 1351643556, type 5 Event Name: E12 Response: None Cab Id: 0 Problem signature: P1: c-RTL-AMD64 P2: 14.00.0639.021 P3: ExSetupUI P4: M.Exchange.Management P5: M.E.M.D.RolesUtility.GetConfiguringStatus P6: System.InvalidCastException P7: 6489 P8: 14.00.0639.021 P9: P10: Attached files: C:\ExchangeSetupLogs\ExchangeSetupWatson.log C:\ExchangeSetupLogs\ExchangeSetup.msilog C:\Users\administrator.JDSTEELCO\AppData\Local\Temp\2\f2b06987-1039-47aa-9cca-324a4efcfd26\report.txt C:\Users\administrator.JDSTEELCO\AppData\Local\Temp\2\f2b06987-1039-47aa-9cca-324a4efcfd26\report.xml These files may be available here: C:\Users\administrator.JDSTEELCO\AppData\Local\Microsoft\Windows\WER\ReportArchive\Report21827501 ____________________________________________ 10/03/2011 19:29:55.0149] [0] ********************************************** [10/03/2011 19:29:55.0180] [0] Starting Microsoft Exchange Server 2010 Setup [10/03/2011 19:29:55.0180] [0] ********************************************** [10/03/2011 19:29:55.0180] [0] Local Time Zone: (GMT-07:00) Arizona. [10/03/2011 19:29:55.0180] [0] Operating System version: Microsoft Windows NT 6.0.6002 Service Pack 2. [10/03/2011 19:29:55.0180] [0] Setup version: 14.0.639.21. [10/03/2011 19:29:55.0180] [0] Logged on user: JDSTEELCO\administrator. [10/03/2011 19:29:55.0462] [0] Command Line Parameter Name='mode', Value='Install'. [10/03/2011 19:29:55.0462] [0] Command Line Parameter Name='sourcedir', Value='D:\'. [10/03/2011 19:29:55.0462] [0] Command Line Parameter Name='fromsetup', Value=''. [10/03/2011 19:29:55.0462] [0] ExSetupUI was started with the following command: '-mode:install -sourcedir:D:" /FromSetup'. [10/03/2011 19:29:55.0727] [0] Setup is choosing the domain controller to use [10/03/2011 19:29:55.0852] [0] The MSExchangeADTopology has a persisted domain controller: JDSTEEL-TMBR.jdsteelco.local [10/03/2011 19:29:56.0555] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use JDSTEEL-TMBR.jdsteelco.local [10/03/2011 19:29:56.0555] [0] Setup is choosing a global catalog... [10/03/2011 19:29:56.0555] [0] Setup has chosen the global catalog server JDSTEEL-TMBR.jdsteelco.local. [10/03/2011 19:29:56.0571] [0] Setup will use the domain controller 'JDSTEEL-TMBR.jdsteelco.local'. [10/03/2011 19:29:56.0571] [0] Setup will use the global catalog 'JDSTEEL-TMBR.jdsteelco.local'. [10/03/2011 19:29:56.0571] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=jdsteelco,DC=local'. [10/03/2011 19:29:56.0587] [0] Exchange organization container for the organization is 'CN=First Organization JDSteel,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=jdsteelco,DC=local'. [10/03/2011 19:29:56.0618] [0] Setup will search for an Exchange Server object for the local machine with name 'JDSTEEL-EX2010'. [10/03/2011 19:29:56.0633] [0] Exchange Server object found : 'CN=JDSTEEL-EX2010,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization JDSteel,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=jdsteelco,DC=local'. [10/03/2011 19:29:56.0680] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole AdminToolsRole [10/03/2011 19:29:56.0680] [0] The following datacenter roles are unpacked: [10/03/2011 19:29:56.0680] [0] The following roles are installed: BridgeheadRole ClientAccessRole AdminToolsRole This is all of the log entry. It just stops. Please help.

Is this a new server with the same name as the one that failed or a partially installed server or something else?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Is this a new server with the same name as the one that failed or a partially installed server or something else?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi According to your log, exchange server object already exists on your server. please remove all exchane role on server and ADSI. Then you can install fresh exchange system.

There is an Exchange 2003 server that is working just fine. The exchange 2010 server will replace the 2003 server. The 2003 server is on a computer named jdmain. The 2010 is on a new virtual 2008 R2 server named jdsteel-ex2010. The 2003 server is not virtual. My big worry is not crashing the 2003 server with wrong active directory edits. CoryCory Larsen

I'm still not sure of your question. If you're trying to do an in-place upgrade of Exchange 2003 to Exchange 2010 on the same server, that's not supported and won't work. If you're building a new Exchange 2010 server in the same organization, that shouldn't affect your Exchange 2003 server.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

I tried to run uninstall through programs and features and with setup uninstall command. Neither works. I just get a setup error. My big worry is not crashing the 2003 server with wrong active directory edits. I would also appreciate better instructions than just "remove all exchange role on server and ADSI." Since setup won't uninstall, the question is HOW with the detailed steps that will remove the items exchange 2010 setup and not distroy the running exchange 2003 server. Note: There is an Exchange 2003 server that is working just fine. The exchange 2010 server will replace the 2003 server. The 2003 server is on a computer named jdmain. The 2010 is on a new virtual 2008 R2 server named jdsteel-ex2010. The 2003 server is not virtual.Cory Larsen

You don't need to replace the old server per se. Bring the new server up with a different name so you can move the mailboxes, public folders and connectors to it and then retire the old server. If you insist on trying to bring up a new server with the same name as the old one you're going to make things very difficult for yourself and your users. You might consider buying a book by Tony Redmond, Jim McBee or Rand Morimoto and reading through it for a lot more information about this process, or read the documentation on TechNet, or hire a consultant.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

You don't need to replace the old server per se. Bring the new server up with a different name so you can move the mailboxes, public folders and connectors to it and then retire the old server. If you insist on trying to bring up a new server with the same name as the old one you're going to make things very difficult for yourself and your users. You might consider buying a book by Tony Redmond, Jim McBee or Rand Morimoto and reading through it for a lot more information about this process, or read the documentation on TechNet, or hire a consultant.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."