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

ApexSQL Audit – An error occurred during local report processing

Summary
This article explains how to resolve the issue when ApexSQL Audit’s Web console shows the following error:

  • An error occurred during local report processing
    • The definition of the report ” is invalid
      • The value of the Width property for the tablix ‘ContentTablix’ is “X,X in”, which is not a valid size. Valid sizes may not exceed 455 inches