Skip to main content
dbu
Staff
Staff
Oct 12, 2026 8:45 AM UTC

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:

2026-10-09 12:46:12.262 +0100 [pool-61-thread-1] INFO GlobalObjectGRPCClient - GlobalObjectGRPCClient sync Failed- by[] serverIP =x.x.x.x Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1; statement executed: delete from bsc.AccessPolicy where ID=? and VERSION=?
2026-10-09 12:46:12.271 +0100 [pool-61-thread-1] INFO yams.NetworkControlManager - Manual SYNC failed

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:

DELETE FROM `AccessPolicy`
WHERE `ID` = <ID>
  AND `VERSION` = <expected_version>;


If the affected managed server contains a different VERSION, the statement matches zero rows, and synchronization fails with:

 actual row count: 0; expected: 1;


  1. Check the Policy on the manager and CA server:

SELECT
    `ID`,
    `VERSION`,
    `NAME`,
    `guid`,
    `globalModifiedDate`,
    `PROFILE_ID`,
    `CONFIGURATION_ID`,
    `LAST_MODIFIED_BY`,
    `LAST_MODIFIED_DATE`,
    `LAST_CHANGE_SUMMARY`
FROM `AccessPolicy`
WHERE `NAME` = 'Students'
   OR `guid` = 1484348937400340\G


In the validated case, after comparing the outputs, the same globally synchronized policy showed the following values.


Manager:

NAME    = Students
VERSION = 5
guid    = 1484348937400340


Successfully synchronizing CA:

NAME    = Students
VERSION = 5
guid    = 1484348937400340


Failing CA:

NAME    = Students
VERSION = 7
guid    = 1484348937400340


The GUID was already correct. The mismatch was limited to the CA-side VERSION.

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.


  1. Verify if the policy contains evidence of an intentional local modification:

SELECT *
FROM `AccessPolicyAudit`
WHERE `LIVE_ID` = <LOCAL_ACCESS_POLICY_ID>
   OR `RECORD_NAME` = 'GI-students'
ORDER BY `TIMESTAMP` DESC
LIMIT 20;


In the validated case, the audit query returned "Empty set" and the affected row showed:

LAST_MODIFIED_BY    = SYSTEM
LAST_CHANGE_SUMMARY = []


The higher VERSION number on the CA represents synchronization state (SYSTEM) rather than a modification from Administrator.


  1. Update the policy:

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.

UPDATE `AccessPolicy`
SET `VERSION` = 5
WHERE `ID` = 1509798846496798
  AND `NAME` = 'Students'
  AND `guid` = 1484348937400340
  AND `VERSION` = 7;


Note:

Direct database modifications should only be performed after taking a current database backup and preferably during a maintenance window under Fortinet Support guidance.


  1. Verify the policy has the correct VERSION:

SELECT
    `ID`,
    `VERSION`,
    `NAME`,
    `guid`,
    `globalModifiedDate`,
    `PROFILE_ID`,
    `CONFIGURATION_ID`,
    `LAST_MODIFIED_BY`,
    `LAST_MODIFIED_DATE`
FROM `AccessPolicy`
WHERE `ID` = 1509798846496798\G


Expected:

VERSION = 5


  1. Run the synchronization again from the FortiNAC Manager and verify the status.

    Risk and Resilience in the Age of AI. An OT Thought Leadership Summit for Houston's Critical Infrastructure Leaders. Date: Thursday, December 3, 2026. Time: 8:30 am - 1:30 pm (CT). Location: The Westin Houston, Memorial City | 945 Gessner Road, Houston, TX 77024