Microsoft Exchange Rpc Client Access Not Starting Sbs 2011 Remote

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 coffee. From that point forward all the new Outlook 2013 clients give me this error,

Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost).

Solution

Microsoft Exchange RPC Client Access (SBS 2011 Server Only) Microsoft Exchange Forms Based Authentication (SBS 2011 Server Only) If you attempt to manually start the services, the services should start correctly. The problem occurs in some environments when Exchange is installed on a Global Catalog. The Exchange Team has released a KB article. 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. That is when we discovered that the RPC Client Access service was not starting on a reboot. So, when migrating to SBS 2011, make sure to check the Exchange Services right after a reboot and then make that the first troubleshooting step when something is not cooperating as expected during the migration process. I'm tring to troubleshoot a problem with sending data from a light forwarder to a splunk server. In this particular case, the clients are 2 Windows 2008 R2 boxes running the 'Client access server' role for exchange 2010. The splunk server is a redhat linux 5 64 bit box. Both are running splunk 4.1.4.

1. At first I thought this was a user profile problem, so i logged on as another user (no difference). So I thought it was a problem with Outlook/Office on that PC. Until I built another one and it did the same. If you are seeing this error I suggest you remove the Outlook profile on the affected machine first.

2. Some Google searching told me this can happen if certain services have not started, as I had this problem on the same server, I checked the services and sure enough the Microsoft Exchange RPC Client Access’ service was not running. I could manually start it, and the error ceased. That’s great but I needed to deliver the server to a client and I wouldn’t be about to manually start services every time they rebooted it!