Cisco Bug: CSCuo72702 - Replication of bookings from TMSXE to TMS may not resume after Exchange
Nov 29, 2017
- Cisco TelePresence Management Suite (TMS)
Known Affected Releases
Symptoms: Bookings made in Microsoft Exchange do not replicate to Cisco TMS. Cisco TMSXE's subscription worker threads get into a bad state, where they are unable to pick up changes from Exchange and replicate them to Cisco TMS. Example TMSXE-log-file entries showing the connection problem: 2014-05-08 10:17:18,906  ERROR PullSubscriptionWorker245 - Error while retrieving block of events from Pull subscription with message: The request failed. The remote server returned an error: (503) Server Unavailable. 2014-05-08 10:17:18,914  ERROR SubscriptionWorkItemProcessor - Processing SubscriptionWorkItem for System ID TMS-245 failed. After some retries, subscription worker threads become blocked, and no further entries are written to the log. The example log entries above are also visible in the Windows Event Viewer, under "Applications and Services Logs" > "Cisco TMSXE". Conditions: The issue has been seen after the connection from Cisco TMSXE to the Microsoft Exchange CAS server has been interrupted, for example because one or more of the CAS server's services were down. In most cases, Cisco TMSXE is able to recover once the connection to Exchange is re-established. Cisco is still investigating the exact conditions that could lead to Cisco TMSXE not recovering. Workarounds: Once the Cisco TMSXE Windows service is restarted, it will regain its subscriptions to Exchange, and process all incoming bookings. No data will be lost, as bookings created while the connection was down will be processed and replicated to Cisco TMS after the restart. If using a clustered Cisco TMSXE deployment, restart the service on both Cisco TMSXE nodes.
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