Article ID: 311033 - Last Review: July 28, 2006 - Revision: 1.3

OL2002: You Cannot View Free/Busy Details When You Schedule a Meeting for an Outlook 98 User

View products that this article applies to.

This article was previously published under Q311033

SYMPTOMS

If an Outlook 2002 user creates a new meeting request and invites a Microsoft Outlook 98 user, the Outlook 2002 user cannot view the calendar details for the Outlook 98 user's free/busy information (no details appear with the additional information about the appointment). This behavior occurs even if the Outlook 2002 user has reviewer permissions to the Outlook 98 user's Calendar folder. Microsoft Outlook 2000 users can see the appointment details for the same Outlook 98 user if they have reviewer permissions.

Back to the top

RESOLUTION

To 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: Microsoft Office XP SP-1 must be installed on your computer before you install this hotfix.

The English-language version of this fix should have the following file attributes or later:

   Date           Time  Version    Size       File name     
   -------------------------------------------------------
   20-Dec-2001    17:43   10.0.3618.0  6,306,120  outllib.dll
   20-Dec-2001    17:44   10.0.3618.0     92,488  outlmime.dll
   11-Dec-2001    22:13   10.0.3604.0    534,856  outlcm.dll

After the hotfix is installed, the following files will have the listed attributes or later:

   Date           Time  Version    Size       File name     
   -------------------------------------------------------
   20-Dec-2001    17:43   10.0.3618.0  6,306,120  outllib.dll
   20-Dec-2001    17:44   10.0.3618.0     92,488  outlmime.dll
   11-Dec-2001    22:13   10.0.3604.0    534,856  outlcm.dll

Back to the top

STATUS

Microsoft 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).

Back to the top