Troubleshooting Tip: FortiNAC Manager synchronization fails with 'Batch update returned unexpected row count' for AccessPolicy
Description | This article describes how to troubleshoot a FortiNAC Manager synchronization failure caused by a version mismatch in a globally synchronized AccessPolicy.The Manager may report an error similar to: |
Scope | Â FortiNAC Manager, FortiNAC-F. |
Solution | The AccessPolicy table contains a VERSION field used by FortiNAC when updating or deleting policy records. During synchronization, FortiNAC may issue an operation equivalent to: If the affected managed server contains a different VERSION, the statement matches zero rows, and synchronization fails with:
In the validated case, after comparing the outputs, the same globally synchronized policy showed the following values.
Failing CA:
Note: Do not assume that the Manager VERSION should always be copied to the CA. First, confirm the same expected version against a successfully synchronizing CA.
The higher VERSION number on the CA represents synchronization state (SYSTEM) rather than a modification from Administrator.
If the Manager and a known-good CA confirm the expected version and the failing CA contains a stale version, update only the VERSION field. Note: Direct database modifications should only be performed after taking a current database backup and preferably during a maintenance window under Fortinet Support guidance.
Expected:
|
