Applies to
ApexSQL Recover 2014
Summary
This article shows how to install ApexSQL Recover server-side components to a remote server.
The “Formatting profiles with duplicate names exist” message is shown when adding a new profile or when saving changes to an existing one
Applies to
ApexSQL Refactor version 2018.02
The ‘Unknown error has occurred. Please see %AppData%\Local\ApexSQL\<ApexSQL application name>\crash.txt’ error is encountered when starting application
Applies to
ApexSQL Log, ApexSQL Recover
Summary
This article explains how to resolve an issue which prevents ApexSQL Log or ApexSQL Recover from starting. When either application is launched, the ‘Unknown error has occurred. Please see %AppData%\Local\ApexSQL\<application name>\crash.txt’ error is encountered, and application fails to start.
The ‘Runtime Error (at -1:0): Cannot import dll:<utf8>%AppData%\Local\VCLStylesSkin\VclStylesIno.dll.’ error is encountered when uninstalling application
Applies to
All ApexSQL applications
Summary
This article explains how to resolve an issue which prevents uninstall process of ApexSQL tools. Once the uninstall process is initiated, the ‘Runtime Error (at -1:0): Cannot import dll:<utf8>%AppData%\Local\VCLStylesSkin\VclStylesIno.dll.’ error is encountered’ error is encountered and uninstall process is immediately terminated.
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:
Microsoft .NET framework 4.7.1 was not found
Applies to
ApexSQL tools
Symptoms
This article explains how to setup Microsoft .NET framework 4.7.1 in order to have ApexSQL tools running on a machine without any problems
Cannot uninstall add-in even when SQL Server Management Studio and Visual Studio are closed
Applies to
ApexSQL add-ins
Symptoms
This article explains how to resolve an uninstall problem when SQL Server Management Studio and Visual Studio are closed and the uninstall info message still appears, informing that SQL Server Management Studio or Visual Studio is running on a machine
The auto-complete hint-list or SQL Server Management Studio, itself, ‘freezes’ when using auto-complete
Applies to
ApexSQL Complete
Symptoms
This article explains what to do when the ApexSQL Complete hint-list requires too much time to load or occasionally “freezes” SQL Server Management Studio.
Conflicts between SSMS native Intellisense and the ApexSQL Complete hint-list
Applies to
ApexSQL Complete
Symptoms
Sometimes conflicts occur between the ApexSQL Complete hint-list and SSMS’s native Intellisense. In such cases, SSMS’s native Intellisense may overlap the ApexSQL Complete hint-list as shown below:
The ALM files are bulking up and using too much space
Applies to
ApexSQL Log
Summary
This article explains what to do when ApexSQL Log temporary files (.ALM type files) take too much space or when the number of .ALM files is too great
