I have a client running Exchange 2003 server as a vm on VMware ESXi 4.1. The server started reporting some errors which are as follows.
"This computer was not able to set up a secure session with a domain controller in domain GBTPS due to the following:
The remote procedure call failed.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator."
Now what we have found is that at some point in the last few months the client changed the domain administrator password and the Active Directory Synch Service on the Exchange server was running using the old Administrator credentials. So that service had not started in perhaps a few months.
We believe that the Exchange Database has been corrupted, possibly because the user was continually rebooting the server as a temporary fix to the issue.
By what process should we repair the exchange database? Microsoft is telling us that they won't support exchange 2003 as a virtual machine so we are kind of on our own. Most instructions we've seen on the repairs tell us to dismount the exchange database before doing anything. The problem is none of the exchange services will start so dismounting at this time is impossible.
Any help would be extremely, and I mean extremely, appreciated.
SB
"This computer was not able to set up a secure session with a domain controller in domain GBTPS due to the following:
The remote procedure call failed.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator."
Now what we have found is that at some point in the last few months the client changed the domain administrator password and the Active Directory Synch Service on the Exchange server was running using the old Administrator credentials. So that service had not started in perhaps a few months.
We believe that the Exchange Database has been corrupted, possibly because the user was continually rebooting the server as a temporary fix to the issue.
By what process should we repair the exchange database? Microsoft is telling us that they won't support exchange 2003 as a virtual machine so we are kind of on our own. Most instructions we've seen on the repairs tell us to dismount the exchange database before doing anything. The problem is none of the exchange services will start so dismounting at this time is impossible.
Any help would be extremely, and I mean extremely, appreciated.
SB
