Client.BadMatch Fault Messages
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
A query did not result in the required number of matches.
Client.BadMatch.Need0
A query resulted in one or more matches when exactly zero matches were required.
Client.BadMatch.Need0.Meeting
A meeting query resulted in one or more matches when exactly zero matches were required. For example, a CreateMeetingRequest attempted to create a meeting in an organizer's personal place when that organizer's personal place already contained a meeting.
Client.BadMatch.Need1Got0
A query resulted in zero matches when exactly one match was required.
Client.BadMatch.Need1Got0.Meeting
A meeting query resulted in zero matches when exactly one match was required. For example, a ModifyMeetingRequest used a StringQuery on the mid field, but there was no meeting with the given mid.
Client.BadMatch.Need1Got0.Recording
A recording query resulted in zero matches when exactly one match was required.
Client.BadMatch.Need1Got0.Recording.InFormat
A recording query resulted in zero matches when exactly one match in a given recording format was required. For example, a GetURLRequest attempted to get a URL from which to download a recording in Windows Media format, but the recording was not available in Windows Media format.
Client.BadMatch.Need1GotMore
A query resulted in two or more matches when exactly one match was required.
Client.BadMatch.Need1GotMore.Meeting
A meeting query resulted in two or more matches when exactly one match was required. For example, a ModifyMeetingRequest used a StringQuery on the opaque1 field, but there was more than one meeting with the given opaque1 value.
Client.BadMatch.NeedNonZero
A query resulted in zero matches when one or more matches were required.