Applies to
Problem description
When starting the ApexSQL Audit main GUI from a remote workstation the GUI is started but the connection to the central instance has not been established and the message shown in the screenshot below pops up:
Preview option fails to generate report and display event data
Applies to
Problem description
When the Preview button is clicked, the preview generation lasts unusually long and, when finished, no results are being displayed in the central grid view. The central grid will display the “No events found” message, even though the data search returned information that there are some rows found in the targeted scope (the Total events information below the central grid view), which indicates that, in fact, there is some data to display.
Success status is shown in the report when captured event contains a failed query
Applies to
Problem description
When using the Extended Events technology for data collection, failed user queries can be captured, and will be shown in reports with the success status. The article will explain how to set auditing configuration to be able to recognize the quality of such events in reports.
An object containing special characters in the schema name is shown as non-existing on a database side in the Action center tab after the initial commit is finished
Applies to
Symptoms
After the linking process and initial commit is done objects with the special characters in their name will be listed only in the Repository column like they have not been committed at all. Those objects will be listed as the Custom script type under the Type column and the wrong schema will be listed under the Schema column.
Objects are shown in the Action center tab as non-existing on both sides and history for those objects is not accessible
Applies to
ApexSQL Source Control
Symptoms
The objects containing Windows reserved words in their name are committed to the source control repository with the 2021.01.2063 or 2021.01.2072 add-in versions. Upgrade to the newer add-in version is done, the Action center tab is opened but the already committed objects are listed.
“Runtime error 217 at XXXXXXXX” error is encountered when starting installation process
Applies to
ApexSQL installer
Problem description
When starting the ApexSQL installer, the Windows taskbar will show the ApexSQL installer icon, but instead of installation splash window, the following Windows-based popup appears:
“Object reference not set to an instance of an object” message is shown on SQL Server Management Studio startup
Applies to
SQL Server Management Studio add-ins
Problem description
In some cases, with various ApexSQL add-ins integrated into the same host, after an upgrade of one or more add-ins, the user might be unable to launch the host application successfully.
ApexSQL Log cannot remotely connect to a SQL Server 2008/2008 R2
Problem description
ApexSQL Log is unable to remotely connect to Microsoft SQL Server 2008/2008 R2 (x86/x64/IA64) editions.
“Another instance of ApexSQL Audit Main GUI is started” error is encountered when trying to apply an auditing configuration change
Problem description
Process of applying configuration changes fails with the “Another instance of ApexSQL Audit Main GUI is started” error shown in the information ribbon and old auditing configuration is retained
“Invalid activation code” error is encountered when trying to activate the product using the automatic activation process
Applies to:
All tools
Summary:
The proper service account has been created and an error message informing the user that the application is in the trial mode is shown after initiating activation.
