Exchange 2003 Reinstallation

Hello there,

I'm new to this website and turning to you guys as a last resort so I would be eternally grateful to anyone who knows a solution to this problem. I will be concise in my explanation and will briefly point out what has happened from start to finish. The current issue is that I am unable to reinstall Exchange 2003 on a DC running Windows Server 2003 Standard. The following Error is returned when installing the Exchange Collaboration and Messaging Services.

"Setup failed while installing sub-component System Attendant service with the error code 0xC00703E5 (Please consult the installation logs for a detailed description). You may cancel the installation or try the failed step again."

I used the following KB article during the Reinstallation of Exchange. http://support.microsoft.com/kb/320202

From the beginning:

1.      Exchange server is in working order and user asks for POP3 service to be enabled on the server for remote users.
2.      New server role added "Mail Server" which installed POP3 and SMTP service. (Stupid I know)
3.      Exchange mail flow stops working and IIS now has an SMTP Virtual Server with the drop down menu. (as if IIS has now taken control of SMTP Virtual Server)
4.      Realized the problem and removed the "Mail Server" role. SMTP and POP3 service now missing. SMTP Virtual Server not running in Exchange System Manager.
5.      Reinstalled SMTP service but still no joy. SMTP Virtual Server still showing within IIS!
6.      Looked into the issue and decided to back up Information Store using NTBackup and also took a copy of MDBDATA after un-mounting the Information Store and stopping all Exchange services.
7.      Uninstalled IIS and reinstalled successfully.
8.      Reinstalled Exchange unsuccessfully with error: "Setup failed while installing sub-component System Attendant service with the error code 0xC00703E5&&."
9.      Skipped error to continue and receive error at the end of the setup wizard "Overlapped I/O operation is in progress, ID no: c00703e5, Microsoft Exchange Setup"
10.      Applied Service Pack 2 for Exchange  Successful
11.      Replaced MDBDATA with backup and started Services. All but "Exchange Routing Engine" started. "Error 1083: The executable program that this service is configured to run in does not implement this service"
12.      After advice from various sources on the web I tried the Re-installation using the /disaster recovery switch. Again the same problem occurs.

I have not yet applied service pack 2 as I am sure I will received the same error with the Exchange Routing Engine. I am sure the problem now resides with the initial re-installation error received. How can this error be prevented? I can find little on this problem and most solutions point towards a permissions issue which I have tried to implement. One of the solutions involves making the Domain Admin the Local Admin of the server, however the Server is a DC so this is not possible. Please help if you are an Exchange Guru! I am desperate for your input on this problem.

Thank you
Potato-JoeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SaakarCommented:
Hummm... you seems to be in a bad shape.

I recommend removing exchange 2003 manually from the computer following
http://support.microsoft.com/kb/833396
and then
How to Reinstall Exchange 2003 over a Damaged Installation
http://technet.microsoft.com/en-us/library/aa997239(EXCHG.65).aspx

- Saakar
0
Potato-JoeAuthor Commented:
Why would you not suggest uninstalling normally and then reinstalling? Is it to avoid harming Active Directory?

Cheers
0
SaakarCommented:
Removing Exchange manually from the server would not harm AD structure.
If you are worried and want to play safe take a system state back up and then perform the steps for manual removal.

Best Luck

- Saakar


0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Potato-JoeAuthor Commented:
So let me get this right.

1. Perform System State Backup
2. Disconnect mailboxes
3. Manually uninstall exchange
4. Reinstall Exchange over damaged installation (I have previously followed this article)
5. Re-mount Information store and re-connect mailboxes.

Is this something you have done before and how certain are you that the same error will not occur during installation?

Thanks!
0
SaakarCommented:
Yes, you are right on spot. I have done it a couple of times, so don't worry everything should go smooth.

All the Best with you reinstall

- Saakar
0
Potato-JoeAuthor Commented:
Will reconnecting the mailboxes give the users access as before? I'm also really worried that this error will just occur again and I'll be left in a worse state?

I really appreciate your help but I wouldn't mind waiting for a second opinion on your solution.

Cheers
0
Potato-JoeAuthor Commented:
I feel as though the manual uninstall will not stop the installation error from occuring. Why should it change?
0
Potato-JoeAuthor Commented:
I found this article which appears to offer a good solutions having understood that there is a permissions issue here. My server is also from an older domain which indicates a possible fix. I am not techinical enough to understand the end of the thread. Please read:

http://forums.msexchange.org/m_40137500/tm.htm

Thanks!
0
SaakarCommented:
I doubt that the the error would appear again while reinstall.
0
Potato-JoeAuthor Commented:
Did you get a chance to look at the link about permissiosn on the AD attributes? What do you think?

Thanks!
0
Potato-JoeAuthor Commented:
One more question. Before I begin the manual removal, would you suggest installed Exchange SP2 with the /distaster recovery switch for completeness?

Cheers
0
Potato-JoeAuthor Commented:
Going back to what you said about not effecting active directory it seems as though the manual uninstall will remove all exchange attributes anyway...

Remove the Exchange 2003 server from Active Directory
To remove the Exchange 2003 server from Active Directory, follow these steps:
Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
Expand Administrative Groups/Your_Administrative _Group_Name/Servers.

Note In this step, Your_Administrative _Group_Name is a placeholder for the name of your administrative group.
Right-click the name of the Exchange 2003 server that you want to remove, click All Tasks, and then click Remove Server.
This procedure will remove all references to the server in Active Directory and remove the mailbox-enabling attributes from all Active Directory users who have mailboxes on the server that you removed.
0
Potato-JoeAuthor Commented:
Is there nobody else with ideas on this issue?
0
Potato-JoeAuthor Commented:
This problem has been resolved. Since I hadn't had any issues uninstalling Exchange 2003 I went ahead the traditional way as opposed to saakar rao's manual recommendation.

Steps:
1. Made a backup of the Exchange.
2. Disconnected all the mailboxes.
3. Unmounted the store.
4. Uninstalled Exchange 2003. (You also need to complete the last step in the Manual Uninstallation method presented by saakar rao - amending attributes using the ADSI Editor).
5. Removed any remaining Exchange Attributes via active directory ->Tasks
6. Reinstalled Exchange 2003.
7. Restored Mailstore using NTBackup.
8. Mounted the store.
9. Reconnected the mailboxes using the mailbox recovery center.
10. Some mailboxes had trouble connecting saying that they were already being used by another user. To resolve this I simply removed the Exchange attributes from the user in question (for a second time) and then reconnect.

All is now working well. I hope others can use this thred to sort their problem in the future since this error is only documented in one other place and it was never resolved.

Thank you saakar rao for your input on this one. Although I did it differently to your recommendation it was you that brought some light to the situation which in turn lead me to go down this route.

Cheers


0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
SaakarCommented:
Potato-Joe,

Don't you think that I deserve some point for this??
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Protocols

From novice to tech pro — start learning today.