Known issues and Limitations

Modified on Thu, 22 Aug at 11:24 PM

Issue with getting Series for Exchange 2013

Series are not being synchronized from Exchange 2013.

Issue appears from RTS 6.6.15.68 onwards

Status: Solution should be available on request to Support from around the 21th of December

Issue with migration of recurring reservation data

When upgrading Resource Central to 4.2 Service Release 1, a data migration of existing recurring meetings fails. Result is decoupled orders on theses reservations.

A fix and a script to reattach the decoupled orders are being made.

Status: Fixed

Permissions - Deleted Groups changes are not return (On-Premise)

Using RC permissions with groups on On-premise environments, Push notifications from Active Directory does not send notifications when deleting a group.

This will result in wrong permission settings on Resources in Resource Finder

Workaround: Set up periodical Full Sync in RealTime Service to synchronize the groups correctly

Status: Analyzing for alternative solution

RTS unable to send E-mails to On-Premise Exchange 2010, 2013 and 2016

With latest version of RealTime Service 6.6.12.22 there is a bug on sending e-mails to On-Premise Exchange 2010, 2013 and 2016.

The warning message shown like below:

2019-07-11 10:58:12,561 WARN [65] RTS.ServiceProcess : Exchange 192.168.2.68 - Notifications: Exception occured while updating permissions for Notification DwByYzE1NC5wc21heC5jb20QAAAA89/gshlvbUKBe8Hx30nddnhHn7qzBdcIEAAAABYOPrYYKoVKgFEHScZLdpQ=, watermark AQAAANB6q+mNqK9EvfgAus6hv33H+TEAAAAAAAE=, items count - 4 / Subscribtion DwByYzE1NC5wc21heC5jb20QAAAA89/gshlvbUKBe8Hx30nddnhHn7qzBdcIEAAAABYOPrYYKoVKgFEHScZLdpQ=, watermark AQAAANB6q+mNqK9EvfgAus6hv33H+TEAAAAAAAE=, SynchronizationItem user ex2016_ps_rts_03 - [email protected], calendar Calendar
System.Web.Services.Protocols.SoapException: The impersonation principal name is invalid.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at RTSExchangeNotificationService.ExchangeWebReference.ExchangeServiceBinding.GetFolder(GetFolderType GetFolder1)
at RTSExchangeNotificationService.EchangeCommunication.ExchangeConnection.GetFolder(String folderid, Boolean onlymainfields)
at RTSExchangeNotificationService.EchangeCommunication.ExchangeConnection.UpdateCalendarPermissions(SynchronizationCalendar calendar)
at RTSExchangeNotificationService.ExchangeNotificationProcessThread.<>c__DisplayClass5_2.b__2(Int32 attempt)
at RTSExchangeNotificationService.ExchangeThread.Repeat(Int32 attempts, Int32 interval, WaitHandle stopEvent, Func`1 shouldInterrupt, Action`1 what, Action`2 onerror)
at RTSExchangeNotificationService.ExchangeThread.Repeat(Action`1 what, Action`2 onerror)
at RTSExchangeNotificationService.ExchangeNotificationProcessThread.Execute(Object param)

If you change both principal name and subdomain, error shown:

2019-07-11 10:56:07,626 ERROR [74] RTS.ServiceProcess : Exchange 192.168.2.68 - Notifications: Error subscribing for notifications ex2016_ps_rts_03 - [email protected]
System.Web.Services.Protocols.SoapException: The impersonation principal name is invalid.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at RTSExchangeNotificationService.ExchangeWebReference.ExchangeServiceBinding.GetFolder(GetFolderType GetFolder1)
at RTSExchangeNotificationService.EchangeCommunication.ExchangeConnection.GetFolders(DistinguishedFolderIdNameType folderType, Boolean onlymainfields)
at RTSExchangeNotificationService.EchangeCommunication.ExchangeConnection.GetDefaultCalendar(SynchronizationUser user, Boolean onlymainfields, Boolean impersonate)
at RTSExchangeNotificationService.ExchangeSubcriptionThread.Execute(Object param)

Workaround: Downgrade to 6.6.12.1

Status: Solved in 6.6.12.157

Insert of "Declined" status on RC reservations

A code bug in 6.6.12 is unfortunately in some scenarios updating Resource Central reservations with a "Decline" status instead of "Free".

Result is that order data is not clean up correctly for deleted reservations.

To see if your Resource Central Database is effected please use the following statement:

SELECT Count(r.id) [Declined Reservations], Count(o.id) [Declined Orders]
FROM reservations r
FULL JOIN orders o on r.id=o.reservationsid
WHERE r.busystatus='DECLINED'

If any wrong data, please contact Add-On Products for assistance on the clean up

Workaround: Install 6.6.12.1 and clean up data

Status: Fixed with 6.6.12.1