ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Provisioning Directory DSA Fails to Start

book

Article ID: 20617

calendar_today

Updated On:

Products

CA Directory CA Identity Manager CA Identity Governance CA Identity Portal CA Risk Analytics CA Secure Cloud SaaS - Arcot A-OK (WebFort) CLOUDMINDER ADVANCED AUTHENTICATION CA Secure Cloud SaaS - Advanced Authentication CA Secure Cloud SaaS - Identity Management CA Secure Cloud SaaS - Single Sign On CA Security Command Center CA Data Protection (DataMinder) CA User Activity Reporting

Issue/Introduction

Description:

Provisioning Directory DSA Fails to Start

Following a reboot of the Provisioning Directory Server the Provisioning Directory fails to start.

Running the 'DXServer status' command shows all DSA(s) stopped and running the 'DXServer start' command fails to start the DSA(s).

This condition can occur when running the Provisioning Directory DSA(s) on a virtual machine, a stand-alone server, or clustered server(s).

Solution:

This problem can be the result of an incorrect Host Name, Port, or IPAddress.

Running the following cmd should point to the problem: dxserver -d start {dsaname}

  1. Verify that DHCP has NOT reassigned the Server a new IPAddress. If so, you will need to update the system Hosts file with the new IPAddress.
  2. Verify that the Host Name and Port are correct in the knowledge.dxc files under: C:\Program Files\CA\Directory\dxserver\config\knowledge

Environment

Release:
Component: IDMGR