The log files are located in the <FirewallAnalyzer_Home> / server / default / log directory. Typically when you run into a problem, you will be asked to send the serverout.txt file from this directory to Firewall Analyzer Support.
Internet Explorer throws this error when you try to open an exported PDF report in the web browser itself. This is a known issue, and we are working on resolving it. For now, save the report to your local machine, and open it using the regular PDF software that you use (Adobe Acrobat Reader or xpdf)
Probable cause: Firewall Analyzer installation directory 'ManageEngine' is accessed by other applications. It is possibile that the inbuilt MySql database of Firewall Analyzer could get corrupted if other processes are accessing these directories.
Solution: Kindly exclude the 'ManageEngine' directory (prior to version 6.0 it was C:\AdventNet or D:\ AdventNet) from both the Backup process and Anti-Virus Scans.
To increase the time limit of web client time out, follow the steps given below:
The above changes will affect all the web clients connected to the FWA server.
Alternatively, you can install the "Auto IE Refresher" in your machine for IE browser and monitor the pages from your machine.
Reference pages:
http:/www.softpedia.com/get/Internet/Other-Internet-Related/Auto-IE-Refresher.shtml
This message could be shown in two cases:
Case 1: Your system date is set to a future or past date. In this case, uninstall Firewall Analyzer, reset the system date to the current date and time, and re-install Firewall Analyzer.
Case 2: You may have provided an incorrect or corrupted license file. Verify that you have applied the license file obtained from ZOHO Corp.
If neither is the reason, or you are still getting this error, contact licensing@manageengine.com
The web server port you have selected during installation is possibly being used by another application. Configure that application to use another port, or change the Firewall Analyzer web server port.
MySQL-related errors on Windows machinesProbable cause: An instance of MySQL is already running on this machine.
Solution: Shut down all instances of MySQL and then start the Firewall Analyzer server.
Probable cause: Port 33336 is not free
Solution: Kill the other application running on port 33336. If you cannot free this port, then change the MySQL port used in Firewall Analyzer.
Firewall Analyzer displays "Port 8500 needed by Firewall Analyzer is being used by another application. Please free the port and restart Firewall Analyzer" when trying to start the server
Probable cause: The default web server port used by Firewall Analyzer is not free.
Solution: Kill the other application running on port 8500. If you cannot free this port, then change the web server port used in Firewall Analyzer.
Probable cause: An instance of MySQL is already running on this machine.
Solution: Shut down all instances of MySQL and then start the Firewall Analyzer server.
Probable cause: Port 33336 is not free
Solution: Kill the other application running on port 33336. If you cannot free this port, then change the MySQL port used in Firewall Analyzer.
Probable cause: The default web server port used by Firewall Analyzer is not free.
Solution: Kill the other application running on port 8500. If you cannot free this port, then change the web server port used in Firewall Analyzer.
Probable cause:Graphs are empty either because there is no traffic passing through the firewall or if the firewall traffic is not sufficient enough to populate the reports table of Firewall Analyzer.
Solution: If you are starting Firewall Analyzer for the first time or if you are shutting down and restarting Firewall Analyzer, it will wait for the reports table to be populated with 5000 log records for the first time. From the next time onwards, Firewall Analyzer will populate reports table once in 7 minutes or once it receives the next 5000 records, whichever is earlier. You can check for the number of records received in " Packet Count " icon shown in top right corner in client UI. This will list out the details like the number of logs received and also the last received log time. It is better to run the server continuously and check whether 5000 records are collected. Do not stop and restart the server in-between!
Moreover, for viewing the already collected log records in the reports, kindly do the following:
http: // localhost:8500/fw/genreport.do
You cannot see Live Reports for SonicWALL firewalls because the time duration attribute is not supported in the SonicWALL log files.
Since Firewall Analyzer processes log files as and when they are received, traffic values of 0.0MB or 0.0% may be displayed initially when the amount of traffic is less than 10KB. In such a case, wait until more data is received to populate the report tables.
This could be happening because bandwidth information is not being captured in the log file. Ensure that your Check Point firewall has been configured to generate both regular and accounting log files. While regular log files contain information regarding firewall activity, the accounting log file contains the bandwidth and session information.
Verify if intranets have been configured correctly. If you have specified IP addresses that are not actually behind the firewall, you will get zero values in the reports.
Trend reports show historical data for the corresponding traffic statistics shown in the report. Hence time changes from the Global Calendar, or top-n value changes from the Show bar on the report, do not affect these reports.
Firewall Analyzer checks for the entry "arg=your URL" in the firewall logs to populate and show URL in report data. If this entry is not present in the firewall logs then the reports wouldn't be showing any URL information.