You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.
As you may see, ItemID is returned 4 times in single response when it was expected to be returned only once.
Preliminary investigation
Issue started to manifest itself on June 2 without any changes on application side, so update or change to Office 365 Exchange Online is a suspect.
Scope
Office 365 only. Exchange 2012-2016 doesn't have this behavior.
Office 365: Only part of the customers are affected, while other part of customers are working OK. Possibly because of staged update of Office 365 instances
Issue definitely seen on Office 365 Exchange version: 15.20.4219.9
Issue doesn't seem to reproduce itself on: 15.20.4195.17
Is there any known fix/workaround to the issue?
The text was updated successfully, but these errors were encountered:
Issue description
EWS FindItem request returns as much ItemID entries for single item(e.g. email) as much categories item has.
Date of first found occurence: 2nd June 2021,12:57:41 UTC
Affected servers: 15.20.4219.9
Sample request&response:
As you may see, ItemID is returned 4 times in single response when it was expected to be returned only once.
Preliminary investigation
Issue started to manifest itself on June 2 without any changes on application side, so update or change to Office 365 Exchange Online is a suspect.
Scope
Office 365 only. Exchange 2012-2016 doesn't have this behavior.
Office 365: Only part of the customers are affected, while other part of customers are working OK. Possibly because of staged update of Office 365 instances
Issue definitely seen on Office 365 Exchange version: 15.20.4219.9
Issue doesn't seem to reproduce itself on: 15.20.4195.17
Is there any known fix/workaround to the issue?
The text was updated successfully, but these errors were encountered: