Appendix a, Appendix a - troubleshoot, Slow update of meetings from tms to exchange – TANDBERG V 11.8 User Manual
Page 38: Error messages of bookings in the past from tms, Appendix a troubleshoot

38
Slow update of meetings from TMS to Exchange
If meetings are slow to be updated, make sure that there is no firewall that
blocks e-mail from the TMS server to the Exchange server. When a meeting is
booked in TMS, and e-mail is sent to the TMS-service account of the Exchange
Integration, trigging the synchronizer to start. If a firewall blocks this mail, the
meeting will only be imported by the synchronizer in to Exchange/Outlook when
the synchronizer is ran because the 5 minute interval.
If a firewall is not blocking the e-mail, check anti virus software running. In some
cases anti virus software will block e-mail sent to the TMS-service account.
To verify that the mail is received by the TMS-service account, check the mail
store of that account when a booking is being made. If no mail is received, the
synchronizer will not be triggered.
Error messages of bookings in the past from TMS
When making a booking on the Exchange server where the dateformat on the
Exchange server is different than the UTC format, you might get some strange
booking errors like “You can not book a conference in the past” when trying to
book a meeting in Outlook.
If this happens, verify that the registry key HKEY_USERS\.Default\Control
Panel\International\sShortDate is set to the dateformat DD/MM/YYYY format.
From TMS .8 and upwards TMS should give a better error message in such
a case.
Appendix A
Troubleshoot