I am Getting ‘Failed to Reserve Meeting’ Error

So, you have come up to the EventBoard display and clicked the Reserve button wanting to have a quick meeting. When you do, you get an error that says, 'Failed to Reserve Meeting: Your meeting could not be reserved at this time.'

The EventBoard will give this error if the calendar you selected is read-only or there is no calendar selected. This is most commonly a permissions error, but there are other scenarios that may cause this error.

To resolve this: check that you have a calendar connected to the room that you are trying to book.

From Teem Web,

1. Click on Manage > Locations from the main menu.

2. Click on Locations, and then find the building, floor, and room that isn't allowing you to be booked.

3. Click on the room name, and then click on Overview on the menu.

There you will see a Calendar section. Ensure that the box next to Room Calendar does not display the following message: Please Select a Calendar.

If you have selected a calendar but still get this error, you must check your calendar system and ensure you have the right permissions. The procedure for this depends on your calendar system; please refer to the Integration document for your calendar system for more information.

Lastly, having the EventBoard read an ICS calendar you have subscribed to is possible. The ICS format only allows read-only, so the 'Allow Reservations' feature will not work. In this case, it is best to turn off the feature in your Teem dashboard or select a different calendar.

‘End Events Early’ Doesn’t Do Anything

You have just finished a meeting early and want to click the 'End Event' button so that others can reserve the room. But nothing happens when you tap the End Event button on the iPad and then confirm the meeting will end early.

This can occur in a couple of situations:

The Exchange 2007 API is being used: The Exchange 2007 is different, and End Events Early functionality is simply not the same as other exchange versions.

The following two conditions are met:

If the calendar is an exchange calendar

The room resource was invited to the event and was scheduled using your desktop computer. It was not created using the quick reserve feature.

In Exchange, because the event organizer created the event, no one else but the event organizer can cancel or modify the event. If your organization desires this feature to work, you may consider changing from a Delegate setup to an Impersonation setup. These two setup methods are outlined in the Basics of Exchange article.

If the circumstance falls outside those two issues, then it could be a permissions issue that must be investigated.

My Private Meetings Are Being Displayed

You have made a private meeting, but the event details appear on the EventBoard. This is understandably frustrating because you don't want Bob to know what is happening. After all, a surprise birthday party must be kept secret until Bob arrives.

By default, Exchange servers are set to have the room resource remove the privacy flag. Super annoying, but it can be changed.

In Exchange 2013 and Office 365, the setting can be changed using Power Shell to change the RemovePrivateProperty value to False.

Once you have your Power Shell environment set up. Run this command in your Exchange Management Shell:

'Set-CalendarProcessing "[room name or smtp]" -RemovePrivateProperty $false'

And that is it! You can have that surprise party, and Bob won't be able to look at the EventBoard and know what is happening. His birthday will be glorious this year!

Where to Find Crash Logs

On rare occasions, the EventBoard and LobbyConnect apps may crash; when this happens, a crash report is created. This report can be very helpful for us as it will tell our developers what went wrong and will allow them to know if something in the app needs to be fixed or if the crash was due to some other issue with the device.

Follow the steps below to locate the crash reports on the device in the event that one of the apps crashes.

1. On your device, click on the Settings app, then select Privacy. 
2. Scroll to the bottom of the privacy page.
3. You'll be looking for either "Diagnostics" or "Analytics & Improvements," depending on your iOS version (instructions for each version are available here).
4. Then you will tap “Analytics Data.”
5. Once in here, you will see all the crash logs for any recently crashed app.
6. Find the name of the app that has crashed and tap on it. You may also see a LatestCrash.ips file.
7. Now highlight all the text, copy and paste it into an email, and send it to us at support@teem.com.

Scroll to the bottom of the privacy page. You'll be looking for either "Diagnostics" or "Analytics & Improvements," depending on your iOS version (instructions for each version are available here). Then you will tap “Analytics Data.” Once in here, you will see all the crash logs for any recently crashed app. You will want to look for the name of the crashed app and tap on it. You may also see a LatestCrash.ips file. From here, you will want to highlight all the text, copy and paste it into an email, and send that text to us at support@teem.com.