A Windows System Admin's Blog

Covering Server Administration, Endpoint Management, Scripting and Network Management

When viewing Public Folders in Outlook you recieve the following error, Cannot expand the folder. Microsoft Exchange is not available.

,

So there have been quite a few posts about Exchange 2010 lately, I guess it’s mainly because that has been my focus for the last few months at my current job. So here is another one regarding an error message when you try to access public folders in outlook and how to fix it.

We were receiving calls that users were unable to access their public folders (which contains our global calendar) We were able to replicate the issue on our own accounts and received the following message.

Cannot expand the folder. Microsoft Exchange is not available.
Either there are network problems or the Exchange server is down
for maintenance. (/o=First Organization/ou=Exchange
Administrative Group (DOMAIN)/cn=Configuration/cn=Servers/cn=SERVERNAME

So we quickly remoted into our server which published our Public Folders, started the public folder tool and could see them all there, also running the get-publicfolder PowerShell cmdlet ran and listed all of the available public folders.  I then decided to take a quick look at the services which were running.

Public Folders are pushed to Outlook clients via Microsoft Exhcnage RPC Client Access Service, and if stopped you are unable to browse for public folders and get the above error.  In our case we were able to simply start the Service and the Public Folders were vieable in Outlook again.  I’ve heard of some isntances where the service no longer starts, if that is the case then you may need to check on permissions in the Bin folder inside Exchange.

 

2 responses to “When viewing Public Folders in Outlook you recieve the following error, Cannot expand the folder. Microsoft Exchange is not available.”

  1. Cody Avatar
    Cody

    I have this exact issue with Exchange 2010 SP3 Rollup 2. However, this service is not the issue and restarting it on any of the Exchange servers doesn’t resolve the issue.

    Public folders load fine if your local on the LAN or using webmail. However, if you are connected via Outlook Anywhere that error gets generated.

    I’m concerned the latest rollup 2 for SP3 on 2010 is causing this. I’ve posted in the Exchange TechNet forums hoping for an answer.

    Reply
    1. John Avatar
      John

      I’ve been holding off from installing the latest and greatest in updates from Microsoft recently. There were issues with DPM roll ups, Hyper-V updates and Exchange Roll ups.

      Reply

Leave a Reply

More Posts

Publish Remote Apps and Desktop Session at the same time

I was recently building a PoC Lab environment for a client where I only had a couple of virtual machines to play with to build a Remote Desktop Services environment to host a line of business application. I needed to be able to publish the application as a Remote App as well as have a […]

Activating Windows 8.1 clients on a KMS Host running Windows Server 2008 R2

I was recently helping out a friend who had a KMS server activating their Windows 7 machines but when they started moving their fleet to Windows 8.1 they saw they couldn’t install the KMS Host product key for Windows 8.1 recieving the following error: 0xc004f015: The Software Licensing Service reported that the license is not […]

Enable a user to Change their Password if it has Expired using OWA for Exchange 2010 and 2013

If you work in a place with a lot of remote users and a password policy with expiration set then you need to give your users a way to reset their passwords.  Microsoft ISA / TMG configured with forms based authentication were able to do this out of the box.  The good news is Exchange […]