Submit a ticketCall us

Announcing NPM 12.2
With NPM 12.2 you can monitor your Cisco ASA firewalls, to monitor VPN tunnels for basic visibility and troubleshooting tunnels. NPM 12.2 also uses the SolarWinds Orion Installer so you can easily install and upgrade one or more Orion Platform products simultaneously.
See new features and improvements.

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: 128 Votes: 3 Revisions: 8

Overview

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:

 DB: SQLSERVERINSTANCE
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

Environment

DPA 9.2 and earlier

Cause 

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.

Resolution

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 https://customerportal.solarwinds.com.

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

Tags

Classifications

Public