ApexSQL Audit web reports show no records

Summary
This article explains how to resolve the problem if ApexSQL Audit’s Web console shows no audited information, due to nothing being captured; what to check and how to fix any individual cause.

Symptoms
ApexSQL Audit’s Web console shows no audited information, due to nothing being captured.

Cause
There can be several reasons for this issue:

  1. ApexSQL Audit service is not running.
  2. The Log On account used for ApexSQL Audit service is not allowed to connect to the SQL Server instance.
  3. The audited ApexSQL Audit instance is not enlisted/connected in the central instance’s GUI.

Resolution
Depending on the cause, the following steps should be performed:

  1. To fix the service not running problem:
    • Run the Services applet in Windows Control Panel on the computer which hosts the audited SQL Server.
    • Check whether the ApexSQL Audit service is running.
    • If it is not running, start the service manually.
    • Set the Startup type option in service properties to Automatic.
  2. To fix the Log On account problem:
    • Run the Services applet in Windows Control Panel on the computer which hosts the audited SQL Server instance.
    • Check which account is used for the Log On As property for the ApexSQL Audit service.
    • Run SQL Server Management Studio.
    • Open the Properties dialog for the account used in the step b. and check whether it is a member of the sysadmin Server role.
    • If the account is not a member of the sysadmin fixed server role, add it to the sysadmin role by checking the appropriate checkbox.
  3. To check and fix the issue where an audited instance is not enlisted/connected to the central instance:
  4. Run the ApexSQL Audit GUI.
  5. Check whether all audited SQL Server instances are enlisted in the left sidebar of the GUI.
  6. If not, add the desired SQL Server instance by clicking Add Server.
  7. • Check whether all desired SQL Server instances are actually being audited or auditing has been stopped: audited SQL Server instances are marked with icon and not audited with icon
  8. If auditing has not been started, start auditing the desired SQL Server instance by clicking the Start button in the main toolbar of ApexSQL Audit GUI

Related posts:

  1. “Another instance of ApexSQL Audit Main GUI is started” error is encountered when trying to apply an auditing configuration change
  2. ApexSQL Audit reports don’t show everything I’m expecting
  3. ApexSQL Audit – An error occurred during local report processing
  4. Some ApexSQL Audit Web Reports requirements are not detected
  5. Reports doesn’t display any data collected by ApexSQL Audit 2014 R1 version after updating to a newer version