Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Database Performance Analyzer (DPA) > Cannot monitor SQL Server Monitor with DPA after applying a Cumulative Update patch

Cannot monitor SQL Server Monitor with DPA after applying a Cumulative Update patch

Created by Tiarnan Stacke, last modified by MindTouch on Jun 23, 2016

Views: 67 Votes: 3 Revisions: 8


This article describes the issue when you cannot start or register monitors in DPA after applying a Cumulative Update patch to a Microsoft SQL Server database, when the data used as a repository or monitored database. The following error appears:

org.quartz.JobExecutionException: DatabaseMonitorStartJob failed [See nested exception: java.lang.RuntimeException: Invalid version string []]

or org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'databaseMonitor' defined in class path resource [spring/idc-monitor.xml]: Cannot resolve reference to bean 'quartzScheduler' while setting bean


DPA 9.2 and earlier


SQL Server 2012' s Cumulative Update 7 and SQL Server 2014's Cumulative Updates have changed the reporting for the Version String "@@VERSION." This change causes monitors to fail.


The best solution for this issue is to upgrade to DPA 10 or newer.

If you are on version DPA 9.0 or 9.2 and cannot upgrade to DPA 10, you can download hot fixes from the SolarWinds Customer portal, at

Please note, If you're running 9.1, you'll need to upgrade to 10.0 or later.

Hot fixes are located under the License Management Tab>Archived Hot Fixes.

Last modified
19:07, 22 Jun 2016