Guest

Preview Tool

Cisco Bug: CSCuo60458 - Booking Service - client session id is expired

Last Modified

Jun 27, 2017

Products (1)

  • Cisco TelePresence Management Suite (TMS)

Known Affected Releases

TMSXE4.0

Description (partial)

Symptoms:

Users cannot schedule telepresence meetings through Cisco TMSXE; the meeting requests are declined by Cisco TMS because of an "expired session ID".

Conditions:

The issue has been seen in some Cisco TMSXE 4.0.1 and Cisco TMS 14.4.x deployments, typically when /TMSservice (the WebEx Productivity Tools proxy) is installed.

Sample TMSXE log entries:


2014-04-30 10:28:10,780 [385] DEBUG LoggedCallSection - Finished:SaveConference
(elapsed 00:00:00.1822354)
2014-04-30 10:28:10,795 [385] DEBUG CallPerfMon - Time in TMS:00:02:25.2110000
%=0.351062488550206
2014-04-30 10:28:10,795 [385] DEBUG TMSCriticalSection -
Finished:SaveConference for -1
040000008200E00074C5B7101A82E0080000000060DC2807045FCF01000000000000000010000000FAFA4C589599E946AFEBEFDA706D86DF
(elapsed 00:00:00.2031328)
2014-04-30 10:28:10,795 [385] DEBUG BookingExceptionFactory - Error:The client
session id is expired. (-2147218253)
2014-04-30 10:28:10,795 [385] DEBUG FaultFactory -
Cisco.TMSXE.Core.TMSConnection.Booking.Errors.ClientSessionExpiredException:
The client session id is expired.

Workarounds:

Lowering Cisco TMS's IIS application pool's recycling interval to 15 minutes could help mitigate the problem.
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)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.