Cisco Unified MeetingPlace

Field Notice: FA00224 Deleting a Chain Fails When One Instance Has Been Re-associated With the Same ID

May 26, 2004

Products Affected



MeetingPlace for Outlook and earlier

Problem Description

Note: This Field Notice is a legacy Latitude Field Notice that has been converted to the Cisco format so the information would remain available to their customers.

Schedule a recurring meeting. Disassociate the last instance of the chain and associate the last one, assigning it the same meeting ID as the chain. Then delete the whole chain. Verify on the MP Server that all occurrences had been deleted including the meeting that had been disassociated and re associated. This fails since the meeting that was disassociated and re associated stays on the MPServer.

Problem Symptoms

Inconsistent information on the calendar and the meeting place server.


This issue has been fixed in MeetingPlace Outlook hotfix. Download the hot fix from the Cisco MeetingPlace for Outlook software page.

Installation Instructions:

  1. Replace the existing setup.exe and upgrade.exe in the \latitude\mpweb\mpoutlook folder.

  2. Copy MPOLSchedule.htm to \latitude\mpweb\Template\ folder.

  3. Run ConfigClients.exe. Save and close.

  4. May be necessary to restart MeetingPlace Agent service if template caching is turned on.

  5. Have end-users install by running the setup.exe program (new users) or by clicking the upgrade link on the MeetingPlace for Outlook scheduling form (existing users).

  6. Make sure to restart Microsoft Outlook after upgrading.

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

Receive Email Notification For New Field Notices

Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.