Remove 1st exchange 2k server - unable to restart services on it to move system folders
Posted on 2004-09-23
We have what I think could me a major problem with our exchange set-up here, we currently have 2 fully working E2K servers in 2 sites (1 in each), we also have a 3rd E2K server based at the main site which was the 1st E2K server in the site/domain.
I had been told by the previous sys admin that problems occurred with the 1st E2K server which resulted in a 2nd E2k being installed and used, the sys admin then went through some processes (which I don't have details of) to remove it from AD. However the 1st server is still running, but with all the exchange services stopped. The previous sys admin informed me that when he tried to switch off the 1st server completely that users reported errors, so he switched it back on and left it with the e2k services all stopped.
I have been tasked with re-installing the 1st server, so I found the article Q307917 from MS site, and the first step for removing E2K is to right hand click on a top-level public folder from within ESM, when I do this a system error appears after about 1 min, then I notice that ESM has a description bar which clearly says: Public Folders (Connected to NameOf1stServer) .
So from this it's clear that the system/public folders have not been correctly moved to the 2nd server, one of the reasons of course that I get the system error is because the E2k services are no longer running on the 1st E2k server - if i try and start the System Attendant service the service cannot be started with "The service did not report an error".
In event viewer I see the following errors logged: event 7001 (relates to System Attendant not starting with %%0), event also logged - 2102(all domain controllers in use are not responding), 1002 (metabase agent failed to start 80040a01), 1005(id 80040a01) , 9004 (metabase update failed 80040a01)
I think that about covers it, any info / help you can give is much appreciated, please let me know if you require more info.