When Cisco runs a manual sync to pull in any user changes, they receive the following error on the Cisco side:
"searchResDone(7) noSuchObject (No such object)"
This is the information reflected on the QCVDS side:
"conn=264 op=5 ABANDON targetop=NOTFOUND msgid=5"
------------------
Complete QCVDS error:
"[09/Jul/2013 08:15:13-0000] ip=10.10.22.10 conn=264 op=1 BIND dn="cn=ciscoldap,ou=hosting,dc=domain,dc=com" method=128 version=3
[09/Jul/2013 08:15:13-0000] ip=10.10.22.10 conn=264 op=1 RESULT err=0 tag=97 nentries=0 etime=0
[09/Jul/2013 08:15:13-0000] ip=10.10.22.10 conn=264 op=2 SRCH base="dc=rootdomain,dc=ldap" scope=0 filter=(&(ipphone=ucm)) attrs=ALL
[09/Jul/2013 08:15:13-0000] ip=10.10.22.10 conn=264 op=2 RESULT err=0 tag=101 nentries=0 etime=0
[09/Jul/2013 08:15:13-0000] ip=10.10.22.10 conn=264 op=3 SRCH base="dc=rootdomain,dc=ldap" scope=0 filter=(objectclass=*) attrs="subschemasubentry"
[09/Jul/2013 08:15:13-0000] ip=10.10.22.10 conn=264 op=3 RESULT err=0 tag=101 nentries=1 etime=0
[09/Jul/2013 08:15:13-0000] ip=10.10.22.10 conn=264 op=4 SRCH base="" scope=0 filter=(objectclass=*) attrs="subschemasubentry"
[09/Jul/2013 08:15:13-0000] ip=10.10.22.10 conn=264 op=4 RESULT err=0 tag=101 nentries=1 etime=0
[09/Jul/2013 08:15:13-0000] conn=264 op=5 ABANDON targetop=NOTFOUND msgid=5
[09/Jul/2013 08:15:13-0000] ip=10.10.22.10 conn=264 op=6 SRCH base="cn=aggregate,cn=schema,cn=configuration,dc=domain,dc=com" scope=0 filter=(objectclass=subschema) attrs="objectClasses,attributeTypes,matchingRules,ldapSyntaxes,objectClass,javaSerializedData,javaClassName,javaFactory,javaCodeBase,javaReferenceAddress,javaClassNames,javaRemoteLocation"
[09/Jul/2013 08:15:13-0000] ip=10.10.22.10 conn=264 op=6 RESULT err=32 tag=101 nentries=0 etime=0
[09/Jul/2013 08:15:13-0000] ip=10.10.22.10 conn=264 op=7 UNBIND"
The problem is when Cisco tries to retrieve the schema entry.
This query is on "cn=configuration,dc=domain,dc=com" branch, so when this query reaches the Virtual Tree, it doesn't know where to send the query and it doesn't find the schema entry.
The solution is to add a Branch Exception at the Virtual Tree tab with the following values:
Branch DN: cn=configuration,dc=domain,dc=com
Server Group: domain.com
© 2024 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center