Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > Upgrades to 2.0 fail with a database connection error

Upgrades to 2.0 fail with a database connection error

Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 1,070 Votes: 0 Revisions: 12

Overview

When upgrading the Patch Manager console to version 2.0 or later versions, you may encounter an error similar to the following:

 

Could not make a connection to the SQL Server. Database could not be applied.

Or

Checking Database Access failed. Database connection cannot be established.

Environment

Patch Manager 2.0

Cause

  • This occurs if you upgraded to Patch Manager 2.0 using ew_cds_007_2.0.2146.0 due to a bug that was fixed in later upgrade packages.
  • This error may be caused after a database migration if the upgrade is finding a reference to the old SQL server.

Resolution

Note: Consult your System Administrator before performing these steps.

 

Process 1:

  1. Before running the upgrade installer for Patch Manager version 2.0.1 or later, delete all registry keys except Default and TargetDir in the path HKEY_LOCAL_MACHINE > SOFTWARE > EminentWare > Data Grid Service.
    Warning: Do not delete the Default and TargetDir keys.
  2. Run the upgrade installer.

 

Process 2:

  1. Verify that the HKEY_LOCAL_MACHINE > SOFTWARE > EminentWare > Data Grid Service > ConnectionString has the correct value.
  2. Verify that ConfigurationWizard.xml file has the correct server information under the <DBSettings> tag.  The <Instance> information may reference the old server.
  3. If it does, back up the ConfigurationWizard.xml file and then edit the file to fix the incorrect entry.
  4. Run the upgrade installer again.
Last modified

Tags

Classifications

Public