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:

“Connection was failed with message: ‘The executable did not complete within the allotted time’” message

Applies to
ApexSQL Data Diff

Symptoms
“Connection was failed with message: ‘The executable did not complete within the allotted time’” message can be encountered during the recomparison after synchronizing to the Mercurial source control repository, when the synchronization script exceeds 300 MB in size. This message can be also encountered if the connection speed between local machine and Mercurial hosting service is slow.

“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