jayman7
asked on
Exchange Server 2003 hangs on "Applying Computer Settings"
Hi All,
Ok i'll give you some background. I just performed a VMware P2V on our exchange server. The conversion worked no problem and booted on the new esxi server. However as soon as I installed VMware tools and connected the VM to the network it would not connect to the domain, saying the domain was unavailable or computer account did not exist, I deleted the computer account on the AD server and disconnected and reconnected to the domain. Now when I boot it just gets stuck on "Applying Computer Settings" (been stuck there for hours).
I have logged into the computer using safe mode and removed all unnecessary programs including APC Powerchute and AV which are known to cause this problem.
It seems to login to the domain fine when in safe mode and the are no errors in the event log on the AD server.
There are errors relating to exchange and IIS in the exchange server event log.
Any help would be greatly appreciated.
Thanks,
Jason
Ok i'll give you some background. I just performed a VMware P2V on our exchange server. The conversion worked no problem and booted on the new esxi server. However as soon as I installed VMware tools and connected the VM to the network it would not connect to the domain, saying the domain was unavailable or computer account did not exist, I deleted the computer account on the AD server and disconnected and reconnected to the domain. Now when I boot it just gets stuck on "Applying Computer Settings" (been stuck there for hours).
I have logged into the computer using safe mode and removed all unnecessary programs including APC Powerchute and AV which are known to cause this problem.
It seems to login to the domain fine when in safe mode and the are no errors in the event log on the AD server.
There are errors relating to exchange and IIS in the exchange server event log.
Any help would be greatly appreciated.
Thanks,
Jason
beechy_
Check DNS, this happens on Exchange servers with DNS problems, also it usually eventually boots if you leave it long enough. You can boot into safe mode, disable the Exchnage services, then boot into normal mode should be quick and then you can locate your issue and also start the services again.
Does the machine last long enough to get into the event logs remotly ? you should be able to see any DNS or system irregularities in one of those longs. I'd agree with beechy that its generally a DNS issue, but it depends on what you mean by 'hang' does the system physically 'lock up' or does it just continue on the screen with no visible progress... they are VERY different symptoms.
my guess is the physical network adapter isn't passing information directly to the virtual network correctly. if the VMWare is preforming an new layer of NAT the a/d DNS probably isn't getting to it. you might have to build a route for the new subnet or use it in bridge mode and use the original IP settings
as beechy said DNS will hang up exchange in a hurry.
as beechy said DNS will hang up exchange in a hurry.
Boot into safe mode, set the information store service to disabled then restart the server.
It should boot happily.
Then set the stores to not mount automatically and then set the information store service to automatic and start it.
Then manually mount one store at a time.
When one hangs, that is the one that needs to be repaired.
Reboot the server, repair the broken store and then mount it.
To repair the store, please run:
eseutil /p
eseutil /d
isinteg -s servername -fix -test alltests
Run isinteg until there are 0 errors and 0 fixes in the last line of output.
It should boot happily.
Then set the stores to not mount automatically and then set the information store service to automatic and start it.
Then manually mount one store at a time.
When one hangs, that is the one that needs to be repaired.
Reboot the server, repair the broken store and then mount it.
To repair the store, please run:
eseutil /p
eseutil /d
isinteg -s servername -fix -test alltests
Run isinteg until there are 0 errors and 0 fixes in the last line of output.
You likely lost your static IP settings when installing VMware tools. Exchange definately won't like that and can hang for a very long time if it isn't correct, IIS will also complain if you have bindings to specific IPs.
While in safe mode make sure your IP settings are all correct.
Good Luck
While in safe mode make sure your IP settings are all correct.
Good Luck
I second harel66's comments as the cause.
As alan said, you should boot it in safe mode.
Check your dns settings when you boot in safe mode
You can also run
Dcdiag /fix
After booting
As alan said, you should boot it in safe mode.
Check your dns settings when you boot in safe mode
You can also run
Dcdiag /fix
After booting
Login to system in safe mode, set all the exchange services to manual.
Reboot the server in the normal mode, if you are able to login to the system with domain admin, then you satrt Exchange services one-by-one. Start with Exchange SA.
If you are not able to login to system with domain admin, then first fix that problem and then think of Exchange.
If there are any errors post t here for more infomration
Reboot the server in the normal mode, if you are able to login to the system with domain admin, then you satrt Exchange services one-by-one. Start with Exchange SA.
If you are not able to login to system with domain admin, then first fix that problem and then think of Exchange.
If there are any errors post t here for more infomration
Usually i resolved that in a physical machine disconnecting the cable from the network adapater, login on, and after login on i again connect the cable adapter.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.