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

Hello,

In central admin I am trying to create a new secure store application.

when I try to set the "target application administrator" it does not resolve any name.

when I click on the people picker icon I get this error

 

How I can resolve this?

December 14th, 2011 7:55pm

hi,

 

try this:

http://www.mstechblogs.com/sharepoint/an-error-has-occurred-in-the-claim-providers-sharepoint2010/

http://sharepoint.nauplius.net/2011/03/sharepoint-error-error-has-occured-in.html

 

Thanks and Regards,

Silambarasan.P

www.sharepointwarriors.com

 

Free Windows Admin Tool Kit Click here and download it now
December 15th, 2011 6:00am

yes. everyone was able to solve the problem by defining the right access control mapping. Except me

In my central admin there are two access control mappings defined for the CA web app

 

1. http://myserver:29066 (default)

2. http://myserver.mydomain.com:29066 (intranet)

 

I always access CA with http://myserver.mydomain.com:29066. If I try to access using http://myserver:29066 then my firms proxy does not resolve the machine name correctly (so i must type FQDN).

Now with FQDN URL the people picker in configuration of Secure Store application does not work (Mind you that people picker everywhere is working fine and I do not get this error anywhere else.... only when configuring secure store application, I get this error).

 

December 15th, 2011 7:59am

I solved the problem by creating a new alternate access mapping for

http://localhost:29066

Now my proxy does not kick in as I am using localhost and sharepoint lets me in because of the AAM.

the people picker is working fine and I am able to resolve all users.

Thanks a lot for your help!!

Free Windows Admin Tool Kit Click here and download it now
December 15th, 2011 9:53am

What you did is a common workaround but sometimes you will suddenly come across it but couldn't solve by playing around AAM. For those who get the same error when working on Target Application on Central Administration page should pay attention to FBA authentication in case you are using it. The error you would see in Event Viewer is "An exception occurred in AllUsers claim provider when calling SPClaimProvider.FillHierarchy(): The connection name 'fbaSQL' was not found in the applications configuration or the connection string is empty. (C:\inetpub/wwwroot\wss\VirtualDirectories\<port_number>\web.config line 453)

Make sure FBA is correctly configured especially connection string added in Web.Config of Central Administration web is valid, unless you would see People Picker not working.

Regards,
-T.s

February 1st, 2013 3:50am

Hi Thuan Soldier,

it 's correct, we have faced same issue. but it got resolved by checking the web.config of CE.

Regards,

Free Windows Admin Tool Kit Click here and download it now
January 20th, 2014 1:26pm

Go to Center Admin Web.config .Change the following setting it works for me.

Find membership tag


<membership defaultProvider="i">
          <providers>
              
              <add name="FBAMemberShipProvider" type="KBLMembership.OdbcMembershipProvider, KBLMembership, Version=1.0.0.0, Culture=neutral, PublicKeyToken=84ea470bcc6094aa" connectionStringName="FBAMemberShipProviderString" enablePasswordRetrieval="true" enablePasswordReset="true" requiresQuestionAndAnswer="true" writeExceptionsToEventLog="true" passwordFormat="Clear" applicationName="FBA" />
           
          </providers>
      </membership>


Replace with

<membership defaultProvider="FBAMemberShipProvider">
          <providers>
              
              <add name="FBAMemberShipProvider" type="KBLMembership.OdbcMembershipProvider, KBLMembership, Version=1.0.0.0, Culture=neutral, PublicKeyToken=84ea470bcc6094aa" connectionStringName="FBAMemberShipProviderString" enablePasswordRetrieval="true" enablePasswordReset="true" requiresQuestionAndAnswer="true" writeExceptionsToEventLog="true" passwordFormat="Clear" applicationName="FBA" enableSearchMethods="true"  />
            
          </providers>
      </membership>


April 10th, 2015 11:25am

Make sure that you are using configured access mapping for the webapplication/central administration website. If the url that you are using is not configured as alternate access mapping, this issue may happen.

A

Free Windows Admin Tool Kit Click here and download it now
May 3rd, 2015 3:21am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics