Article ID: 306327 - Last Review: July 28, 2006 - Revision: 1.3 OL2002: Error Message When You View Replica of Child FolderThis article was previously published under Q306327 SYMPTOMS
When you try to view a replicated child folder, you receive the following error message:
Unable to display the folder. Microsoft Outlook could not access the specified folder location. The contents of this public folder are currently unavailable. Either the Microsoft Exchange Server computer servicing this public folder is down or the public folder has not been replicated to this site. See your administrator. CAUSE
When Outlook 2002 tries to access the child folder, Outlook 2002 tries to build a Uniform Resource Locator (URL) list by accessing the parent folder as well. Because the parent folder is not replicated, Outlook 2002 cannot access it. Therefore, you receive the error message.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Microsoft Office XP. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
307841
(http://support.microsoft.com/kb/307841/EN-US/
)
OFFXP: How to Obtain the Latest Office XP Service Pack
NOTE: This is a post-SP1 fix, which means it requires Outlook 2002 Service Pack 1 installed prior to installing this fix.The fix should have the following file attributes or later: Date Time Version Size File name -------------------------------------------------------- 12-Dec-2001 05:13 10.0.3604.0 534,856 Outlcm.dll 21-Dec-2001 00:43 10.0.3618.0 6,306,120 Outllib.dll 21-Dec-2001 00:44 10.0.3618.0 92,488 Outlmime.dll 29-Nov-2001 07:21 10.0.3527.0 47,432 Recall.dll WORKAROUND
When you replicate public folders, make sure that the parent public folder is also replicated. Alternatively, you can use earlier versions of Microsoft Outlook such as Microsoft Outlook 2000 or Microsoft Outlook 98 to access the child folder.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Office XP Service Pack 2 (SP-2).
| Article Translations
|
Back to the top
