Technical Tip: How to resolve an issue with upgrading FortiClient EMS to 7.4.7 after applying hotfix '1271902_reset_corrupt_value_746'

Description

This article describes how to resolve an issue upgrading FortiClient EMS to 7.4.7 after applying the hotfix '1271902_reset_corrupt_value_746'.

Scope

FortiClient EMS 7.4.

Solution

After applying the hotfix '1271902_reset_corrupt_value_745.zip', FortiClient EMS is still not able to be upgraded to 7.4.7.

Errors in EMS upgrade logs:

ERROR:  Wrong key or corrupt data
ERROR - Fail while running the EMS installation with upgrade. EMS database deploy will be rolled back.
dpkg: error processing package forticlientems (--configure):
installed forticlientems package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)

This occurs because there is one more corrupt value in the FortiClient EMS database and the value cannot be automatically handled.

 
Go to the FortiClient EMS GUI -> Fabric & Connectors -> Fabric Devices, where there should some OAuth Fabric Connectors.

Select the rotate icon, then get the new ClientID and Client Secret. Keep it in a safe place for now, then perform an upgrade to 7.4.7 again. It should work thereafter.

After FortiClient EMS is upgraded to 7.4.7, go to each fabric device that is using oauth2 fabric connector and update the ClientID and Client Secret there.