Troubleshooting Tip: FortiManager ADOM upgrade failed due to Application Category

[WinterSnowYap]

Description	This article describes how to analyze the debug CLI command to troubleshoot an ADOM upgrade that failed due to the Application Category.
Scope	FortiManager.
Solution	In this scenario, FortiManager failed to upgrade ADOM from v7.2 to v7.4. FortiManager upgrade ADOM failed: 'Fail (errno=2):missing application category'. At FortiManager, run the debug CLI command 'get' to get more information. diagnose debug disable diagnose debug reset diagnose debug service dvmdb 255 diagnose debug enable After that, perform another ADOM upgrade, and the debug result will be generated once the ADOM upgrade fails again. From the debug information, it mentions that the error is related to 'DummyAppCustom2' Application Custom Signatures due to an empty Category. At FortiManager, go to Policy & Objects -> Security Profiles -> Application Signatures -> Check for 'DummyAppCustom2' and it it possible to see the Category = 0. The built-in Application Signatures have the Category. At FortiManager, go to Policy & Objects -> Security Profiles -> Application Signatures -> Edit 'DummyAppCustom1', and it is not possible to see a way to add Category information. Therefore, at FortiManager, go to Policy & Objects -> Advanced -> CLI Configurations -> Application -> Custom -> Edit 'DummyAppCustom1' -> Add Category information. Add Category information into 'DummyAppCustom2', as 'DummyAppCustom2' also does not have Category information. After that, FortiManager can upgrade ADOM to version 7.4.