Claims Search call failed. Error Message: Object reference not set to an instance of an object.

Sep 5, 2014 at 9:03 PM
Receiving the error: Claims Search call failed. Error Message: Object reference not set to an instance of an object. SUN LDAP server logs shows query being returned successfully. any ideas?


09/05/2014 16:55:20.96 w3wp.exe (0x1E28) 0x1ED4 LDAPCP LDAPCP 1337 Verbose [LDAPCP] LdapcpConfig PersistedObject found, version: 106551, previous version: 106551 461cf802-b3f0-4a74-8d84-15858e57f944
09/05/2014 16:55:20.96 w3wp.exe (0x1E28) 0x1ED4 LDAPCP LDAPCP 1337 Verbose [LDAPCP] LdapcpConfig PersistedObject found, version: 106551, previous version: 106551 461cf802-b3f0-4a74-8d84-15858e57f944
09/05/2014 16:55:20.96 w3wp.exe (0x1E28) 0x1ED4 LDAPCP LDAP Lookup 1337 Medium [LDAPCP] Connect as uid=sharepointImportQA, ou=People, o=Administrators, l=nyl, dc=newyorklife,dc=com to LDAP://DSQARO.NEWYORKLIFE.COM:389/L=nyl,DC=newyorklife,DC=com. 461cf802-b3f0-4a74-8d84-15858e57f944
09/05/2014 16:55:20.97 w3wp.exe (0x1E28) 0x1ED4 LDAPCP LDAP Lookup 1337 Medium [LDAPCP] This LDAP query did not return any result: "(| (&(objectclass=nylPerson)(nylid=Francois*)) (&(objectclass=user)(displayName=Francois*)) (&(objectclass=user)(cn=Francois*)(!(objectClass=computer))) (&(objectclass=user)(sn=Francois*)) )" 461cf802-b3f0-4a74-8d84-15858e57f944
09/05/2014 16:55:20.97 w3wp.exe (0x1E28) 0x1ED4 SharePoint Foundation Web Controls ad5x Medium Claims Search call failed. Error Message: Object reference not set to an instance of an object. Callstack: at Microsoft.SharePoint.WebControls.PeopleQueryControl.IssueClaimsQuery(String searchPattern, String providerID, String hierarchyNodeID, Int32 pageSize, SPProviderHierarchyTree spgroupTree). 461cf802-b3f0-4a74-8d84-15858e57f944
Coordinator
Sep 8, 2014 at 11:33 AM
Hello,
During what operation do you get this error?
ULS logs you copied show that LDAP server did not return any result. Do you expect to get results? Is this the only query that generates this exception?
Cheers,
Yvan
Sep 8, 2014 at 2:00 PM
Hi Yvand,

This is happening when doing a people picker search. I expect results to be returned and can run the query in an LDAP Browser and return results. Also when looking in the logs on the LDAP server I see that results are returned when making the query with LDAPCP. All queries generate this exception.

Coordinator
Sep 9, 2014 at 12:01 PM
hello,
can you set LDAPCP logging in verbose with cmdlet below and share the result:
Set-SPLogLevel -Identity "LDAPCP:*" -TraceSeverity Verbose