Cisco Bug: CSCup76424 - Duplicate ExternalPrimaryKeys in ConferenceSchedule leads GetConferenceB
Sep 07, 2014
- Cisco TelePresence Management Server
Known Affected Releases
Symptom: Meeting created by TMSXE is in TMS, but is not seen in the resource calendar in Exchange. Conditions: Original meeting was booked while using a TMS version < 14.4.0 and the meeting was deleted or had the telepresence systems removed from the meeting, and later re-added. The meeting was created via a TMS Conference template in a version of TMS older than 14.4.0 The TMSXE replicator log traffic will show TMSXE doing a getConference for an ExternalPrimaryID for the meeting, but get a different meeting with the same ExternalPrimaryKey back from TMS. In TMS's database you can find multiple ConferenceSchedule items with the same ExternalPrimaryKey column value.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases