Applies to
Problem description
When starting the ApexSQL Audit main GUI from a remote workstation the GUI is started but the connection to the central instance has not been established and the message shown in the screenshot below pops up:
Preview option fails to generate report and display event data
Applies to
Problem description
When the Preview button is clicked, the preview generation lasts unusually long and, when finished, no results are being displayed in the central grid view. The central grid will display the “No events found” message, even though the data search returned information that there are some rows found in the targeted scope (the Total events information below the central grid view), which indicates that, in fact, there is some data to display.
Success status is shown in the report when captured event contains a failed query
Applies to
Problem description
When using the Extended Events technology for data collection, failed user queries can be captured, and will be shown in reports with the success status. The article will explain how to set auditing configuration to be able to recognize the quality of such events in reports.
“Another instance of ApexSQL Audit Main GUI is started” error is encountered when trying to apply an auditing configuration change
Problem description
Process of applying configuration changes fails with the “Another instance of ApexSQL Audit Main GUI is started” error shown in the information ribbon and old auditing configuration is retained
How to establish a connection with the central instance after a failed attempt
Applies to
Problem description
ApexSQL Audit is not manageable through the application interface because of the faulted connection to the central repository database.
Cannot browse for folder in Auditing agent properties dialog – The “Accessing remote folder from the location not possible” error is encountered
Applies to
Problem description
The “Accessing remote folder from the location not possible” error is encountered when trying to select a temporary folder destination when adding SQL Server for auditing or editing one that was already added.
Unable to install server-side components on the remote machine
Applies to
ApexSQL Audit
Symptoms
When adding the remote SQL Server instance in the server auditing list and process failes due to the required server-side components are not installed on the target machine (Windows service which allows auditing of SQL Server instances remotely via the ApexSQL Audit main application), and ultimately leading to the error:
“Could not allocate space for object ‘<object_name>’ in database ‘<database_name>’ because the ‘PRIMARY’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.”
Applies to
ApexSQL Audit, ApexSQL Monitor
Symptoms
The error message is telling you that the ‘PRIMARY’ filegroup is full. This article explains how to resolve this error is encountered when working with application. The error will prevent storing any audited or monitored data into a central repository database
Reports doesn’t display any data collected by ApexSQL Audit 2014 R1 version after updating to a newer version
Applies to
ApexSQL Audit
Symptoms
Data collected via ApexSQL Audit R1 version cannot be displayed via the embedded and web reports
The “The server cannot handle directory requests” error is encountered during installation
Applies to
ApexSQL Audit
Symptoms
ApexSQL Audit installation on a computer that is the part of the Active Directory network, could result in the error: “The server cannot handle directory requests” after inserting the required credentials and installation will stop
