I installed a new Exchange 2003 server several days ago (cluster, 2-node, active/passive) and migrated approximately 50 users to it a couple of days later. I also moved the OAB, RUS to this new server and created public folder replicas of all public folders and system folders on this new server. Once I migrated my users off the old 2k3 server, I uninstalled it today. It seems that once I uninstalled this server, the free/busy searches stopped working for the users on this new server ONLY, as well as any public folders. I have a much older exchange 2000 server with approximately 1500 users on it who are working with free/busy just fine. I also tried moving a user from the Exchange 2003 server back to the 2000 server and that mailbox started working. The error that the user gets in Outlook 2003 is No information. No free/busy information could be retrieved. I turned up logging on all public folder replication activities and everything looks ok. I removed the replica from this server then re-added it and while it says that it contains the same amount of data as the other replicas, this server is still not able to access any public folders. In addition, I am unable to view the Client Permissions on the free/busy public folder (I can view them on the 2000 server). The error I get is quite long but it's a MAPI error, ID no: 8004011d-0512-00000000. I have followed this procedure before with no issues so I'm not sure why only the users on this particular server are experiencing the problem. I have read through numerous web sites and postings but nothing is coming up as exactly the issue I'm experiencing. Any insight is appreciated.

You can set per mailbox database which PF database to use. Can you ensure that your mailbox databases on the new cluster point to the PF database hosted by the cluster? If they are, then try dismounting and remounting your PF database and even potentially rebooting. Check the application logs to see if there are any issues record there when you do. Good Luck!

I see that the public folder stores for the mailbox databases are pointing to the old server. However, they are grayed out! I cannot change them.

Well you have identified the source of your problem. If the setting is grayed out, then it is most likely being forced/set through a mailbox policy. Under your Administrative group, there should be a policies folder. In there you will probably find at least one mailbox policy. Make the PF change on the policy and Exchange should replicate it out to the server within a few minutes and your problems should be over. I don't think a reboot is required anywhere (client or server) but your clients may need to close Outlook and re-open it after 5-10 minutes.

Thanks to all for the answers but this issue has developed a side problem. I resolved the public folder and free/busy issue. However, ever since I removed that server, whenever I right-click a mailbox store on the new server in questionand select properties, I get the following error: Exchange System Manager There is no such object on the server. Facility: Win32 ID no: c0072030 Exchange System Manager I am able to click OK and get into the properties and make changes as necessary so I'm not sure where this error is coming from. I don't see anything related to it in the event logs. I have tried it on my desktop pc as well as on the server itself. I have also tried it using a different account that has full privileges. I do not get this error on the mailbox stores of other servers. I also don't get this error when I access the properties of the server or storage group objects, just the mailbox stores.This also happens with newly createdmailbox stores on this server.Any info you may have is welcome!

Have you rebooted the server? The reason I ask is because the mail stores could still be upset, and there are other things a reboot resolves (such as when people move the Exchange server computer account in AD with the system attendant running). If that doesn't work, I would suggest removing the mailbox stores from the policy and see if you can edit them manually w/o errors (again this takes a little time to replicate to the Exchange server). Good Luck!

Yes, I will try rebooting them. Should I rebooting each node do the trick, if that is the trick? I'll also try without the system policy, that's a good thought. Thanks, SLW

I rebooted both nodes but no dice. I still get the error whenever I go to the properties of each mailbox store. Any other ideas?

Did you remove the mailbox stores from the mailbox policy? If so, then you should be able to go in an manually update which PF DB to point to, and you shouldn't get the error anymore. If that works, then I would consider creating a new mailbox policy with the correct settings, and just moving all the mailbox stores to it.