Skip to main content
rcruz23
Staff
Staff
November 23, 2024

Troubleshooting Tip: Failed to synchronize FortiAnalyzer with current ADOM data

  • November 23, 2024
  • 0 replies
  • 2150 views

 

Description This article describes troubleshooting steps when facing synchronization issues.
Scope FortiManager and FortiAnalyzer.
Solution

When facing the following error:

 

Failed to synchronize FortiAnalyzer with current ADOM data. Fail(errno=-1):runtime error 0: invalid value

 

Make sure to check the following requirements:

  1. FortiManager and FortiAnalyzer are both running the same versions.
  2. ADOM name, type (Preferred 'Fabric'), and device names on both devices should be the same.
  3. FortiManager needs to be in Normal ADOM mode.

  4. FortiAnalyzer features globally need to be disabled on FortiManager.
  5. The same FortiGate devices must be added to the same ADOM (names and types) in both FortiManager and FortiAnalyzer.
  6. FortiManager access needs to be enabled on the FortiAnalyzer interface (see screenshot below). 

 

Mohamed_Akram_0-1775652301896.png

 

If there is any discrepancy, make sure that FortiAnalyzer does not have any devices that are not included in FortiManager. FortiManager will update any new device that FortiAnalyzer does not have.

If FortiAnalyzer has a device that is not in FortiManager remove the device from FortiAnalyzer as this will trigger the error. After removing all the devices on FortiAnalyzer that are not included on FortiManager try to add FortiAnalyzer on FortiManager, and the error should be fixed.

 

Helpful troubleshooting commands:

 

FortiManager command line:


diagnose debug disable
diagnose debug reset
diagnose debug application depmanager 255
diagnose debug application dmworker 255
diagnose debug application securityconsole 255
diagnose deb service dvmcmd 255
diagnose debug application dmapi 255
diagnose debug enable

 

Add the FortiAnalyzer to the FortiManager and reproduce the issue to collect the logs. Disable the debug after collecting the logs using the below syntax.


diagnose debug disable
diagnose debug reset