BGilhooley
asked on
Exchange 2003 uninstall "hanging"
Hi there. Doing an exchange migration last few weeks and its all gone well thus far. Im at the stage of uninstalling the old exchange as everythings moved to the new one, mailboxes, public folders, services etc. All working fine on the new box (its 2003 exchange). The problem I'm having is when I go into Add/Remove programs, run the uninstall, it gets as far as Microsoft Exchange in the preinstallation process and then just does nothing. Its been sitting there for over an hour now and aint progressing. Screenshot attached.
Notice also that I have a red x next to the messaging and collaboration services, guessing thats a hidden mailvbox which I would clean up if the uninstall would allow me. If I try and cancel the uninstall I get the mesage: 'setup cannot be cancelled during installation of this component' so I'm kinda in limbo with it. Reluctent to kill the process in case it causes an issue. Anyone seen this happen before?
Have googled and it doesnt seem a common issue anyway. Thanks in advance folks...
stuck.jpg
Notice also that I have a red x next to the messaging and collaboration services, guessing thats a hidden mailvbox which I would clean up if the uninstall would allow me. If I try and cancel the uninstall I get the mesage: 'setup cannot be cancelled during installation of this component' so I'm kinda in limbo with it. Reluctent to kill the process in case it causes an issue. Anyone seen this happen before?
Have googled and it doesnt seem a common issue anyway. Thanks in advance folks...
stuck.jpg
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Razi_Ahmed
also do you see event 1002 in event log ?
Look in the ExchangeSetupProgress.log which should be in the root of the C: drive it should shed some light on why E2k3 is not uninstalling.
ASKER
This is the last line in the setupprogress.log file:
[17:35:55] Calling Dr. Watson 2.0 installer with command line: "msiexec /i dw20.msi /q reinstallmode=vomus reinstall=all reboot="ReallySuppress""
[17:35:55] Process created ... waiting (-1)
Could it be Dr Watson holding it up?
Negative on the event 1002 Razi.
theres Symantec MSME and SAV AV on there. Trying to stop the services but they are refusing to stop for me thus far.
[17:35:55] Calling Dr. Watson 2.0 installer with command line: "msiexec /i dw20.msi /q reinstallmode=vomus reinstall=all reboot="ReallySuppress""
[17:35:55] Process created ... waiting (-1)
Could it be Dr Watson holding it up?
Negative on the event 1002 Razi.
theres Symantec MSME and SAV AV on there. Trying to stop the services but they are refusing to stop for me thus far.
ASKER
cant force the symantec services to stop, via services or via taskmgr.
ASKER
dont see how I can get around this without forcing a reboot but how will that affect my uninstall and indeed exchange and AD environment?
ASKER
killed one of the Symantec process using pskill but that spiked CPU to 100% constant so that might not be the way to go.
If I force the uninstall to cancel at the stage its at and reboot am i going to break things?
If I force the uninstall to cancel at the stage its at and reboot am i going to break things?
Uninstall the AV software then try uninstall Exchange
ASKER
i understand I need to uninstall the AV, however at present i cant until I reboot. My query now bsically is it is safe to kill the uninstall process where it is? Its telling me I cant cancel it when I try to..
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Have gotten the AV etc removed and have tried the uninstall again, however its failing with the following error:
An unexpected error occured.
ID no. 8000ffff
Microsoft Exchange Setup
Have checked this out and running the uninstall from the cd seems to be the accepted wisdom however the client cant find the exchange 2003 enterprise CD, nothing is ever straight forward. Have to try and find one somewhere
An unexpected error occured.
ID no. 8000ffff
Microsoft Exchange Setup
Have checked this out and running the uninstall from the cd seems to be the accepted wisdom however the client cant find the exchange 2003 enterprise CD, nothing is ever straight forward. Have to try and find one somewhere
ASKER
Got a CD and got uninstall to run properly. Just one more query, when I check in system manaager the old now uninstalled server still shows up in the server list/routing groups. Can i just delete from here?
If Exchange is removed from the servers sucessfully and server is still showing up in ESM then go ahead and remove it from ESM, it should e a stub object. (Delete the server from ESM)
ASKER
Need clarification on this, its been offline a few days now, everythigns working fine. However in ESM on the new server when I try and delete the server it just hangs the ESM. (Right click on old servr- egg timer).
Looking with adsiedit I still see references to the old server. I would have thought that seeing as the uninstall went without any errors (once the symantec had been taken care of) that all references would have been removed from AD and it would no longer be in ESM?
Looking with adsiedit I still see references to the old server. I would have thought that seeing as the uninstall went without any errors (once the symantec had been taken care of) that all references would have been removed from AD and it would no longer be in ESM?
How long did you leave it ESM for? Might be worth leaving for an hour after pressing delete on the server.
Otherwise delete it with ADSIEdit as per this article http://support.microsoft.com/kb/833396
Otherwise delete it with ADSIEdit as per this article http://support.microsoft.com/kb/833396
ASKER
what I had to do was bring back online the old server, then delete it via ESM. Gave me an error initially but still allowed me delete it. Its now gone fully from ESM and no ref in ADSIedit. Looking good.
sounds good.
yes, you will probably find ESM was hanging because it was trying to contact the old server. It should of eventually come back and said the old server was unavailable and then allowed you to delete it.
yes, you will probably find ESM was hanging because it was trying to contact the old server. It should of eventually come back and said the old server was unavailable and then allowed you to delete it.