Turned out to be a service that was stopped on our Exchange server. Thanks anyways.

• Marked as answer by Melon Chen CHNMicrosoft contingent staff, Moderator 6 hours 34 minutes ago

Hi,

It's the first time I've seen this issue, are you working in Cached Exchange Mode? If you switch to Online Mode, does the problem persist?

As a test, please let one user who is affected create a new Outlook profile, check if the problem persists.

Please also disable any integration with Outlook, like 3rd-party add-ins, then try again. We can perform a clean boot to determine whether this issue is related to background program conflict.

Regards,

Melon Chen
TechNet Community Su

Yes, I have tried turning off cached mode, and also creating a new profile, but that does not fix the problem. I ended up opening a ticket with Microsoft support, so I will update this post with the results.

Microsoft Exchange RPC Client Access

• Marked as answer by Melon Chen CHNMicrosoft contingent staff, Moderator 6 hours 34 minutes ago

Turned out to be a service that was stopped on our Exchange server. Thanks anyways.

All my clients (Outlook 2013) seem to be running into an issue when trying to access their Public Folders under "Other Calendars" in Outlook. UserA has 10 calendars listed under "Other Calendars". These are referencing a calendar on our Public Folder store. When you click on one of these calendars under "Other Calendars", the calendar link disappears. Weirdest thing. So then you try the next one, and that one disappears too. So I close out Outlook, and run "outlook.exe /resetnavpane", and then the calendars work and are accessible within the "Other Calendars" listing in the Calendar section. Close Outlook again, open it up, and same problem happens all over again. So we have to run the /resetnavpane command every time to get them to work.

Any ideas?

Thanks.

Hi RBanse,

Thank you for sharing this.

Regards,

Melon Chen
TechNet Community Su

Hi RBanse,

As you mentioned the "/resetnavpane" could get it to work every time, I didn't think the cause was on Exchange. I'm glad to hear it was resolved anyway.

If you could let me know which service on Exchange needs to be turned on in this scenario, it will also be helpful to other users who have this issue and see this thread.

Regards,

Melon Chen
TechNet Community Su