Applies to
ApexSQL Monitor
Symptoms
The “Number of servers exceeds the number of available server licenses. Remaining licenses -1” error warning message appears in the Add instance page when trying to add a new SQL Server instance to monitor.
“Unable to open SQL Server connection” when installing application with repository database on a remote server
Applies to
ApexSQL Monitor, ApexSQL BI Monitor, ApexSQL VM Monitor
Symptoms
The “Unable to open SQL Server connection” error appears in the Configuration step of the ApexSQL Monitor installation when the remote SQL Server instance is specified in the Server name field of the Central repository database section
“Internal server error”, missing performance data, page cannot load or corrupted pages issues occur after application update
Applies to
ApexSQL Monitor, ApexSQL BI Monitor, ApexSQL VM Monitor
Symptoms
The “Internal server error” warning message appears in the various application pages, pages without performance data or corrupted pages are displayed, or page cannot be loaded issues might be encountered after the application is updated to a newer version.
Internal server error
Applies to
ApexSQL Monitor
Symptoms
The Internal server error warning message appears in the Dashboard page when in the instance tree view a particular SQL Server is selected.
“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
The “The server <server_name> doesn’t exist in the database” error is encountered when disabling the monitored SQL Server
Applies to
ApexSQL Monitor
Symptoms
After extended work in the ApexSQL Monitor console, when user selects the monitored SQL: Server instance from the monitored servers list and presses the Disable button, the error message “The server <server_name> doesn’t exist in the database” will pop up and the operation will not be accomplished leaving SQL Server enabled.
SQL Server database can’t be taken offline when monitored via ApexSQL Monitor
Applies to
ApexSQL Monitor
Symptoms
A SQL Server instance can’t be put offline using the SSMS Take Offline command when the hosting SQL Server is monitored by ApexSQL Monitor
Cannot update the ApexSQL Monitor user console to a newer version
Applies to
ApexSQL Monitor
Symptoms
On computers where only the user console is installed, the installer will offer only the full installation of ApexSQL Monitor, instead of clean updating of the user console
The “An error occurred when trying to replace existing file” error is encountered when updating ApexSQL Monitor
Applies to
ApexSQL Monitor 2014.03.0072
Summary
When updating ApexSQL Monitor 2014 R2 to ApexSQL Monitor 2014 R3 an error occurs.
The “System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation” error
Applies to
ApexSQL Monitor
Symptoms
When a user attempts to enter the global metrics period value immediately after selecting the Metrics view, the above error will occur and the application will close
