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

Using Workgroup Manager on Mac OS X Server to set the homepage for a group of Macs in your Apple environment

So my first post about managing Macs.  We have a lab of them, not a large amount but it would take a considerable amount of time to log onto each one and change the settings on each one (which we’ve done in the past mind you).  So to add to the blog I will also […]

How to allow an Active Directory Certificate Authority to generate Certificates with a Subject Alternative Name attribute

Starting with Google Chrome 58, Chrome no longer trusts certificates without the Subject Alternative Name attribute, so this makes it a little troublesome for those with internal CAs where you rely on them for Software Development. We noticed last week that some end users couldn’t hit an internal application over HTTPS, but was fine in […]

BackupExec unable to read or write to the Database

Today when checking one of the servers I manage, I got an error when opening up the BackupExec 12.5 management console. The error was “Unable to read or write to the Database” which I found a bit puzzling. I checked to make sure SQL Server which hosted the BE database was running, and it was. […]