grovenetsupport
asked on
SBS 2011 Exchange RPC Client Access wont start
Back with the same problem as before on a previous post. RPC client access wont start and puts error in event log of "Failed to register service principal name ExchangeMDB. Failed with error code The RPC server is unavailable (1722)."
The server has been fine until reboot. I called Microsoft on this but when they logged on the damn service just started so I must have done something correct but still doesn't solve when rebooted. They told me if I ever get the problem again just go into the AD and find the server and change the inheritable permissions on it and all should be fine again. Doesn't really solve the long term issue and doesn't work this time anyway. All I get is service started then stopped.
I have tried nearly every relevant fix google has to offer but to luck any clever ideas people?
The server has been fine until reboot. I called Microsoft on this but when they logged on the damn service just started so I must have done something correct but still doesn't solve when rebooted. They told me if I ever get the problem again just go into the AD and find the server and change the inheritable permissions on it and all should be fine again. Doesn't really solve the long term issue and doesn't work this time anyway. All I get is service started then stopped.
I have tried nearly every relevant fix google has to offer but to luck any clever ideas people?
This is SBS 2011 so this would be Exchange 2010
Have you tried setting the service to Automatic (Delayed Start)?
Have you tried setting the service to Automatic (Delayed Start)?
ASKER
Thanks for the comments. It all seems to hinge around the permissions for the network service as all services loading around this seem to fail. Very weird though as after a long period of time all loads fine and I am talking hours until you reboot again.
I misworded my question - I didn't mean version as in Exchange 2010, I meant as in service pack level. Is the server fully up to date. The problem seems to me to be network related - I have seen this problem myself when the network configuration was wrong.
Simon.
Simon.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for all support on this but did not find a solution
Have you run the EXPBA and SBS BPA against the system to ensure it doesn't flag anything?
It sounds like the network isn't available when Exchange starts, which would point to a network configuration issue. Was the server setup using the wizards?
Simon.