# diagnose de application sqlreportd 255# diagnose de en
While the debug is running, execute the report via GUI or CLI as described in step 3. After the debug output is generated, close the debugging in CLI via commands:
# diagnose de dis# diagnose de res
3) Execute the report manually via CLI, in this example we will use “User Detailed Browsing Log” from the root ADOM.
# exe sql-report run root ?<schedule-name> <----- Select one of the available SQL report schedule names.
ADOM: rootNAME TITLE10012 - User Detailed Browsing Log10017 - User Top 500 Websites by Bandwidth10018 - User Top 500 Websites by Session10019 - Application Risk and Control10025 - Cyber Threat Assessment10037 - Secure SD-WAN Report10039 - SOC Incident Report10041 - Throughput Utilization Billing Report22001 - FortiClient Default Report30001 - FortiDDos Default Reporturanium-esx50 # exe sql-report run root 10012
4) Run following command:
# diagnose system fsck harddiskThis operation will check and repair the file system, then reboot the system.Do you want to continue? (y/n)y
5) Manually rebuild hcache tables for the reports:See related articles.6) Rebuild the database:See related articles.7.) If the issue remains, please contact Fortinet TAC Support and provide additional details to the ticket such as output of following commands:
# diag test application sqlreportd 99# exe tac report
Also output of the commands ran in step 2 of debug section.In case chrome is used, it is also possible to download the Fortinet chrome extension in order to capture more details: https://chrome.google.com/webstore/detail/fortimanagerfortianalyzer/dhdlbdcjpkjngafjclfegbbcajbfhlac