I am trying to import from AD by using PDM_LDAP_IMPORT, however it returns an error message "Method got_dob in Ldap_Catcher failed (NOT FOUND)"
STDLOG shows "web:local 13064 ERROR parse.c 8051 Unable to fetch DOB for PDM_LIST at lsEnd.mac: NOT FOUND"
I tried PDM_LDAP_TEST, and it was able to read the info.
Does anyone have anyone why is this happening? Thanks in advance.
Edit. I run into this issue again with CA SDM 14.1, this time the work around provided by Lila does not work.
Any one has experience with this issue on 14.1.02?
Whats the version of SDM and its patch level? It worked fine earlier or never worked? Did you add any to the custom ldap.mod file? If yes, remove the file from site/mods/majic folder and then try to import the contacts to see if it works.
It is 12.9 SDM version dtn-416, with Cumulative Patch #1.
It never worked since install and there is no custom ldap.mod file.
Can you verify if CUM#1 was corretly applied? If applied correctly then 3 patches should comprise it.
I had a similar issue in the past, in that case:
When i try create user from LDAP like:
File --> New Contact from LDAP --> Click on Search buttonI dont see no one user in list, but in count (bottom right corner) i see:
1-17 of 17.
Unable to fetch DOB for PDM_LIST at lsEnd.mac
Problem is due the ldap_search_base defined as
the space after the comma cause this issue,
after change to:
problem is fixed.
I hope it helps ...
Thinking about problem num #2970 by looking at the error "Method got_dob in Ldap_Catcher failed (NOT FOUND)".
Thanks a lot for your help. Your solution works like a charm.
Excellent! I just came across this issue with SDM 14.1 at a client site. Had me quite puzzled but this solution hit the spot.
I run into this issue again with 14.1, I created this post when I was working with 12.9.
Just wondering did this work around fix the issue?
And did your environment apply any cum patch?
Because it seem this work around no longer work with 14.1.
I am having the same issue with SDM 14.1.03 and there is no space in the ldap_search_base. Did you resolve this?
I had same problem in 220.127.116.11. (fresh migrate from 12.5)
This idea resolved!