Hi all; hope everything is fine... Well, as a last resource I´ve decide to post this here, since there is a lot of information over the internet, I couldn´t find a solution: We have a client which still had in it´s organization a Windows 2000 based domain, recently the exchange 2000 server restarted unexpectedly and they had to Join again the organization, this exchange 2000 ran over windows 2000 server. Once the server was re-joined to the domain, the OWA stopped to work, so, when I started the troubleshooting I realize that the PF couldn´t be accesed through the Exchange System Manager, because some DCOM or COM+ errors that couldn´t be fixed following the recommended troubleshooting so, we purposed or suggested to bring a new, fresh windows 2003 server to host the exchange 2000 organization, since the organization is "Mixed Mode" Now I still continue with the PF expand problems, I´ve followed every white paper, every trobuleshooting from microsoft, with no success, so if some of you had the same problem in the past and could fix it succesfully, please share their experience with us..!! The error Im having is: The object is no longer available. Press F5 to refresh the display, and then try again the organization is: Windows 2000 based domain mixed mode Exchange 2000 SP3 over windows 2003 full patched / fixed We don´t use URLscan...! I´ve followed this technet troubleshooting, step by step, with no success, among others that I'd founded in the internet but basically are the same: "Troubleshooting Microsoft Exchange System Manager Public Folder Expansion Problems" http://technet.microsoft.com/en-us/library/aa996098%28EXCHG.65%29.aspx I hope you could help us...!! Thanks for reading..! César Barrios CCS, Venezuela.

I woudl suggest you to do a Disaster recovery for this server .( this is a better and simple solution). http://support.microsoft.com/kb/297289 This would also help .. http://support.microsoft.com/kb/326052 also it is better to switch to Exchange 2010 as this is no more supported by MS.

Hi Khoj... thanks for you help... We already decided to migrate to exchange 2003, keeping the same server name; since our client doesn't has the intention to migrate to Exchange 2010... Regards, Cesar.

Support for exchange 2000 has ended on Jan 10, 2006. So it won’t be any support available when issues occur on the exchange 2000 server, if you don’t have extended support Support Life-Cycle Policy for Exchange 2000 Server If IISlockD, or URLscan is on the exchange server, please see KB 309508 Other resources: You Cannot Expand Public Folders Through Exchange System ManagerJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com