Hi,

after migrating to Exchange 2013 several month ago, I can't get public folders access from Outlook 2007 for PC working. Primary mailbox access is fine, when trying to open the public folder tree, the following error message appears:

Cannot expand the folder. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance.

The problem appears exactly like described here: https://support.microsoft.com/de-de/kb/2839517/en-us

Access to public folders from Outlook for Mac and Entourage works without any problem. Outlook 2013 didn't work by default, but works after applying KB2863843 (guess this is a culmulative hotfix pack which also includes 2817347 as described in the upper mentioned KB article).

Unfortunetely, I still can't get Outlook 2007 to access the public folders. The August 13, 2013 hotfix package *is* installed, but the error remains the same. Since the hotfixed Outlook 2013 for PC works as well as Outlook for Mac and Entourage, I bet that this is not an exchange server issue.

Does any froum you uses Outlook 2007 to access Public Folders on an Exchange 2013 Server successfully? Have you any Idea where I coult start digging in this issue?

Best regards

Holger

Hi,

According to your description, I understand that Outlook 2007 client cannot access public folder with error Cannot expand the folder. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance, however Outlook 2013 client and Outlook for mac works well.
If I misunderstand your concern, please do not hesitate to let me know.

Do you have migrate public folder to Exchange 2013 yet? If not, please implement this as below link:
https://technet.microsoft.com/en-us/library/dn912663(v=exchg.150).aspx
Conversely, we can configure legacy public folders where user mailboxes are on Exchange 2013 servers as mentioned below:
https://technet.microsoft.com/en-us/library/dn690134%28v=exchg.150%29.aspx

Meanwhile, Outlook 2007 SP3 with November 2012 Cumulative Update is full supported for Exchange 2013. Please upgrade to latest version for testing.
I find an similar thread about Outlook cannot expand public folder in coexistence environment, for your reference:
https://social.technet.microsoft.com/Forums/office/en-US/642f7382-4b3d-421c-ab16-ec0d0f47dfa0/outlook-2007-prompts-for-login-when-accessing-public-folders?forum=exchangesvrgeneral
https://social.technet.microsoft.com/Forums/en-US/5a62266e-2179-4a6f-9b1c-b39fe8aa6692/user-in-exchange-2013-mailbox-cannot-access-public-folder-in-exchange-2010?forum=exchangesvrdeploy

Thanks

Hi Allen,

thanks for taking time with my issue. You've understood the problem 100% correct. However, the migration is completely finished and the old server is removed. All mailboxes - as well as the Public folder container - reside on the new server, Exchange 2013 CU7, multi role, single server.

The client version reads: Outlook 2007 (12.0.6691.5000) SP3 MSO (12.0.6721.5000)

Thanks for finding more ressources. Except of the last one, they did not apply. Regarding the last one, I tried to remove "Negotiate" from "Default Web Site/Rpc/" and reset IIS. Unfortunately, this did not solve the problem as well.

There are two more issues with public folders, which I do not see in connection with this issue. However, I explain for reference:

1) If I use EAC to change the root access rights of the whole ipm_subtree (plus subfolders), or the access rights of a public folder tree which contains subtrees with several elements, after running for about 10 minutes, it stops with the following error message:

Error: The array dimensions have exceeded the supported range.

Having the ressource monitor open while performing this operation, you can see that the server is slowling running out of memory. While not having digged in this issue further, I'd assumed that 16GB RAM may probably be a bit insufficient.

2) Using OWA, I can open the IPM_SUBTREE, and can see (and browse through) all the folders and subfolders. However, its impossible to add any of the folders to favorites due to the following error:

Only mail public folders can be added to favorites.

The key is: Indeed thes are mail public folders (if I've got that right: A folder which only contain mail elements). Even empty folders cannot be added. I haven't further digged into that issue.

Best regards

Holger

Hi Allen,

thanks for taking time with my issue. You've understood the problem 100% correct. However, the migration is completely finished and the old server is removed. All mailboxes - as well as the Public folder container - reside on the new server, Exchange 2013 CU7, multi role, single server.

The client version reads: Outlook 2007 (12.0.6691.5000) SP3 MSO (12.0.6721.5000)

Thanks for finding more ressources. Except of the last one, they did not apply. Regarding the last one, I tried to remove "Negotiate" from "Default Web Site/Rpc/" and reset IIS. Unfortunately, this did not solve the problem as well.

There are two more issues with public folders, which I do not see in connection with this issue. However, I explain for reference:

1) If I use EAC to change the root access rights of the whole ipm_subtree (plus subfolders), or the access rights of a public folder tree which contains subtrees with several elements, after running for about 10 minutes, it stops with the following error message:

Error: The array dimensions have exceeded the supported range.

Having the ressource monitor open while performing this operation, you can see that the server is slowling running out of memory. While not having digged in this issue further, I'd assumed that 16GB RAM may probably be a bit insufficient.

2) Using OWA, I can open the IPM_SUBTREE, and can see (and browse through) all the folders and subfolders. However, its impossible to add any of the folders to favorites due to the following error:

Only mail public folders can be added to favorites.

The key is: Indeed thes are mail public folders (if I've got that right: A folder which only contain mail elements). Even empty folders cannot be added. I haven't further digged into that issue.

Best regards

Holger

We have had issues with clients connecting to Public folders and it's usually linked to saved credentials in "Credential Manager" on the local workstations. I would try removing any entries in there related to the users AD account or email account.

We have had issues with clients connecting to Public folders and it's usually linked to saved credentials in "Credential Manager" on the local workstations. I would try removing any entries in there related to the users AD account or email account.

No, it looks like the problem is Windows XP related (no commments about still using them on our workstations please. If I would have a vote, these would be already gone).

Ok, here's what I tried: I performed a clean install of Windows 7 Pro + all updates. Installed Outlook 2007 + all updates (12.0.6691.5000) SP3, and it worked. Primary mailbox worked instantly, however, I had to add my self signed server certificate to the list of thrustworthy certificate authorities, otherwise I could not access public folders + get a proxy error message on starting outlook.

Then I performed a clean install of Windows XP SP3 (desecration of a corpse :-) + all updates. Installed Outlook 2007 + all updates (same patch level as like as above). Primary mailbox is ok, public folders won't work, regardless if I add the certificate or not. Also no proxy error message at any time.

Any Ideas?

Best regards

Holger

I've removed the outlook profile on XP once again and applied certificate prior creating a new outlook profile. The behaviour changed this was:

The server can be connected and the primary mailbox can be accessed without problems. When clicking to open the public folders tree, a login prompt appears (Connect to exchange.contoso.loc) which does not accept any known credentials. The only possibility is to cancel. From that point of time, outlook is in offline mode. On the next launch of outlook, the login prompt appears immediately and again does not accept any credentials. After cancelling, outlook remains in offline mode. This continues unless I remove the outlook profile and create a new one. Outlook is online again then with no login prompt, unless you click to open the pulic folders tree. Then this repeats.

This behaviour does not happen if the certificate is not installed. Outlook simply won't access public folders then, but keeps working as usual.