Microsoft Exchange RPC Client Access will not start.

Question

_{Monday, January 19, 2015 5:22 PM}

A few days ago all my outlook clients were disconnected.  Looking into it and the Microsoft Exchange RPC Client Access service had died.  Tried several restarts of the system but the service will not go into a running state.  It always says Starting. But it is actually terminating and restarting.  In the system log get Event 7031 - "The Microsoft Exchange RPC Client Access service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service."  I can't find anything else on the error in any log file.  Some other info not sure if this related or not.  The contentIndex are corrupt and will not rebuild. Get a state of "Failed" with an error message of "The database has been dismounted."  Also at time the system is very sluggish.  Mostly right after a reboot for an hour or two.  Details about the system are; Running Exchange 2013 SP1 on server 2012 R2.  All roles on one machine.  About 20 mailboxes. Database is about 40gig. No VM, just a normal server. plenty of diskspace, memory and CPU.   The system has been running fine for about a year.  Also, mobile devices and OWA work fine.  Mail flow is fine.  Outlook just can't connect.  

Tried restoring the databases and logs from before the problem started but that did not help.

Not sure what to try from here.

Thanks

All replies (3)

_{Tuesday, January 20, 2015 1:01 PM ✅Answered}

Hi,

Thanks for the responses.  I have resolved the issue.

Amit, I did not want to install CU7 because it was one way and I was worried one of my 3rd party apps would not like it.

Winnie, Yes there was a bad pointer in msExchHomePublicMDB.  I clear it, wait a few minutes and stop and restarted all the exchange services.  But the RPC client access would not start.  In about 5 hour I tried stopping and starting all the exchange service and still no luck.  I did not reboot, was that bad?

At this point I did a system-state restore from backup before I was having an issue.  After the restore I rebooted and the system was back to normal.  Even the content indexes were being rebuilt.

Thanks for all your help.

_{Monday, January 19, 2015 11:43 PM}

I would start installing latest cumulative update when I see any service/process crash as it might have been resolved in newer updates..

Cumulative Update 7 for Exchange Server 2013 (KB2986485) - http://www.microsoft.com/en-us/download/details.aspx?id=45221

But I would find why it doesn't show correct time and mound the database. You can disable the ContentIndex temporary to see if databases are getting mounted or not...

Amit Tank | Exchange - MVP | Blog:

exchangeshare.wordpress.com 

_{Tuesday, January 20, 2015 8:40 AM}

Hi,

Please check whether an unavailable Public Folder database is pointed to in your Exchange 2013 mailbox database as the default public folder database setting.

If there is no legacy public folder database and you are working in a pure Exchange 2013 environment, please remove the default public folder database setting on each Exchange 2013 Mailbox database that points to the deleted public folder database object in ADSI Edit:

1. Open ADSIEdit, Connect to the Configuration container.

2. Expand Configuration, expand CN=Configuration,DC=Domain,DC=com.

3. Expand CN=Services -> CN=Microsoft Exchange -> CN=Domain -> CN=Administrative Groups -> CN=Exchange Administrative Group -> CN=Databases.

4. In the right hand pane you will see a list of databases. Right-click the listed database object -> Properties.

5. Check whether the msExchHomePublicMDB value is set to an unavailable value. If you see reference to the old database, please clear the value.

6. Click OK.

7. Check the rest of the databases to make sure that they are not populated in the same way.

For more information about this, please refer to:

http://support2.microsoft.com/kb/2962915/en-us

Regards,

Winnie Liang
TechNet Community Support