Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > Patch Manager primary application server is bound to wrong IP address

Patch Manager primary application server is bound to wrong IP address

Updated July 12, 2017

Overview

Patch Manager is displaying the wrong IP address inside the registry and in the Management Server section in the Patch Manager Console, which can affect agent creation and automation server and secondary application server connections.

Environment

All Patch Manager versions

Cause 

This may occur because of an IP address change to the primary application server.

Resolution

  1. Run mmc.exe.

  2. Click File > Add Remove/Snap-in > Add Certificates, and then select Computer account.

  3. Click Next > Finish > OK.

  4. Go to Trusted Root Certification Authorities > Certificates.

  5. Delete EminentWare Certificates.

  6. Remove CAHostname and CAIPAddress from the HKLM\SOFTWARE\EminentWare\Data Grid Service registry.

  7. Run SQL Management Studio and clear the record for PAS from dbo.gc_device and dbo.device.
    Note: Perform this step for both the Primary and Automation databases.

  8. Run setuphelper /provisionserver /type primary.

  9. Go to Patch Manager System Configuration > Security and User Management.

  10. Select Credentials, click Change Password, and then change the password.

  11. Go to Patch Manager System Configuration > Patch Manager Servers.

  12. Click the Patch Manager Server wizard, and then register the primary server.

 

 

Last modified

Tags

Classifications

Public