Nevermind, I finally got it to respond to the local account by switching to basic auth in IIS and disabling windows auth. Its been so long since I had to manage these settings I forgot what I was doing. Hope this helps anyone who is using a local account like me.

Thanks

Honestly i’ve never setup Central Admin to authenticate with FBA, and i’m not sure if it can be. And if you’re using the FBA Pack, it was never meant to work with Central Admin either, so I wouldn’t expect it to work either.

Wonderful article, I got to the last step and I wanted to use forms based auth for the Sharepoint Central Administration Site. I have this all running under a local user account (dev environment) and that’s the reason for needing to swap it over. Every time I log in with an admin account currently it can’t find it and drops me back into System Account, which can’t manage central administration. How would I go about setting Central Administration to do that?

Thanks

The error pretty much means that the membership provider can’t talk to the database – could be for a variety of reasons. It might be some misconfiguration in the config files. Usually it’s a SQL Server permission issue that causes the problem. You have to make sure that the SharePoint app pool user has DBO permissions on the membership database.

“A Membership Provider has not been configured correctly. Check the web.config settings for this web application.”

i recheck my web.config and nothing seems to be wrong

is there any solution o any help could resolve it?

by the way i do the same way in sharepoint2016 and its run without any problem.

I’ve run into the issue if it’s only FBA configured on the default zone, but don’t recall having issues if both FBA and AD are configured on that zone. But I guess it very well could be that the 3rd party connectors don’t take that into consideration. Unfortunately, if that’s the case, apart from trying to get the 3rd party provider to handle that scenario, you will probably have to do what you suggested and create a 2nd zone, with FBA activated solely on zone 2. This shouldn’t have a detrimental effect, and I’d say that in general this setup is probably more popular than your current setup (as user’s don’t get prompted to choose to login with windows or forms). The only issue is going to be that now there will be 2 url’s – one for windows login and one for forms. So all of one set of users is going to have to learn to use the new url.

We have a single zone SP2016 on prem setup, which has the FBA pack installed and it has been working solidly for a few years now.

However what we are now finding is that when 3rd party connectors are trying to connect to our sharepoint they are throwing up an error where its saying the credentials are incorrect.

I believe that this might be down to the 3rd party program not being able to decipher whether it is a Windows/Forms user.

Is there any way we can get around this within our setup? or do we need to create a new zone, switch off FBA on Zone1 and Activate it solely on Zone2. Would this have any detrimental effect on our user logon list?

really appreciate your help on this.

With no error logged, i’m not sure what would be causing it. Does it really give you all 0’s for the correlation id? I haven’t seen that before. Usually it’s a guid that can be searched for in the SharePoint logs to get the error details.

Hi Chris,

No errors in iis error log and no error in sharepoint log.

This is particularly happening with FBA configured site and on the Non FBA site it is working properly.

sorry something went wrong
an unexpected error has occurred.
technical details
correlation id : 0000000-0000-0000-00000000 go back to the site.

your help will be highly appreciated.

Thanks,
Faizan

There should be more details of the error, either in the event log if it’s an iis error, or the sharepoint log if it’s a sharepoint error. Hopefully that will give a clue as to what is wrong.