Known issues
Known issues are organized into the following categories:
To inquire about a particular bug or to report a bug, please contact Fortinet Customer Service & Support.
New known issues
No new issues have been identified in version 7.6.1.
Existing known issues
The following issues have been identified in a previous version of FortiAnalyzer and remain in FortiAnalyzer 7.6.1.
Device Manager
| Bug ID | Description |
|---|---|
|
1106056 |
Deleting a model device may result in the removal of the Logs folder under Storage. This issue occurs only if the model device never comes online and does not match a FortiGate. |
Fabric View
| Bug ID | Description |
|---|---|
| 1078817 |
The "FortiClient EMS Cloud" Fabric Connector (existing/newly added) may not function properly, causing FortiAnalyzer to potentially fail in establishing a successful connection with the "FortiClient EMS Cloud" due to this issue. |
FortiView
| Bug ID | Description |
|---|---|
|
922053 |
Mismatched Username Detected for the Same IP Address in IOC Compromised Hosts. |
| 954542 | When the time range is extensive, FortiAnalyzer may experience limitations in handling data points, resulting in potential omissions of data entries in the final results for FortiView > SD-WAN Monitors widgets. |
Log View
| Bug ID | Description |
|---|---|
|
1058278 |
The Preview under the Chart Builder displays "No record found". Dataset is saved but chart is not saved. Workaround: Charts needed to be manually created by using the saved dataset. |
|
1061367 |
The Webfilter logs are not visible on the FortiGate's GUI if the source set to FortiAnalyzer. |
Others
| Bug ID | Description |
|---|---|
| 1053830 |
MEAs cannot be enabled from FortiAnalyzer's GUI. Workaround:
Use the followingCLI command to
enable them (in this example, config system docker set status enable set universalconnector enable end |
| 1060337 |
The log insertion might be interrupted if FortiAnalyzer is upgraded directly from version (7.4.0/7.4.1) to 7.6.0/7.6.1. Workaround: To avoid this issue, upgrade the FortiAnalyzer to 7.4.2/7.4.3 first and then go to the 7.6.0/7.6.1. For more details please visit the FortiAnalyzer Upgrade Guide. |
| 1062128 |
After upgrading to the latest available build, the FortiAnalyzer GUI displays the warning message: "A new firmware version is available". |
| 1064103 |
The "siemdb" daemon may fail to start on a FortiAnalyzer VM running version 7.6.0, which can prevent log migration from completing. This issue may occur due to inconsistencies in the number of CPUs reported by the system during initialization. Certain CPU-related settings might trigger this problem. For more details, see Special Notices. |
Reports
| Bug ID | Description |
|---|---|
| 895106 | Top destination by bandwidth dataset does not exclude long-live session. |
System Settings
| Bug ID | Description |
|---|---|
|
766197 |
An admin user limited to a device group can view all device's log |
|
1027547 |
In certain cases (currently under investigation), the License Status on FortiAnalyzer may be incorrectly displayed as "Expired" despite the license being active in the account. Workaround: Restart the FortiAnalyzer when feasible. |
|
1058282 |
Remote administrators may be unable to review the Event Logs, as the GUI might display the following message: "Web Server Error 500." |
|
1063040 |
Unable to import a local certificate into FortiAnalyzer. This issue may occur if the certificate is encrypted with a newer OpenSSL version that FortiAnalyzer does not yet support. Workaround: Convert the latest certificate to the legacy format before uploading it to FortiAnalyzer. |