Answered by:
Equipment Room: This instance was declined because there are conflicts.

Question
-
We are using equipment room resources in Exchange 2010 for shared team calendars in order to utilize the Booking Attendant AutoAccept feature. When doing recurring meetings we are constantly getting back the following message.
This instance was declined because there are conflicts.
We have these settings in place, see below, we used the get-calendarprocessing cmdlet.
RunspaceId : 4daa7abc-ae57-432b-8543-b56ad5337d85
AutomateProcessing : AutoAccept
AllowConflicts : True
BookingWindowInDays : 365
MaximumDurationInMinutes : 0
AllowRecurringMeetings : True
EnforceSchedulingHorizon : True
ScheduleOnlyDuringWorkHours : False
ConflictPercentageAllowed : 100
MaximumConflictInstances : 999999999
ForwardRequestsToDelegates : True
DeleteAttachments : True
DeleteComments : True
RemovePrivateProperty : True
DeleteSubject : False
AddOrganizerToSubject : True
DeleteNonCalendarItems : False
TentativePendingApproval : True
EnableResponseDetails : True
OrganizerInfo : True
ResourceDelegates : {}
RequestOutOfPolicy : {}
AllRequestOutOfPolicy : False
BookInPolicy : {}
AllBookInPolicy : True
RequestInPolicy : {}
AllRequestInPolicy : False
AddAdditionalResponse : False
AdditionalResponse :
RemoveOldMeetingMessages : True
AddNewRequestsTentatively : True
ProcessExternalMeetingMessages : False
RemoveForwardedMeetingNotifications : False
MailboxOwnerId : domain.com/CorpUsers/Test Exchange Accounts/TestEquipRoom
Identity : domain.com/CorpUsers/Test Exchange Accounts/TestEquipRoom
IsValid : True
All the clients are Outlook 2003 SP3Server is Exchange 2010 SP1 w/ RU2
Any ideas?
dTuesday, March 15, 2011 4:43 PM
Answers
-
Hi dfunk12,
Please set the AllowConflicts as false, and then make a test.
Regards!
Gavin
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.- Marked as answer by Gavin-Zhang Monday, March 28, 2011 6:26 AM
Friday, March 18, 2011 9:08 AM
All replies
-
Am I reading this correctly that your meetings are not allowed to be longer than 0 minutes? If so that could be a problem.
MaximumDurationInMinutes : 0
Stephen
Tuesday, March 15, 2011 6:00 PM -
Thanks for responding. I actually tried up'ing that to 999999999, but still no luck.
dTuesday, March 15, 2011 6:39 PM -
Hi dfunk12,
Please set the AllowConflicts as false, and then make a test.
Regards!
Gavin
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.- Marked as answer by Gavin-Zhang Monday, March 28, 2011 6:26 AM
Friday, March 18, 2011 9:08 AM -
Old thread with no answer...
I am having this issue that seems to have started with 2010 SP2.To Gavin, what is the purpose of your test? Are you saying that AllowConflicts = false really means true? Or that turning it off, then on again will fix an underlying bug?
For reference, MaximumDurationInMinutes = 0 means unlimited duration. So that's NOT it.
Any answer out there?
edit: I set AllowConflicts to false, tested it and it acted as expected. I reset it to true and it acts exactly the same. The test was a meeting for the 1st of every month. The conflict was a user who takes Monday's off. So every Monday that's the first was declined.
This instance was declined because there are conflicts.
The conflicts are:
Organizer and Time of Conflicting Meeting
Other User <mailto:ouser@contoso.com> - Monday, October 01, 2012 12:00:00 AM to Tuesday, October 02, 2012 12:00:00 AM
Other User <mailto:ouser@contoso.com> - Monday, April 01, 2013 12:00:00 AM to Tuesday, April 02, 2013 12:00:00 AM
Other User <mailto:ouser@contoso.com> - Monday, July 01, 2013 12:00:00 AM to Tuesday, July 02, 2013 12:00:00 AM
All times listed are in the following time zone: Customized Time Zone
- Edited by amcmis Wednesday, February 29, 2012 3:37 PM
Wednesday, February 29, 2012 3:26 PM