EWS FindItem request with complexity above certain started to fail
Date of first failure: 1/16/2020, 7:04:57.639 AM UTC
Failing servers: Office 365, supposedly version 15.20.2644.21, Exchange 2010-2016 do not manifest this issue
How it fails
FindItem EWS request errors with following message:
Error: ErrorInternalServerError
MessageText: An internal server error occurred. The operation failed., This query contains too many sort columns. This provider does not support more than 6 columns for a normal query, or 4 sort columns for a grouped query. Parameter name: sortColumns
Severity and Impact
Thousands of production users are affected.
Attempts to isolate
Issue started to manifest itself on Jan 16 without any changes on application side, so update or change to Office 365 Exchange Online is a suspect.
Scope
Office 365 ONLY. Exchange 2010-2016 do not have this issue.
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.2644.21
Issue seem to not reproduce itself on: 15.20.2644.20
Issue seem to be related with query complexity. As soon as we drop amount of fields in restriction to be less or equal than 5, query starts to work fine.
Nature of issue
EWS FindItem request with complexity above certain started to fail
Date of first failure: 1/16/2020, 7:04:57.639 AM UTC
Failing servers: Office 365, supposedly version 15.20.2644.21, Exchange 2010-2016 do not manifest this issue
How it fails
FindItem EWS request errors with following message:
Error: ErrorInternalServerError
MessageText: An internal server error occurred. The operation failed., This query contains too many sort columns. This provider does not support more than 6 columns for a normal query, or 4 sort columns for a grouped query. Parameter name: sortColumns
Sample failing request
Preliminary investigation
Severity and Impact Thousands of production users are affected.
Attempts to isolate Issue started to manifest itself on Jan 16 without any changes on application side, so update or change to Office 365 Exchange Online is a suspect.
Scope
Office 365 ONLY. Exchange 2010-2016 do not have this issue.
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.2644.21
Issue seem to not reproduce itself on: 15.20.2644.20
Sample Exchange servers where issue seen:
X-BEServer: BN8PR10MB4084 X-BEServer: BYAPR13MB2583
Narrowing down problem
Issue seem to be related with query complexity. As soon as we drop amount of fields in restriction to be less or equal than 5, query starts to work fine.
Is there any known fix/workaround to the issue?