Public folder issue
Hi GuysHave a funny issue that i need to diagnose on public folders and have no idea where to start looking for thisI run a 2003 Exchange organisation that run on a 2 node cluster. When exchange is active on serv1 i have no issues but when i fail over to serv2 clients have issues connecting to some of the public folders. The outlook client tries to connect and basically takes a long time to connect toteh folder and retrive the information for it. My outlook client is not running in cache mode but i have the same issue in cache mode.Does anyone have any suggestions for me here?Thanks
April 15th, 2010 8:09am

It would figure that cached mode wouldn't make a difference unless you had manually configured the folder you're using to be available offline (synchronized). Aside from that comment I can't fathom why this would occur. Does this happen for all users? You might try opening the connection status (hold Ctrl and click on the Outlook icon in the system tray, then select Connection Status) to verify that Outlook is talking to the correct host for public folders. For a cluster it's supposed to be trying to use the cluster hostname, not the individual node hostnames.-- Ed Crowley MVP"There are seldom good technological solutions to behavioral problems."."Overgrownboy" wrote in message news:f8787412-42f4-4437-a8a8-f25e763920c3...Hi GuysHave a funny issue that i need to diagnose on public folders and have no idea where to start looking for thisI run a 2003 Exchange organisation that run on a 2 node cluster. When exchange is active on serv1 i have no issues but when i fail over to serv2 clients have issues connecting to some of the public folders. The outlook client tries to connect and basically takes a long time to connect toteh folder and retrive the information for it. My outlook client is not running in cache mode but i have the same issue in cache mode.Does anyone have any suggestions for me here?ThanksEd Crowley MVP "There are seldom good technological solutions to behavioral problems."
Free Windows Admin Tool Kit Click here and download it now
April 17th, 2010 8:08pm

Hi Ed Thanks for your insight. This is a very weird error as with a cluster you would expect the same result on a resource no matter which host is active. In this case I am only plagued by this issue on one of the hosts in the cluster. This issue also affects all users when i fail over to the affected machine I unfortunately am very new to the exchange game and need to grow my confidence on exchange a bit. I think there could be some mis-configuration on the affected host, other than using the ESM console, where else can I can I look at the configuration of the public folders on the servers? Also could this be an issue with a corrupt view that is on the servers and how can i clear the views cache?
April 20th, 2010 7:41am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics