baysysadmin
asked on
Exchange 2013 Services not starting
Today our exchange vm crashed and we had to restart it.
Upon reboot the Info Store service and bunch of others would not start, they get stuck in starting.
I found out the IS was in dirty state so I used recovery to get it to clean state.
Now IS eventually started but these services would not
MSExchangeThrottling
MSExchangeUM
MSExchangeUMCR
MSExchangeRPC
The event logs are complaining about topology and not being able to get to domain controller on bunch of different errors.
But nothing has changed on the network.
MSExchange ADAccess event id 2112
MSExchange ADAccess event id 4027
MSExchangeADTopology 2069
MSExchangeRepl 2155
MSExchangeThrottling 1002
I tried to use policytest.exe on exchange CD to verify AD connection, but I cant find that file anywhere
it should be in
CD \Setup\ServerRoles\Common
other things iver tried.
make sure IPv6 is ON
make sure clock is synched
Upon reboot the Info Store service and bunch of others would not start, they get stuck in starting.
I found out the IS was in dirty state so I used recovery to get it to clean state.
Now IS eventually started but these services would not
MSExchangeThrottling
MSExchangeUM
MSExchangeUMCR
MSExchangeRPC
The event logs are complaining about topology and not being able to get to domain controller on bunch of different errors.
But nothing has changed on the network.
MSExchange ADAccess event id 2112
MSExchange ADAccess event id 4027
MSExchangeADTopology 2069
MSExchangeRepl 2155
MSExchangeThrottling 1002
I tried to use policytest.exe on exchange CD to verify AD connection, but I cant find that file anywhere
it should be in
CD \Setup\ServerRoles\Common
other things iver tried.
make sure IPv6 is ON
make sure clock is synched
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Next time you re-run prep domain command. That will fix all your permission issues.
ASKER
I tried the prep cmd as well, it failed.
And there were no permissions issues. It was group policy which prep cmd would not touch.
And there were no permissions issues. It was group policy which prep cmd would not touch.