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 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
Description: An exception occurred in All Users claim provider when calling SPClaimProvider.FillHierarchy(): Object reference not set to an instance of an object..
One of those settings is for the Secure Store. Without it, you cannot use PerformancePoint’s unattended service account to connect to data sources. As with the 2007 version of the product, which used the application pool account as the application identity, the unattended account cannot use the application pool identity to connect to data sources. Rather, it must use a domain account, whose password is stored in the secure store. If you have created a new PerformancePoint service application and there is no secure store set up in the default proxy group, you will need to configure the secure store. You can tell whether things have been set up correctly when you go to the PPS settings page. You will see a warning indicating that the secure store hasn’t been configured.
|Secure Store Warning|
In order to configure the secure store, you will need to create a secure store service first. Do that by clicking on New (in the ribbon) from the Manage Service Applications page. If the Edit functions in the ribbon appear inactive, make sure that the secure store service has been started. You can check this by going to the Manage services on server page in Central Administration. If it hasn’t been started, start it, and proceed with the steps below. Fill in the parameters, and click OK. Once the service is created, you can configure it.
To configure the secure store for PPS, follow these steps:
Configure the Unattended Service Account (necessary for using "Unattended Service Account" option on Data Sources)