Resolution
Directory and Resource Administrator 6.x
fact
Directory and Resource Administrator 7.x
symptom
Directory and Resource Administrator (DRA) client interfaces are being directed to a DRA server which is offline.
symptom
Some Directory and Resource Administrator (DRA) clients are being directed to a DRA server which encountered a hardware failure.
cause
The secondary Directory and Resource Administrator (DRA) server, which is offline, is still registered with the NetIQ DRA Agent. The NetIQ DRA Agent is not aware that the secondary server is no longer running.
If the secondary DRA server crashes or encounters a hardware failure, it is not automatically un-registered with the NetIQ DRA Agent; DRA clients may still be directed to this unavailable server. When a DRA server is gracefully taken offline by stopping the NetIQ Administration Server (MCS OnePoint Administration Server) service, the server un-registers itself with the NetIQ DRA Agent service.
fix
If a DRA server was ungracefully taken offline and is still registered with the NetIQ DRA Agent service, please contact NetIQ Technical Support to obtain a supported version of the EAAgentUtil which includes a /UnregisterEx switch.
The enhanced EAAgentUtil is also available for download from the Knowledge Depot at: https://www.netiq.com/support/dra/extended/knowledgedepot/default.asp.
fix
You can also manually un-register the DRA server by performing the following steps on each domain controller running the NetIQ DRA Agent service:
- Launch Regedt32.
- Expand the DraAgent data key under HKEY_LOCAL_MACHINE | SOFTWARE | Mission Critical Software.
- Delete the dra_server_name data key.
- Restart the NetIQ DRA Agent service using the Services applet.
An Enhancement Request has been opened with Development to include this functionality in a future version of Directory and Resource Administrator.