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:
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
Applies to
ApexSQL Audit
Symptoms
Data collected via ApexSQL Audit R1 version cannot be displayed via the embedded and web reports
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
Applies to
ApexSQL Audit
Symptoms
Auditing options cannot be configured for SQL Server with caps sensitive collation.
Applies to
ApexSQL Audit
Symptoms
The ApexSQL Audit installation runs normally until the required SQL Server and credentials information are entered and after that installation fails and the changes are rolled back. The installer just closes without any warning or info dialog.
Summary
The article explains what to do when the operating system freezes after ApexSQL Audit has been installed.
Summary
This article explains how to resolve the issue when ApexSQL Audit’s Web console shows the following error:
Summary
The ApexSQL Audit installation cannot be completed successfully due to missing prerequisites.
Applies to
ApexSQL Audit
Summary
This article explains what to do when the ApexSQL Audit central repository database, where ApexSQL Audit stores all audit information, grows too quickly.
