Any thoughts on why the People Picker would be trying to use Claims Based Authentication only when setting permissions for a secure store target application?

[EDIT: Further info]
This is in the error log:

02/10/2012 14:52:12.43 w3wp.exe (0x1304) 0x0E18
SharePoint Foundation Claims Authentication 8307 Critical
An exception occurred in All Users claim provider when calling SPClaimProvider.FillHierarchy():
The connection name 'LocalSqlServer' was not found in the applications configuration or the connection string is empty.
(C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Config\machine.config line 148).
084879fb-8d9b-4abd-be0c-aed55789601c

NB: I am not looking for instructions on how to configure claims based authentication. I am trying to figure out why People Picker is using claims based authentication and how to stop it!

Has the machine.config file mentioned been changed? You mention that the Auth Provider is windows. But you are in "Claims-mode" or "Classic-mode"?
–
Paul SchaefleinFeb 17 '12 at 16:54

Hi Paul, no changes have been made manually to the machine.config. The authentication provider for all three web applications is classic. I have updated the question to clarify that.
–
Mark van ProctorFeb 22 '12 at 0:52

4 Answers
4

Looks to me like there are some rogue configurations in your web.config. Did you ever set a custom membership/role provider manually or in IIS? Did you ever use FBA?

The error message you're getting looks like there is a custom membership provider set which uses a non-existing (or no longer existing) connectionstring for a local SQL server instance. So when you open up the people picker it tries to look up those members and fails.

I would check the web.config and verify the default providers and the people picker wildcards.

That was going to be my suggestion. If you had FBA configured at some point in time, it's possible that during the upgrade something got reverted there. Double check that the providers are setup correctly on the web applications. Also confirm the web.config for Central Administration and the STS services as they're all configured separately.
–
webdes03Dec 16 '12 at 13:28

Ivan, thank you for responding, but your response does not help me at all.I don't want to remove PeoplePicker. I want to use PeoplePicker with Classic mode authenticaiton.
–
Mark van ProctorSep 3 '12 at 2:24

well, I didn't suggest to remove PeoplePicker. I was mentioned "PeoplePicker entry in web.config" :) Did you try that? And please also check web config for STS as well.
–
Ivan PadabedSep 5 '12 at 17:50

Please don’t add just a link as answer to a question. If the link breaks, the answer you provided will not be useful for future visitors. Provide an answer of your own and use the link as reference. If needed, you can block quote the content from your link. More information is found in our help center, especially How do I write a good answer
–
Benny Skogberg♦Jul 15 '14 at 8:38