Cannot remove server in System manager after manual uninstall

I have an old exchange server that is still showing up in the system manager that I recently brought back online to remove. I tried to remove it using Add/Remove programs, but I kept getting an error that I could not remove it because there were still mailboxes in the store. When I would go to see if this was true in the system manager, I would get an error that the mailbox store could not be reached. I made sure IIS was running, but still I couldn't get into the store. Since it didn't matter what mailboxes might have been on that server because it hadn't been online in at least a year or so, i decided just to remove Exchange manually. I followed the instructions on the Microsoft KB, which I had done successfully in the past, but the server is still showing up in the system manager on the new server. When I try to remove it there using the remove server option, I get the error that there are still mailboxes on the server, even though Exchange has been removed from the server. Is there another place I need to go to remove this info?
numb3rs1xAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
sk_raja_rajaConnect With a Mentor Commented:
install the support tools on your 2003 domain controller - either from the Server CD or my website http://www.petenetlive.com/Downloads/software/TOOLS.zip

then Start Run adsiedit.msc {enter}
expand the following

configuration > cn=config.... > cn=servces > cn=microsoft exchange > cn=firsr org > cn=administrative groups > cn= first administrative group > cn=servers
Locate the dead server > right click and delete

Restart the server (or restart the exchange services)
0
 
jacodaletCommented:
what version of exhange are you running now! and was that other server a DC aswell
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
numb3rs1xAuthor Commented:
sk_raja_raja: After I made that change, the exchange IS service would not come back up. I had to scramble using the event manager and google to discover there was some kind of routing master role that was still assigned to that old server. I used the system manager to set the role to the current server and it came back, but that was close. everything seems to be functional now and I'm looking over the event manager. Is there anything else I should look our for?
0
 
numb3rs1xAuthor Commented:
I am getting the event 112 from EXOLEDB, which, since it seems to have only logged itself once, might be nothing, but I was looking it up and there was mention of having more than one schemaroot attributes under the public folders section in the system manager. I looked this up under my system manager and I noticed that I might have 2 of those. One at schema-root\default and one at schema-root\microsoft\exchangeV1. Is this what is meant by having two or are these both supposed to be there?
0
 
sk_raja_rajaCommented:
This error can get logged when the exoledb interface tries to make a call to the store but the databases are dismounted (as will usually happen at startup). You should then see informational events for your stores mounting and no more of the 112s. If this is what you are seeing you can ignore the errors. If you, however, continue to see the events while the dbs are mounted then you have a problem that will require further investigation.

If you continue to see these events while the DBs are mounted then try the following steps:

In ESM, check to see if you see two "schemaroot" system folders.
To check this, right click "Public Folders" and click "View System Folders".
You can safely delete the older one. This should correct the EXOLEDB event
0
 
sk_raja_rajaCommented:
To stop the error generating open exchange system manager
Expanded Folders
Clicked Public Folders and on the Action menu chose view system folders
right-clicked on schema-root folder and renamed it to schema so when properties are view it is non_ipm_subtree\schema.
then restart exchange services twice and the original schema-root will be  recreated.
0
 
numb3rs1xAuthor Commented:
sk_raja_raja:

ok, you are just pasting that first post. it's the same post I read and that's where I had the question for clarification. refer to my question for my request for clarification. I can't tell if I do in fact have two schema-root folders.


your second comment, I don't understand what you mean by this part :

right-clicked on schema-root folder and renamed it to schema so when properties are view it is non_ipm_subtree\schema.

Thanks.
0
All Courses

From novice to tech pro — start learning today.