Technical Tip: How to fix Exchange connector related issue in FortiSOAR

Issue 1: 

After upgrading to a higher version, the Health Check and connector actions for the Exchange connector may occasionally fail with the below errors.

Reason of failure:

During the connector upgrade the listener could not start and continue to fail.

Steps to fix the issue:

As a workaround, try deactivating and reactivating the connector to restart the listener.

Issue 2: 

Once the connector health check is up and running, the action may fail with the below error

Error message : Tried versions ('Exchange2016', 'Exchange2015_SP1', 'Exchange2015', 'Exchange2013_SP1', 'Exchange2013', 'Exchange2010_SP2', 'Exchange2010_SP1', 'Exchange2010', 'Exchange2007_SP1', 'Exchange2007') but all were invalid Connector :: exchangeV4.6.0

Reason of failure:

During the upgrade, exchangelib is also updated, but due to the system cache, the connector continues to use the previous version of exchangelib.

Steps to fix the issue:

1. Remove the pycache from the connector folder:

A. cd /opt/cyops/configs/integrations/connectors/exchange_4_5_1/

B. rm -rvf __pycache__

2. Restart uwsgi service using the command 'systemctl restart uwsgi'.