Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Database Performance Analyzer (DPA) > Error or unsuccessful when trying to register a Microsoft SQL Server for monitoring

Error or unsuccessful when trying to register a Microsoft SQL Server for monitoring

Created by Interspire Import, last modified by Robert Holtam on Aug 24, 2016

Views: 191 Votes: 0 Revisions: 10

Overview

You can't register a Microsoft SQL Server to monitor it. The registering process either hangs, or the monitor appears down. You may get the error message "Could not get JDBC Connection; nested exception is java.sql.SQLException: I/O Error: DB server closed connection."

Environment

Applies to DPA version 9.1 and earlier

Resolution

There are two workarounds:

  • Disable SSL record splitting at the JRE Level
  • Use an earlier version of the Oracle JRE (Linux/Unix only)

Disable SSL record splitting at the JRE Level

On Windows:

  1. Edit the file: {install directory}\iwc\tomcat\bin\service.bat
    The default {install directory} is: "C:\Program Files(x86)\SolarWinds\ignite pi"
  2. Find the line:
    "%EXECUTABLE%" //US//%SERVICE_NAME% --JvmOptions "-Dcatalina.base=%CATALINA_BASE%;-Dcatalina.home=%CATALINA_HOME%;-Djava.endorsed.dirs=%CATALINA_HOME%\endorsed" --StartMode jvm --StopMode jvm
  3. Modify the line to:
    "%EXECUTABLE%" //US//%SERVICE_NAME% --JvmOptions "-Djsse.enableCBCProtection=false;-Dcatalina.base=%CATALINA_BASE%;-Dcatalina.home=%CATALINA_HOME%;-Djava.endorsed.dirs=%CATALINA_HOME%\endorsed" --StartMode jvm --StopMode jvm

Note: There are no spaces between the semicolons(;) and the hyphens(-).

  1. Edit repo.propertes file and add: repo.additionalProperties=ssl=request  then save.
  2. Remove the Ignite PI Server service:
    1. Open a Command Prompt with Run as Administrator.
    2. Change directory (cd) to the DPA home directory.
    3. Run removeWindowsService.bat.
  3. Check the Windows Services list to make sure the Ignite PI Server service has been removed.
  4. Create a new Ignite PI Server service:
    1. Open a Command Prompt with Run as Administrator.
    2. Run createWindowsService.bat.

On Linux/Unix:

  1. Edit the file: {install directory}/iwc/tomcat/bin/catalina.sh
  2. Search for the section containing:
    JAVA_OPTS="$JAVA_OPTS -XX:MaxPermSize=128m"
    JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote"
    JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true"
    JAVA_OPTS="$JAVA_OPTS -Dnet.sf.ehcache.skipUpdateCheck=true"
  3. Add the following JAVA_OPTS line:
    JAVA_OPTS="$JAVA_OPTS -Djsse.enableCBCProtection=false"

Use an earlier version of the Oracle JRE (Linux/Unix only)

SolarWinds DPA ships with JRE version 6 update 45. To resolve this Microsoft SQL Server issue, we recommend downgrading to JRE version 6 update 20, a version we have successfully used with DPA in the past.

  1. Download and install JRE version 6 update 20.
  2. Locate the path to the java executable file for this version.
  3. Open the file:
    {install directory}/iwc/tomcat/ignite_config/java_loc.txt
  4. Find the line containing the path to the java executable. For example:
    /home/java/jdk160_03/bin/java
  5. Update the path to point to the new java executable, and save the file.
  6. Restart Ignite PI by running:

    {install directory}\shutdown.sh
    {install directory}\startup.sh

Cause

Microsoft has a bug that prevents applications with later versions of Java 1.6 from monitoring SQL Server instances. SolarWinds DPA is affected by this Microsoft issue.

Last modified

Tags

Classifications

Public