OL98: If Appointment Is Dragged from a Public Folder to a Personal Calendar Folder Synchronizing Stops (214834)



The information in this article applies to:

  • Microsoft Outlook 98

This article was previously published under Q214834

SYMPTOMS

If you develop a custom calendaring application that uses public folders to hold the appointments, users can drag appointments from the public folder to their personal Calendar folder. If the appointment is created via a custom form and the form has custom properties, dragging the appointment from the public folder to the personal Calendar folder may stop Outlook from synchronizing with the user's personal Calendar folder on the Microsoft Exchange Server.

CAUSE

Data from custom fields on custom forms are stored in named properties. When an appointment was dragged from the public folder to the user's personal calendar, it is initially put into the calendar cache in the Offline folders (OST). Periodically, the OST will synchronize with the calendar on the user's Exchange Server.

There was a logic error in Outlook that caused a named property to be incorrectly added to the property set on the private folder information store. When Outlook tried to synchronize the Calendar folder, it would try to map the ID of the named property to a name. Since the named property was incorrectly added, Outlook could not map it, and synchronizing stopped.

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web: The English version of this fix should have the following file attributes or later:

File name     Version
---------------------
Outllib.dll   8.5:6023.0
					


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Modification Type:MinorLast Reviewed:9/22/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbQFE KB214834