Proposed as answer by howitzer1972 Friday, January 18, 2013 9:40 PM Unproposed as answer by howitzer1972 Friday, January 18, 2013 9:42 PM Wednesday, May 02, 2012 1:41 AM Reply | Quote During the restore, we created a new site but I think the fault was that we made the authentication "claims based". All contents are copyright of their authors. Thursday, July 14, 2011 1:43 PM Reply | Quote 0 Sign in to vote I had the same issue, but it wasn't with MySite, but with the Managed Metadata Term Store. Source
Simply add the present URL as an Alternate Access Mapping for the Central Admin web application and all should be good. How to deal with a DM who controls us with powerful NPCs? Are you able to resolve users in the main site? Share a link to this question via email, Google+, Twitter, or Facebook. https://thesharepointfarm.com/2011/03/sharepoint-error-an-error-has-occured-in-the-claim-providers-configured-for-this-site-collection-easy-fix/
More information is found in our help center, especially How do I write a good answer –Benny Skogberg♦ Jul 15 '14 at 8:38 add a comment| Your Answer draft saved Monday, October 04, 2010 2:57 PM Reply | Quote 2 Sign in to vote Hi I had exactly the same problem - I was trying to setup a new Secure Store If we load the people picker to assign permissions in our central administration, it displays the classic mode view and works just fine. Monday, May 17, 2010 7:51 PM Reply | Quote 0 Sign in to vote We did not do a migration just a fresh install.
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. Edit public URLs 7. How do i fix this or how do I change the authentication method? http://sharepoint.stackexchange.com/questions/28979/people-picker-attempts-to-use-claim-based-authentication-but-the-web-application This workbook cannot be opened because it is not stored in an Excel Services Application trusted location One of our user has opened a ticket with us by mentioning that he
Anonymous June 6, 2012 at 4:33 pm Reply Thanks!! Did you try that out? Share this:TwitterFacebookLinkedInRedditGoogleMoreEmailPrintPinterestTumblrLike this:Like Loading... No trackbacks yet.
I would start by deleting the UPS and then running the Configuration Wizard again to automatically provision it.SharePoint Architect || Microsoft MVP || My Blog Sunday, May 16, 2010 6:38 PM https://social.technet.microsoft.com/Forums/office/en-US/e126e1fc-4fc9-4623-aa76-d52204224df1/claim-provider-error?forum=sharepointadminprevious This is a much different problem area than what I thought you were saying the whole time. Except me In my central admin there are two access control mappings defined for the CA web app 1. I had added the AAM just for the web site and NOT the Central Admin site.
It didn't work at first when I set up the full FQDN and then I realised why. Browse other questions tagged authentication claims-based-auth people-picker windows-authentication secure-store or ask your own question. You can even send a secure international fax — just include t… eFax Advertise Here 856 members asked questions and received personalized solutions in the past 7 days. LEARN MORE Suggested Solutions Title # Comments Views Activity Conditional Formatting 4 16 108d How to attached SharePoint 2013 Picture Library to other site? 10 43 77d Sharepoint 2013 returns HTTP
When I open the address Book I get the error "an error has occurred in the claim providers configured from this site collection. Or have you not attempted to set up claims at all and just got an error with the wrods "claim providers" in it? After I switched to the right AAM, the error went away. Even after deleting and recreating the Central Admin site.
Must Read: 50 Important Queries In SQL Server C# Corner Contribute An Article A Blog A News A Video A Link An Interview Question Ask a Question TECHNOLOGIES .NET Chapters An error has occurred in the claim providers confi... I am not very knowledgeble with sharepoint and I have done an install to try and get to grips with it all.
We are using windows authentication and neva-eva configure the claims authentication but today we faced this strange error: An error has occurred in the claim providers configured from this site collection. MSDNStudent Knows not much! I would be more than happy to help you as well as resolves your issues. This error is not stopping me from being able to continue so ill investigate it more at a later date.
So, trying creating an AAM for your site. Did you ever set a custom membership/role provider manually or in IIS? What uses do you see in the Read Permissions box that has the red italics? That's why you see the "Claims Provider" errors.
I wrote a book and am getting offers for to publish. It seems this error is very much related to the AAM of central administration. Share this post! I am having this same issue.