Your calendar couldn't be checked to see whether this event conflicts with other events.

%3CLINGO-SUB%20id%3D%22lingo-sub-49578%22%20slang%3D%22en-US%22%3EYour%20calendar%20couldn't%20be%20checked%20to%20see%20whether%20this%20event%20conflicts%20with%20other%20events.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49578%22%20slang%3D%22en-US%22%3E%3CP%3EWe've%20been%20using%20Office%20365%20for%20about%20two%20years%2C%20and%20we've%20had%20a%20few%20rooms%20setup%26nbsp%3B%20as%20resources%20this%20entire%20time.%26nbsp%3B%20The%20Administrative%20Assistant%20schedules%20the%20rooms%20and%20it's%20worked%20well%20for%20us.%26nbsp%3B%20Lately%20she%20started%20getting%20the%20notice%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22%3CSPAN%20class%3D%22_fc_4%20o365buttonLabel%22%3EYour%20calendar%20couldn't%20be%20checked%20to%20see%20whether%20this%20event%20conflicts%20with%20other%20events.%22%3C%2FSPAN%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ein%20emails%20requesting%20the%20rooms.%26nbsp%3B%20It's%20not%20every%20time%2C%20just%20often%20enough%20to%20be%20frustrating.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20idea%20why%20this%20started%3F%26nbsp%3B%20All%20the%20staff%20making%20the%20requests%26nbsp%3Band%20the%20rooms%20are%20in%20the%20same%20domain%26nbsp%3Band%20under%20the%20same%20license.%26nbsp%3B%20Nothing%20is%20on%20premise.%26nbsp%3B%20Everything%20I%20could%20find%20through%20searching%20dealt%20with%20on%20premise%20exchange%20servers%20or%20google%20app%20requests.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-49578%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-286690%22%20slang%3D%22en-US%22%3ERe%3A%20Your%20calendar%20couldn't%20be%20checked%20to%20see%20whether%20this%20event%20conflicts%20with%20other%20events.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-286690%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%2C%20this%20has%20resolved%20for%20me%20too...%20was%20broken%20when%20we%20added%20our%20emails%20to%20route%20OUTBOUND%20via%20Mimecast%20so%20any%20mail%20smart%20host%20would%20also%20probably%20break%20this%20too.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-168673%22%20slang%3D%22en-US%22%3ERe%3A%20Your%20calendar%20couldn't%20be%20checked%20to%20see%20whether%20this%20event%20conflicts%20with%20other%20events.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-168673%22%20slang%3D%22en-US%22%3E%3CP%3EMr%20Mooney%2C%20thank%20you%20for%20taking%20the%20time%20to%20come%20back%20with%20this%20response.%20resolved%20our%20issues%20even%20though%20the%20room%20mailbox%20was%20set%20to%20process%20emails%20automatically.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69956%22%20slang%3D%22en-US%22%3ERe%3A%20Your%20calendar%20couldn't%20be%20checked%20to%20see%20whether%20this%20event%20conflicts%20with%20other%20events.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69956%22%20slang%3D%22en-US%22%3E%3CP%3EBit%20late%20but%20for%20others%20who%20find%20this%20page%2C%20I%20resolved%20this%20with%20the%20following%20powershell%20command%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESet-CalendarProcessing%20%3CEM%3EMeetingRoomName%3C%2FEM%3E%20-ProcessExternalMeetingMessages%20%24True%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1509767%22%20slang%3D%22en-US%22%3ERe%3A%20Your%20calendar%20couldn't%20be%20checked%20to%20see%20whether%20this%20event%20conflicts%20with%20other%20events.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1509767%22%20slang%3D%22en-US%22%3Eawesome%2C%20exactly%20what%20I%20needed!%20Thank%20you!!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1834941%22%20slang%3D%22en-US%22%3ERe%3A%20Your%20calendar%20couldn't%20be%20checked%20to%20see%20whether%20this%20event%20conflicts%20with%20other%20events.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1834941%22%20slang%3D%22en-US%22%3E%3CP%3EI%20get%20this%20error%20from%20any%20invitation%20from%20outside%20the%20company%2C%20whether%20it%20contains%20a%20room%20or%20not.%26nbsp%3B%20Very%20frustrating.%26nbsp%3B%20Why%20would%20it%20not%20be%20able%20to%20check%20my%20own%20calendar%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

We've been using Office 365 for about two years, and we've had a few rooms setup  as resources this entire time.  The Administrative Assistant schedules the rooms and it's worked well for us.  Lately she started getting the notice

 

"Your calendar couldn't be checked to see whether this event conflicts with other events." 

 

in emails requesting the rooms.  It's not every time, just often enough to be frustrating.

 

Any idea why this started?  All the staff making the requests and the rooms are in the same domain and under the same license.  Nothing is on premise.  Everything I could find through searching dealt with on premise exchange servers or google app requests. 

 

Thanks!

5 Replies
Highlighted

Bit late but for others who find this page, I resolved this with the following powershell command:

 

Set-CalendarProcessing MeetingRoomName -ProcessExternalMeetingMessages $True

Highlighted

Mr Mooney, thank you for taking the time to come back with this response. resolved our issues even though the room mailbox was set to process emails automatically.

Highlighted

Thanks, this has resolved for me too... was broken when we added our emails to route OUTBOUND via Mimecast so any mail smart host would also probably break this too.

Highlighted
awesome, exactly what I needed! Thank you!!
Highlighted

I get this error from any invitation from outside the company, whether it contains a room or not.  Very frustrating.  Why would it not be able to check my own calendar?