User schedules meeting in outlook, doesn't receive denial until - Microsoft Community
- Get link
- X
- Other Apps
here facts. user 1 booked meeting in outlook, received confirmation. next day, user 1 received denial letter stating "is defective because of endpoint availability conflict". investigating in tms (telepresence management suite) found user 2 booked room month prior, same date user 1. user 1's meeting started before user 2, lasted 24 hours. believe have been caused user 1's outlook not being synced database. if else have caused open answers. work company supports telepresence devices , infrastructure various companies. of has scheduling, manage tms , tmsxe , not monitor, manage, or trained on exchange or outlook. below series of events tms event log provides time stamps of meeting creation.
user 2
tms > view conference 152230:
5/2/2017 1:44:47 pm tms-service service conference: created
5/2/2017 1:44:47 pm tms-service service instance: created, start time 06/23/2017 13:00:00 -04:00
5/2/2017 1:53:03 pm tms-service service conference: recreated
5/2/2017 1:53:03 pm tms-service service conference: recurrence changed none none
5/2/2017 1:53:03 pm tms-service service instance: updated
5/2/2017 1:53:03 pm tms-service service instance: start time changed 06/23/2017 13:00:00 -04:00 06/19/2017 13:00:00 -04:00
5/2/2017 1:53:03 pm tms-service service instance: end time changed 06/23/2017 15:00:00 -04:00 06/19/2017 15:00:00 -04:00
5/31/2017 7:40:05 am tms-service service conference: deleted
5/31/2017 7:40:05 am tms-service service instance: deleted
6/1/2017 8:11:04 am tms-service service conference: updated
6/1/2017 8:11:05 am tms-service service instance: created, start time 06/19/2017 13:00:00 -04:00
user 1
tms > view conference 155167:5/30/2017 10:29:57 am tms-service service conference: created
5/30/2017 10:29:57 am tms-service service instance: created, start time 06/19/2017 05:00:00 -04:00
5/31/2017 7:51:14 am tms-service service conference: recreated
5/31/2017 7:51:14 am tms-service service conference: defective because of endpoint availability conflict
5/31/2017 7:51:15 am tms-service service instance: updated
5/31/2017 7:51:15 am tms-service service instance: start time changed 06/19/2017 05:00:00 -04:00 06/19/2017 00:00:00 -04:00
5/31/2017 7:51:15 am tms-service service instance: end time changed 06/19/2017 13:00:00 -04:00 06/20/2017 00:00:00 -04:00
5/31/2017 4:25:40 pm tms-service service conference: updated
5/31/2017 4:25:40 pm tms-service service instance: updated
5/31/2017 4:25:40 pm tms-service service conference: no longer defective
**post moved moderator appropriate forum category.**
Office / Outlook / Other/unknown / Unknown/other
- Get link
- X
- Other Apps
Comments
Post a Comment