Applies to:
ApexSQL Backup
Symptoms:
In the process of selecting a SQL Server that will host the ApexSQL Backup Central Repository Database the ‘Cannot connect to server’ error is encountered if selected server has a default named instance.
“RESTORE LOG is terminating abnormally” error is encountered in during the restore database step in the log shipping job
Applies to:
ApexSQL Backup
Symptoms:
If a destination database recovery state is not set to the no-recovery (restoring) state, log shipping job will fail during the process of transaction log restore with the "The log or differential backup cannot be restored because no files are ready to rollforward. RESTORE LOG is terminating abnormally" error.
Restore job fails during the log shipping process and the ‘System.Data.SqlClient.SqlError: …. An earlier log backup that includes LSN can be restored.’ error is encountered
Applies to:
ApexSQL Backup
Symptoms:
During the process of Log shipping, the restore transaction log job fails and the ‘System.Data.SqlClient.SqlError: The log in this backup set begins at LSN, which is too recent to apply to the database. An earlier log backup that includes LSN can be restored.’ error is encountered, and whole process fails.
The Out Of Memory exception is encountered when comparing large databases in ApexSQL Data Diff
Applies to:
ApexSQL Data Diff
Symptoms:
If very large databases are compared, in some cases, the memory limitation of the application may be exceeded. If so this will produce an Out Of Memory error.
The application’s GUI disappears and cannot be displayed when using multi-monitor setup
Applies to
ApexSQL Data Diff, ApexSQL Diff, ApexSQL Generate and ApexSQL Script
Symptoms
If the multi-monitor setup is used, while working with mentioned applications, the following issues could be experienced:
ApexSQL Source Control shared database model doesn’t work after update
Applies to
ApexSQL Source Control
Symptoms
After upgrading from the previous versions to 2015.03.0065 or higher, ApexSQL Source Control cannot detect the previously linked shared databases and a “The path is not of a legal form” error is encountered when opening the Action Center tab:
A “Error 404” error is encountered when linking a database to Team Foundation Server in a different domain from the host
Applies to
ApexSQL Source Control
Symptoms
During the process of a database linking to Team Foundation Server located in a different domain from the host machine, ApexSQL Source Control will not be able to resolve a DNS address and an error will be thrown:
Functionality in ApexSQL Complete is disabled
Applies to
ApexSQL Complete and ApexSQL Search
Symptoms
This issue is encountered after the installation of ApexSQL Complete and ApexSQL Search latest releases. Due to the conflict issue between mentioned add-ins, functionality in ApexSQL Complete is disabled.
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
