Blog Job Engineering
Monday, February 27, 2012
 
An error has occurred in the claim providers configured from this site collection

Error Message when checking names: Name does not resolve and following error displayed:

No exact match was found. Click the item(s) that did not resolve for more options.

Using People Picker displays this error:

An has occurred in the claim providers configured from this site collection

An error has occurred in the claim providers configured from this site collection

In Event Log you will see the error below. If you look events that occurred just before the event 8307 An exception occurred in All Users claim provider when calling SPClaimProvider.FillHierarchy() you will notice few Alternate Access Mapping Errors (event id: 8059). They seems to be irrelevant but that’s exactly the cause. You are missing AAM mapping that user is using to access the site where name resolution was attempted. There might be million other reasons for error you chasing but try this first and make sure you have AAM configured. Note, batteries not included and reboot or IIS reset not required for AAM updated to take effect J

Log Name: Application
Source: Microsoft-SharePoint Products-SharePoint Foundation
Date: 1/29/2011 7:33:36 PM
Event ID: 8307
Task Category: Claims Authentication
Level: Error
Keywords:
User: Domain\loginID
Computer: serverName.domain.com
Description: An exception occurred in All Users claim provider when calling SPClaimProvider.FillHierarchy(): Object reference not set to an instance of an object..

Event Xml:



8307
14
2
47
0
0x4000000000000000

51361


Application
<serverName.domain.com>



All Users
SPClaimProvider.FillHierarchy()
Object reference not set to an instance of an object.



http://www.agileconcepts.com/Blogs/AQ/Lists/Posts/Post.aspx?ID=52
 
Comments: Post a Comment
not another bull crap blog page

ARCHIVES
05/01/2003 - 06/01/2003 / 08/01/2003 - 09/01/2003 / 12/01/2004 - 01/01/2005 / 03/01/2005 - 04/01/2005 / 06/01/2005 - 07/01/2005 / 05/01/2006 - 06/01/2006 / 06/01/2006 - 07/01/2006 / 01/01/2009 - 02/01/2009 / 03/01/2009 - 04/01/2009 / 05/01/2010 - 06/01/2010 / 01/01/2012 - 02/01/2012 / 02/01/2012 - 03/01/2012 / 07/01/2012 - 08/01/2012 /


Powered by Blogger