Fortimanager Error when edit variable mapping "Failed to add per-device mapping to FMG variable"

[Nour_Alkonsol]

Hello 
we have Fortimanager giving the Error message appearing every time trying to edit variable mapping.
"Failed to add per-device mapping to FMG variable"

we tried :
diagnose dvm check-integrity
diag cdb upgrade check objcfg-integrity
diagnose cdb check policy-packages
diagnose pm2 check-integrity all
diag cdb upgrade check reference-integrity
diagnose cdb upgrade check +all
But the above commands, unfortunately, didn't work

Any Advice?
Thanks

[Jean-Philippe_P]

Hello Nour_Alkonsol, 

Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible. 

Thanks, 

[Jean-Philippe_P]

Hello,

We are still looking for an answer to your question.

We will come back to you ASAP.

Thanks,

[Jean-Philippe_P]

Hello Nour_Alkonsol,

I found a solution. Can you tell us if it helps, please?

To address the error message "failed to add per-device mapping to fmg variable," you can try the following steps:

1. Check ADOM Integrity: Use the command `diagnose cdb check adom-integrity [adom]` to check and repair the specified ADOM's database. Replace `[adom]` with the appropriate ADOM name.
   
   
2. Check ADOM Revision: Run `diagnose cdb check adom-revision [adom] [preview]` to check or remove invalid ADOM revision database entries. Use the `preview` option to see the changes before applying them.
   
   
3. Check Policy Packages: - Execute `diagnose cdb check policy-packages [adom]` to ensure the policy packages are correct.
   
   
4. Upgrade and Repair: Perform a comprehensive upgrade check using `diagnose cdb upgrade check <action>`. Consider actions like `objcfg-integrity`, `reference-integrity`, and `duplicate-uuid`.
   
   
5. Force Retry Upgrade: If an upgrade was previously attempted, use `diagnose cdb upgrade force-retry <action>` to re-run the upgrade.
   
   
6. Review Logs: - Check the logs using `diagnose cdb upgrade log` for any specific error messages that might provide more insight.

If the issue persists after these steps, consider reaching out to Fortinet Support for further assistance.