Microsoft Exchange RPC Client Access Service Does Not Start. Home » Exchange » Microsoft Exchange RPC Client Access Service Does Not Start. KB ID 0000802 Problem. I build a new SBS 2011 environment last week, and I had just put on the new digital certificate, and as no one was using it, I simply rebooted the SBS Server and went for a.
- Microsoft Exchange Rpc Client Access Not Starting Sbs 2011 Remote Start
- Microsoft Exchange Rpc Client Access Not Starting Sbs 2011 Remote Control
I was called on to troubleshoot an issue with Microsoft Exchange Information Store not starting recently. All other Exchange services were up and running, but the Information Store wouldn’t start and produced the following error:
“Windows could not start the Microsoft Exchange Information Store on the Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to the service specific error code – 2147221213.”
Microsoft Exchange Rpc Client Access Not Starting Sbs 2011 Remote Start
As the error message suggested I took a look in the System Event log and spotted the following Event.
- Find answers to SBS 2011 Exchange RPC Client Access wont start from the expert community at Experts Exchange.
- I have inherited a new SBS 2011 Standard server that the client has no plans on using Exchange or Share Point. Since SBS is such a fickle beast I would like to know if there is any way to safely disable Exchange and Share Point without creating problems down the road.
Source: MSExchangeIS
Event ID: 5003
“Unable to initialize the Information Store service because the clocks on the client and server are skewed. This may be caused by a time change either on the client or on the server, and may require a restart of that computer. Verify that your domain is correctly configured and is currently online.”
Sure enough the time on the Exchange server was significantly different to the DC after a recent reboot.
To synchronise the time between them I ran the following command.
net time servername /set /y
This brought the time into line on the Exchange Server, but the Information Store still wouldn’t start.
To successfully start the Information store, I restarted the Microsoft Exchange Active Directory Topology service. This restarts all the other Exchange services and should successfully start the Information Store.
Don’t forget to troubleshoot the root cause of the time skew!
End of article
Related Articles:
1. How to install Exchange 2016 (CU3 and beyond) on Windows Server 2016
2. Exchange 2010 SP3 Update Rollup 16 released and installation tips
3. Exchange 2013 Cumulative Update installation tips and best practices
4. How to connect to and manage Office365 using PowerShell
I have recently needed to decommission Exchange on several 2011 Small Business Servers.
This is generally not recommended as it can easily break some of the functionality of the SBS.
However, in several cases I have dealt with, the client’s mail has been migrated to a Hosted Exchange platform or to Office 365 and Exchange was no longer required. Additionally disk space was running low and Exchange was an easy-ish target for reclaiming space and allowing the SBS to continue running for a few more months before decommissioning.
It is generally considered best practice to simply disable all the Exchange services until the SBS is fully decommissioned and I would highly recommend this if at all possible.
That said, the following is what I have found was required to decommission Exchange with minimal breakage.
(As stated the following is not supported or recommended so proceed at your own risk! I HIGHLY recommend taking a full restorable backup before continuing)
Initial Decommissioning
To go through the initial steps of the Exchange decommissioning, the blog post by ITProMentor was very helpful.
After running Exchange Management Shell as Administrator the following commands can be entered, answering prompts with “A” for ALL.
At this stage Exchange should be fairly bare.
Resolving public folder database removal failure
However, in all cases I have dealt with, the commands to remove the public folder database failed with the following or similar:
The post by Todd Nelson was very helpful in this regard as ADSIedit was needed to remove the public folder database.
Using ADSIedit can be very dangerous, so for the second time, proceed at your own risk.
IN ADSIedit I browsed to the following location:
Under this location I deleted the object for the public folder database.
In one case I also had to browse through the Exchange Administrative Group and remove another reference to a previous Public Folder Database that had not been correctly removed.
Uninstall Exchange
Having done this I was able to uninstall Exchange as follows:
In an elevated command prompt, browse to the Exchange BIN folder and run the setup in uninstall mode:
If all went well, this will run through some checks and then proceed to uninstall Exchange.
In one case I needed to kill a process that was locking some of the files and then re-run the setup in uninstall mode.
At this stage I would highly recommend a reboot.
This is where most guides I have found stop, and in some cases this is fine.
However, I have found that if Remote Web Workplace was used for remote access to a terminal server or PC’s this functionality is now likely to be broken.
Examining the event logs will likely show errors as follows:
After some searching I found an article by Wayne Small at sbsfaq which was very helpful.
Resolve kerbauth.dll errors
The solution is as following:
Open notepad as administrator and use File > Open to open the applicationHost.config file in the following directory. C:WindowsSystem32inetsrvconfig
Microsoft Exchange Rpc Client Access Not Starting Sbs 2011 Remote Control
Use the find feature to find the line containing Kerbauth and remove the entire line.
Save and close the file then run iisreset in an elevated command prompt.
This should resolve the Kerberos errors in the event logs.
However, the remote desktop gateway is likely to still be broken.
Fix Remote Desktop Gateway
After a lot of research into Exchange, IIS, Remote Desktop and RPC I was able to find the following solution.
Open IIS Manager and navigate to the Default Website, right click on “rpc” and click explore.
This should take you to: C:WindowsSystem32RpcProxy
In this location there will be a web.config file which will contain multiple references to Exchange files which are no longer in place.
Simply deleting this web.config file in it’s entirety and issuing another iisreset in an administrative command prompt should restore the Remote Desktop Gateway functionality to working order.
I have not encountered any further issues caused by the removal of Exchange in this manner.
Hopefully this post has been helpful and has saved you the hours of google I had to go through.