Error "AHD04013: internal error in method ldap (got_ldap_domset): AHD03053: INVALID WHERE CLAUSE: Parse error at: "ldap_domain = ? AND userid = ?" (Attr not found or not atomic)" when running pdm_ldap utilities

Document ID : KB000031739
Last Modified Date : 14/02/2018
Show Technical Document Details

Problem:

In a scenario where running pdm_ldap utilities (import, sync or merge contact) fails and CA SDM shows the following error:

AHD04013: internal error in method ldap (got_ldap_domset):

AHD03053: INVALID WHERE CLAUSE:

Parse error at: "ldap_domain = ? AND userid = ?" (Attr not found or not atomic)

 

Environment: 

 

This problem can be seeing in CA Service Desk Manager (CA SDM) 12.9 installations.

 

Resolution:

Verify the following points:

  1. If there had been any customization added to ldap.maj file under NX_ROOT\bopcfg\majic.
    If so, you should create a ldap.mod file under NX_ROOT\site\mods\majic with the customizations needed and restore a copy of the original file under NX_ROOT\bopcfg\majic.

  2. If you installed Cumulative Fix 1 (CF1) for SDM 12.9, verify that the ldap.maj file was properly installed - you may compare the file under NX_ROOT\bopcfg\majic and the one from the CF1 package.
    If the one under NX_ROOT doesn't have new attribute "ldap_domain", then it has not been installed and that is the reason why you are getting the problem - possibly because the file under NX_ROOT\bopcfg\majic folder was edited or changed (which is not recommended), and the file timestamp was newer than the one from the CF1, and in this scenario, the fix installation will preserve the newer one. 
    You will need to manually copy the file from the CF package to the one under NX_ROOT\bopcfg.

    Note that is CF1 introduces a new feature which allows the pdm_ldap utilities to access multiple ADs and as part of that added attribute ldap.domain to the file.

 

Additional Information:  

 

You can refer to the following entry in CA SDM 12.9 Administration Guide for additional details:
Configuring User Accounts > Special Handling Types > How CA SDM uses LDAP Data to Communicate > Attribute Mapping