Microsoft Exchange RPC Client Access - Wont Start
Having difficulties after upgrading my DC from 2008 R2 to 2012 R2. Now my Exchange Server 2010 SP3 RU9 running on Server 2008 R2 SP1 was hanging at "Applying Settings..." until I stopped all the Exchange services.
Manually starting the services works, all except "Microsoft Exchange RPC Client Access". It gives me the boiler plate "..some services stop automatically...", but without it none of my OWA clients can connect.
Been ALL over the net, seems to be a pretty regular issue, but cant find anything that fixes this.
Manually starting the services works, all except "Microsoft Exchange RPC Client Access". It gives me the boiler plate "..some services stop automatically...", but without it none of my OWA clients can connect.
Been ALL over the net, seems to be a pretty regular issue, but cant find anything that fixes this.
ASKER
"Is your OLD DC still in production"
Once I demoted DC1 (2008) I shut it down. DC2 (2012) has been the only DC running.
"restart the Microsoft Exchange AD Topology service "
Rebooted multiple times, so I would assume this would do that?
More information: (was late last night and should have said this earlier)
Small home network, NAT behind Cisco E4200 (running DD-WRT)
Only one domain and domain server.
Servers are all VM's running on ESXi 5.1 (hardware is a HP ML150 G6)
DC1 - 2008 R2 (shutdown and disabled from starting)
DC2 - 2012 R2
FS2 - 2012 R2 (file/print server)
MAIL - 2008 R2 SP1 (Exchange Server 2010 SP3 RU9)
ADMIN - WIN7 (runs vSphere client, automated tasks,...)
Once I demoted DC1 (2008) I shut it down. DC2 (2012) has been the only DC running.
"restart the Microsoft Exchange AD Topology service "
Rebooted multiple times, so I would assume this would do that?
More information: (was late last night and should have said this earlier)
Small home network, NAT behind Cisco E4200 (running DD-WRT)
Only one domain and domain server.
Servers are all VM's running on ESXi 5.1 (hardware is a HP ML150 G6)
DC1 - 2008 R2 (shutdown and disabled from starting)
DC2 - 2012 R2
FS2 - 2012 R2 (file/print server)
MAIL - 2008 R2 SP1 (Exchange Server 2010 SP3 RU9)
ADMIN - WIN7 (runs vSphere client, automated tasks,...)
Hi,
Did you find any event logs related to Microsoft Exchange RPC Client Access service in event viewer. Well to be frank exchange services should come up automatically without user intervention is the still problem still same means you need to start the services manually
Thanks
Manikandan
Did you find any event logs related to Microsoft Exchange RPC Client Access service in event viewer. Well to be frank exchange services should come up automatically without user intervention is the still problem still same means you need to start the services manually
Thanks
Manikandan
ASKER
I have that single service disabled, so my server will boot. (otherwise I get "Applying settings... and hang)
When trying to manually start it, all I get in the System Event Log is:
"The Microsoft Exchange RPC Client Access service entered the stopped state."
Event ID: 7036
Yeah, never had an issue before, so think it is related to the DC upgrade.
But can't find anything wrong, no logs,... I don't know why it even won't start. Lovely MS...
When trying to manually start it, all I get in the System Event Log is:
"The Microsoft Exchange RPC Client Access service entered the stopped state."
Event ID: 7036
Yeah, never had an issue before, so think it is related to the DC upgrade.
But can't find anything wrong, no logs,... I don't know why it even won't start. Lovely MS...
Hi,
As per my finding this issue was related to memory leak in RPC Client Access Service. However this is already been fixed in Update Rollup 3. And it seems you are already on Update rollup 9. I would recommend you too raise a ticket with Microsoft to address because if you're are on the latest update rollup you should not encounter this issue
Refer the below links for details.
https://support.microsoft.com/en-us/kb/2529939
https://www.experts-exchange.com/questions/26874442/The-Microsoft-Exchange-RPC-Client-Access-service-entered-the-stopped-state.html
Thanks
Manikandan
As per my finding this issue was related to memory leak in RPC Client Access Service. However this is already been fixed in Update Rollup 3. And it seems you are already on Update rollup 9. I would recommend you too raise a ticket with Microsoft to address because if you're are on the latest update rollup you should not encounter this issue
Refer the below links for details.
https://support.microsoft.com/en-us/kb/2529939
https://www.experts-exchange.com/questions/26874442/The-Microsoft-Exchange-RPC-Client-Access-service-entered-the-stopped-state.html
Thanks
Manikandan
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Problem went away after application of the patch. Self found in Google search!
You mentioned that you upgraded your DC to 2012 R2. Is your OLD DC still in production normally when you remove the DC from the AD forest you need to restart the Microsoft Exchange AD Topology service which forces exchange to detect the dynamically discover new DC. If you already did that and still you face issues try to change the DC from the management console and see if it points to the OLD DC. If yes point it to the new DC and reboot the system and see if exchange services start automatically.
Also check in event viewer for any errors for starting RPC Client Access Service and send those errors to us
Thanks
Manikandan