Hi,
I encountered a problem while instaling an Exchange 2007 CAS/HUB server within a Windows 2000/Exchange 2000 scenario. I have already upgraded the Windows to 2003 and have also done the pre-requisites for Exchange 2007. However when I was installing the CAS/HUB server, because I was performing this on a blade server and using the DVD-ROM on the RDP Server, the connection was quite slow which resulted in a failure to complete the installation.
It generated an error "An unexpected error has occured and a Watson dump is being generated. Access to the path 'Z:\Setup\ServerRoles\Common\64' is denied." Upon checking on this error, I found that is was a low bandwidth issue which could be resolved simply by copying the setup files to the hard disk itself.
However, since it was an unsuccessful installation, I then proceeded to remove the Exchange 2007 and planned to redo this again by using the setup.com /m:uninstall option. However, it threw back this error: "An unexpected error has occurred and a Watson dump is being generated: Unexpected error [0x16C9C811\ while executing command '$error.Clear(); uninstall-ExsetdataAtom -AtomName SMTP -DomainController $RoleDomainController'."
Searching for any articles to manually Remove Exchange 2007 have resulted in telling me to perform the uninstallation as per above which didn't work for me.
Has anyone ever encountered this problem? And how do I go about cleaning the Active Directory of records of this server so that I can re-install this server completely and proceed to install a new CAS/HUB server? Any input will be much appreciated.
Thank you.
regards
Ricky Chong
What happens when you try a reinstall and specify the local source data?
- Joel
Yeah. I was able to successfully uninstall it and installing it was ok. But sigh... installing the Transport role into the server, the Transport service fails to start and kicks up an Event ID:2114 error:0x80040a02. Which checking from the Microsoft TechNet Forum is from not having the SACL configured properly when I was preparing the Forest and Domain for Exchange. But I could've sworn that I have already done all those steps and now I have to uninstall the CAS/HUB (technically only a HUB server as it never installed the CAS portion into the server) and redo the /preparealldomains
Well.. patience is a virtue.. :)
You can run /preparedomain or /preparealldomains or any of the other switches without uninstalling the roles. Try just running it first and see if it helps.
Actually, I tried running /preparedomain or /preparealldomains from the CAS/HUB server but it wouldn't let me. It stated that the installation for the CAS/HUB failed while installing and would not continue. I did manage to get the CAS/HUB uninstalled and re-preped my AD for Exchange 2007 by doing all the steps. After that, I installed each role individually starting with the CAS then the HUB and it went in fine.
When I created the Routing Group Connectors to connect to the Exchange 2000 Server which is in the same Exchange Org, mail-flow was running fine from E2k -> E2k7, E2k7 -> E2K, External -> E2k7, E2k7 -> External (my IMC is on the Exchange 2000 Server). Alas, by luck ran short about then and when I came back the next day, I could send emails from E2K7 -> E2K, E2k7 -> External but not E2K -> E2K7 and External -> E2K7. The funniest thing which I saw was; Our recipient policy had 3 domains specified, xxx.gov.my, xxx.com.my and xxx.local.
When I tracked any emails sent from E2K to E2K7, all emais that was suppose to go to E2K7 went out the IMC. Considering that the receipient policy should dictate that it is a local domain and shouldn't be routing it externally and als considering the user was in Active Directory as well as the Global Address List, I didn't think this was possible. However, it did happen to which now I am totally stumped.
Any ideas or anyone had this experience before?
If you run winroute from the Exchange 2000 Server computer do you see any problems with the connection between the 2000 and 2007 servers?