Error: Provisioning Server Router failed to connect to the Provisioning Directory

Products

• CA Identity Manager
• CA Identity Suite

Issue/Introduction

When an existing CA Identity Manager Provisioning Directory (CA Directory / IMPD) is already deployed on one server, attempting to install a second IMPD instance on another machine may result in the following error:

(Sep 21, 2018 12:13:11 AM), Install, com.ca.etrust.install.admin.ETAInstallRepositoryRouter, err,
The Provisioning Server Router failed to connect to the Provisioning Directory, which may need to be updated with knowledge of the Provisioning Server Router. Look at the log file C:\Users\ADMINI~1\AppData\Local\Temp\3/imps_server_install.log for details.

(Sep 21, 2018 12:13:11 AM), Install, com.ca.etrust.install.admin.ETAInstallRepositoryRouter, err,
ProductException: (error code = 200; message="Java error"; exception = [ProductException: (error code = -1; message="Provisioning Server Router failed to connect to Provisioning Directory")])

STACK_TRACE: 12

ProductException: (error code = 200; message="Java error"; exception = [ProductException: (error code = -1; message="Provisioning Server Router failed to connect to Provisioning Directory")])
    at com.ca.etrust.install.admin.ETAInstallRepositoryRouter.install(ETAInstallRepositoryRouter.java:152)
    at com.installshield.product.service.product.PureJavaProductServiceImpl.installProductAction(PureJavaProductServiceImpl.java:1916)
    at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.getResultForProductAction(PureJavaProductServiceImpl.java:5195)
    at com.installshield.product.service.product.InstallableObjectVisitor.visitComponent(InstallableObjectVisitor.java:369)
    at com.installshield.product.service.product.InstallableObjectVisitor.visitInstallableComponents(InstallableObjectVisitor.java:333)
    at com.installshield.product.service.product.InstallableObjectVisitor.visitProductBeans(InstallableObjectVisitor.java:133)
    at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.install(PureJavaProductServiceImpl.java:4563)
    at com.installshield.product.service.product.PureJavaProductServiceImpl$Installer.execute(PureJavaProductServiceImpl.java:3758)
    at com.installshield.wizard.service.AsynchronousOperation.run(AsynchronousOperation.java:41)
    at java.lang.Thread.run(Thread.java:745)

Environment

Release : 14.x
Component : Identity Manager
Component : Identity Suite Virtual Appliance

Cause

The problem is caused by an incorrect configuration within the Provisioning Directory.

Resolution

For vApp validate all configuration settings and retry the installation.

For on-premise deployment, ensure all Provisioning Directory servers are aware of on-boarding Provisioning Server.

• Re-run the Provisioning Directory installer on each of the hosts in 'REPAIR' mode.
• When prompted, specify the on-boarding Provisioning Server (PS) hostname.
• Run through to the last screen without changing anything else and you will notice:

A new PS router KNOWLEDGE .dxc file should be created under $DXHOME/config/knowledge folder.

Under the same folder, you will notice 'impd.dxg' file updated with 'source' line of this new imps-router.