We have more than 4 domains need to import CA CMDB with following commands.
But the 3rd domains always failed with error message 'pdm_ldap_import: Method got_record in Ldap_Catcher failed ()' .
pdm_ldap_import -l "last_name='%%'" -c "userid=?"pdm_ldap_import -n DomainB -l "last_name='%%'" -c "userid=?"
pdm_ldap_import -n DomainC -l "last_name='%%'" -c "userid=?"
pdm_ldap_sync pdm_ldap_sync -n DomainB
pdm_ldap_sync -n DomainC
Could you advise how to fix it ? thanks
Which version of SDM is this?
Checkout this doc: pdm_ldap_import errors out with "Method got_record in Ldap_Group_Catcher failed (LDAP agent not found)". maybe that'll help?
I did checked this document, it is different case with me, thanksk
Just quick question: Why is the 3rd domain NX_LDAP_PORT2=3268 while the 1st and 2nd are port 389?
The 3rd company only release 3268 for us, i have to use it to configure on CA.
And i did guess whether it related 2 different ports for same service, so change all ports to 3268, then 3rd one is not still work, no idea why.
Have you tested a connection to the 3rd party’s ldap server outside of service desk? Sorry if this is obvious, you didn’t mention it so I wanted to make sure.
I suggest running the ldp utility from the background or standby server to see if it works outside of sdm before adding the config to service desk.
That is standalone server, and it can be return ldap entries via LDAP browser on the server, always failed by PDM LDAP commands, no idea why
Is this behavior with the 3rd LDAP domain still happening?
If so, does the 'pdm_ldap_test' show any issues when connecting to the LDAP domain?
I think we managed to resolve this via the support case.
An LDAP browse of the DN account for the 3rd domain showed the sAMAccountname had one value whereas the CN and name had different values.They updated the sAMAccountname so that it matched the cn and name and that resolved the problem.