Troubleshooting: No Data Found in report result
Why am I receiving ‘No Data Found’ in report result?
After trying to generate a report, the following is displayed in in the Report Results window:
'NO DATA WAS FOUND FOR THE REPORT SELECTION CRITERIA'
Typically, this is caused by one or more of the following conditions:
- The Log Sources are not correct, or do not have data loaded or categorized for the specified report filters (date/time, category, user)
- An incorrect log file format or date has been selected
- There are no log records for the date or time, categories, user(s), report filters, or log source(s) selected in the report filter properties
- Permissions are not set to allow the services account access to the log file directory
The Log Sources are not correct, or do not have data loaded or categorized for the specified report filters (date/time, category, user):
bt-LogAnalyzerSE must be configured with the correct log source in order to pre-load and categorize the log data for reporting.
Verify that your log source(s) is/are correct by running a test in the log source properties page to determine if bt-LogAnalyzerSE is able to detect and read the log files.
Navigate to the Log Source List page by clicking the ‘Log Sources | Log Source List’ menu item
Navigate to the properties page of the log source(s) that is/are being used to report on. This can be done by clicking the desired log source, then clicking the ‘Log Source Properties’ link in the left-hand menu, under the Log Source List section. This can also be done by clicking the ‘Log Source Properties’ button, located on the right-hand side of the desired log source.
Ensure that the proper log file format is used
Ensure that the ‘Use all files’ option is selected under the Use Following Files section. If using an ODBC connection or Watchguard log source, ensure that the proper values are entered into the required fields.
Note: For remote MSDE databases, ensure that the ‘Use remote server for this Log Source’ option is selected and the remote MSDE server is specified in the Advanced tab of the properties page. Then ensure that the Remote Log Data Loader is properly installed and configured on the remote server.(See the FAQ on setting up the ‘Remote Log Data Loader’ option)
Click the ‘Test’ button near the bottom of the properties page. You should see green text just above the properties page menu tabs indicating a successful test, along with the number of log files or records found. If bt-LogAnalyzerSE is unable to read the log files, an error message in red text will be displayed.
If the test fails, there is a permissions or access problem with the directory, please see the section labeled Permissions are not set to allow the services account access to the log file directory: to change the settings.
Verify that you have data loaded and categorized for the date and time range that you are attempting to report on:
- Navigate to the Loading History section by hovering your mouse over the Log Sources menu item, then click on ‘Loading History’
- Verify that data has been loaded and categorized successfully for the necessary date range of the log source being reported on. If the ‘Status’ column indicates ‘Data loaded’ and there is a ‘0’ under the ‘Records’ column, no data has been loaded for that operation date. Also if the Status says ‘Data loading’ or ‘Data categorizing’ you must wait until these operations are completed before attempting to generate the report.
Verify that data has not been purged for the dates that are being reported on after the successful load and categorization. The ‘Date from’ and ‘Date to’ columns will have dates that show the range of the data that was purged. This would indicate that though the data was previously loaded and categorized, a purge operation has cleared the data from the database. At this point, the data must be reloaded and categorized to be reported on.
An incorrect log file format or date has been selected:
All Microsoft logs should use the default, ‘Auto-detect – MS’ date and file format. All other log file types should be selected from the drop down list. If using custom/modified Microsoft ISA Server logs, please ensure they contain the following fields:
- Client IP (c-ip)
- Client User Name (cs-username)
- Date (date)
- Time (time)
- Processing Time (time-taken)
- Bytes Sent (cs-bytes)
- Bytes Received (sc-bytes)
- Protocol (cs-protocol)
- Operation (s-operation)
- Object Name (cs-url)
- Object MIME (cs-mime-type)
- Result Code (sc-status)
There are no log records for the date or time, categories, user(s), report filters, or log source(s) selected in the report filter properties
Note: When trying to diagnose why reports show ‘No Data..’ it is usually best to remove as many of the filters as possible to first verify that you have data to be reported on. Once you confirm that you have data available, you can then start adding filters to find out what causes the 'No Data Found' message.
Navigate to the Reports section of the bt-LogAnalyzerSE interface by clicking the ‘Reports’ menu item
Navigate to the properties page of the desired report by first selecting the report, then clicking the ‘Report Properties’ option in the left-hand menu under the Reports section. You can also click the ‘Report Properties’ icon associated with the desired report located on the right-hand side of the report.
From the report properties page, select the ‘Customize’ tab
Click the ‘Edit’ button for Date/Time
Select a ‘Custom’ date range for a period of time in which you are certain that URL data from log files has been loaded and categorized. If filtering a specific time range, be sure to include a time range that you are certain is included in the log files that are loaded and categorized. Click ‘OK’ to save the changes.
Click the ‘Edit’ button for Categories, and be sure to select ‘All categories’.
Note: this filter can be modified later to specify only the desired categories, but for troubleshooting purposes, should be set to ‘All categories’.
Click the ‘Edit’ button for Users and select ‘All users’. Save the changes for the user filter by clicking ‘OK’.
Click the ‘Edit’ button for Reports and ensure that NO report filters are selected. This filter should only be used for more complicated reporting functionality, and will result in ‘No Data Found’ report results if not configured correctly.
Click the ‘Edit’ button for Related Log Sources, and be sure to select either ‘All log sources’ or the individual log source that you are certain has data loaded and categorized, which fits the date/time, user, and category filters applied to the report.
Save the changes, then re-generate the report
Permissions are not set to allow the services account access to the log file directory:
Verify that the service account for the below services has read access to the desired log files:
If the LA7 services account must be changed, make sure that the requirements included in the bt-LogAnalyzerSE Installation manual still apply (Local Admin permissions, DBO role on all three LAEE_* databases).