Public Folder Could Not Be Opened

I have a user who is unable to open public folders on her laptop uisng "Outlook 2007 (12.0.6691.5000) SP3 MSO (12.0.6683.5000)" When she tries, the error message:

"Cannot display the folder. The public folder could not be opened because the Microsoft Exchange organization you are connected to does not support public folders."

However, other people can access the public folders, and if she logs on to another desktop, running the same version of Outlook, she can access the public folders.

So far I've done the following:
Checked the versions on the working desktop and the users, and they are the same.
Ran Windows Updates, and installed all updates & hotfixes.
Created a new Outlook profile
Reset public folder permissions, making her a Published Editor

Not sure what else to try now!
bjblackmoreAsked:
Who is Participating?
 
Jeffrey Kane - TechSoEasyConnect With a Mentor Principal ConsultantCommented:
At this point I'm thinking that there may be some misconfigured autodiscover records in the registry.

Review this KB article:  http://support.microsoft.com/kb/2212902

A quick test would be to use the "Test E-mail AutoConfiguration" which you'll find right below the "connection status" you used to post the above info.
0
 
Andy MInternal Systems ManagerCommented:
The fact that she can access it with the same account on another PC (and other users can access them) would lean towards a problem on the pC itself rather than the server.

The next thing Iw ould try is a remove and reinstall of Microsoft office on the affected PC. Also what OS are the PC's running - are they the same?

Also, what version of exchange are you using?
0
 
bjblackmoreAuthor Commented:
Thanks for the reply.

OS is Windows XP (I know, but no upgrade budget). However the test VM is also Win XP, and her accout works on there, but not her XP system.

I'll perform the Office re-install tomorrow, to see if that fixes the issue.

We're currently running hybrid Exchange systems, on premise Exchange 2007, in the progress of migrating to Office 365. All mailboxes have moved over, but public folders are still on premise.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
bjblackmoreAuthor Commented:
Well, spent the past 1 & 1/2hrs uninstalling Office 2007, re-installing, installing SP3, then installing the O365 hotfixes (kb2596598 & kb2687404), then installing all Windows updates.

Deleted the profile, re-created, tried again, and it still failed. Same error! Not sure what else to try now!
0
 
Simon Butler (Sembee)ConsultantCommented:
Does the problem occur to another user on the same machine?
If not, then it is the Windows profile.

Personally I have never seen an Office/Outlook installation resolve this kind of problem. When it comes to machine specific issues I have three steps only to resolve the problem.

1. New Outlook profile.
2. New Windows profile.
3. Wipe the machine.

Simon.
0
 
bjblackmoreAuthor Commented:
Yes, does it with my profile on her machine as well. Today was the first time I'd logged in, so was a new clean profile, tried public folders and got the same error. Yet my laptop works, my test VMs all work.

Only thing I can think left is she also has Visio 2003 installed, so maybe there is a shared dll or something screwing it up! Going to uninstall Visio 2003 and install 2007 tomorrow.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I doubt that it's due to Visio being installed, but rather could be a DNS cache problem on that machine.  

Be sure that autodiscover is pointing to your on-premise Exchange Server for this machine, because it sounds as if Outlook is going directly to Office365 and requesting the Public Folders from there -- and since there aren't any Public Folders in Office 365 you get the error.
0
 
bjblackmoreAuthor Commented:
So you think I should clear out the DNS cache? She has a laptop, so restarts it every day. Is there anyway to point PFs to point to on premise?
0
 
bjblackmoreAuthor Commented:
OK, so today I ran "ipconfig /flushdns", restarted Outlook, same issue. I also added the server names/IPs to the hosts file, just to check, same issue. I'm able to ping each of the servers, and ran a tracert, and got the same output as myself.

When I compare my Connection Status with her's I seem to be able to establish a connection to Public Folders on NAMX01, however her is constantly in a state of 'Connecting, establishing, disconnecting...Connecting, establishing, disconnecting...' It tries to do this with the on premise Exchange 2007 server, and the on premise Exchange 2010 hybrid server. Eventually it gives up, and the "Cannot display the folder. The public folder could not be opened..." error appears.
public-folder-status.jpg
public-folder-status2.jpg
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Is there any kind of 3rd-party firewall on the laptop which may be hampering that connection to the EX2010 server?
0
 
bjblackmoreAuthor Commented:
We have Symantec Endpoint Protection v12.1, but this is installed on dkestops.laptops, and all use the same policy pushed out via the central SEPM server.
0
 
bjblackmoreAuthor Commented:
Thanks for this, I will try to get on the users machine sometime this week to check, and will report back!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.