Description
This article explains how to fix an issue where endpoint compliance configurations do not show in the GUI.
Scope
FortiNAC 9.x.
Solution
A case may occur where there are multiple EPC configured but none show. Upon trying to create a new one with a name that was already used, an error is returned stating that the EPC already exists. It appears as though the EPC are configured, but they do not appear in the GUI and cannot be used in policies.
An empty list is shown here:
Configuration cannot be selected in the drop-down menu:
While adding a new policy from the GUI or refreshing the page, check for any errors shown in the CLI:
# logs
tf output.master
Search for logs like similar to this one:
yams SEVERE :: 2023-02-22 11:09:45:127 :: #749 :: org.hibernate.ObjectNotFoundException: No row with the given identifier exists: [com.bsc.api.group.Group#22]
--
In this case, a Group with DBID 22 was expected to exist, but somehow managed to be deleted without the EPC Configuration object blocking the transaction. This could be due to a missing validation in the REST API or Actions files (older GUI server files) that allowed it to be deleted while in use.
To resolve the issue, add a new group with that DBID into the database. For example, create a new Group in the GUI and assign it the name
TempGroup. Run the following command in the CLI to change its DBID to 22:# mysql bsc -e 'update bsc.Group set ID=22 where name="TempGroup";'
After this change, the GUI should correctly display all EPC entries.
