Cisco Bug: CSCum95482 - TMSXE should skip meetings without required properties
Jun 27, 2017
- Cisco TelePresence Management Suite (TMS)
Known Affected Releases
Symptom: If a meeting is found on an exchange room calendar without a Subject, Start Time and or End Time, it will cause TMSXE to break and not process any other meetings for any room Calendar. These Meetings should be skipped and TMSXE process all valid meetings; similar to the behavior on CTS-MAN. Often times, these are meetings that the customer is unaware of and therefore would be classified as 'don't cares'. An enhancement defect was filed with instructions for correcting these meeting in outlook to allow sync and asked for debug level logging of these occurrences. Defect ID: CSCum84052 This defect is more for us to ignore these meetings that do not meet the criteria and possible send an email to admin to correct the problem meetings later; however, TMSXE should be robust enough to skip such meetings. 2014-01-28 15:19:02,104  ERROR SyncFolderItemsWorker104 - SyncFolderItemssrEx: ErrorInvalidPropertyRequest Property is not valid for this object type. Microsoft.Exchange.WebServices.Data.ServiceResponseException: Property is not valid for this object type. at Microsoft.Exchange.WebServices.Data.ServiceResponse.InternalThrowIfNecessary() at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute() at Microsoft.Exchange.WebServices.Data.ExchangeService.SyncFolderItems(FolderId syncFolderId, PropertySet propertySet, IEnumerable`1 ignoredItemIds, Int32 maxChangesReturned, SyncFolderItemsScope syncScope, String syncState) at Cisco.TMSXE.EWS.ExchangeConnectionResource.GetSyncFolderItems(PropertySet propSet, Int32 maxRes, String syncState) at Cisco.TMSXE.EWS.Subscription.SyncFolderItemsWorker.RetrieveBlockOfFolderItems() Conditions: Meeting booked in outlook without key component break TMSXE * Subject * Start Date * End Date A meeting missing any combination of these criteria will completely break TMSXE sync for that room calendar.
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