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.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Manikandan NarayanswamySecurity Specialist & IBM Security GuardiumCommented:

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

kitmaxAuthor Commented:
"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,...)
Manikandan NarayanswamySecurity Specialist & IBM Security GuardiumCommented:

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

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

kitmaxAuthor Commented:
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...
Manikandan NarayanswamySecurity Specialist & IBM Security GuardiumCommented:

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.

kitmaxAuthor Commented:
Finally found the "solution".

KB Article Number(s): 2566059
Language: All (Global)
Platform: x64
Location: (

I can run, so think I will migrate to 2013 ASAP...  :-)

Thanks for all the help!!

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
kitmaxAuthor Commented:
Problem went away after application of the patch.  Self found in Google search!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.