Known Issues
The following issues have been identified in FortiAnalyzer version 6.0.6. For inquires about a particular bug or to report a bug, please contact Fortinet Customer Service & Support.
|
Bug ID |
Description |
|---|---|
| 542774 | Upgrading from 5.2 to 5.6 may break Log aggregation if password contains the special character ($). |
| 542933 | FortiView may not search logs for the time entered in custom time. |
| 543259 | Error checking should prevent administrator from being able to incorrectly configure log forwarding with same IP address of FortiAnalyzer. |
| 545197 | Device Manager's log rate may be displayed incorrectly for a FortiGate HA cluster. |
| 548872 | FortiAnalyzer Report Cover Page footer display set to transparent may not work the same way as previous releases. |
| 550116 | FortiAnalyzer may intermittently not sending reports to Email as per the configured schedule. |
| 552067 | FortiAnalyzer may show the error, "authorization failed for restapi request OFTP_RESTAPI_GENERIC_REQ", in the event log. |
| 552613 | There may not be abnormal behavior using the space character in Advanced Search field. |
| 553495 | FortiAnalyzer may show Web Server 404 Error when trying to download a report. |
| 554201 | FortiAnalyzer may not be able to import reports when re-creating an ADOM with the same name. |
| 554345 | System may generate the error message, "Did not receive any log from device <device-name> in xxxx minute for device changed standalone to ha". |
| 554480 | GDPR user can open the log browse and the Source columns are not masked within the log file. |
| 554890 | Syslog forward as syslog reliable miss end delimiter (0x0a) between logs. |
| 555907 | FortiAnalyzer may not successfully run all scheduled reports. |
| 556106 | FortiGate ADOM should not access the blocked web sites statistic from non-FortiGate devices. |