Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Outlook Integration throws ErrorInvalidServerVersion Fault Code

SA-50896

Summary



User is using Pega 7.3.1 with Pega Sales Automation 7.31.

User is deploying the Connect-SOAP call for "GetUserAvailability" that is used to get the free/busy schedule of an email address and another Connect-SOAP call for "createItem" that is used to create the meeting request in Outlook.

Both of these SOAP calls are failing with SOAP Fault reason set to "
The specified server version is invalid" and with SOAP Fault Code set to ErrorInvalidServerVersion. Their system is using Microsoft Outlook Exchange Version 14.3.352.4000, which translates to Exchange Version 2010_SP3.


Error Messages



ErrorInvalidServerVersion


Steps to Reproduce

  1. Go to Out-of-the-box (OOTB) Sales Automation portal in the environment.
  2. Click Appointment link to create an Appointment.
  3. Fill in the required details and see if the free/busy schedule is showing for the selected email address.


Root Cause



An issue in the custom application code or rules is identified as root cause. Per information provided on Microsoft MSDN for Outlook integration, there is no EWS schema for “Exchange2010_SP3”.

Resolution



Perform the following local-change:

Set value of below Dynamic System Settings entry to "Exchange2010_SP2".
RuleSet: PegaFW-EWSIntegration
Name: ExchangeVersion
Value: Exchange2010_SP2

Published April 13, 2018 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us