I am having problems setting up the AspNetSqlMembershipProvider for the Authentication Provider in SharePoint 2007. I have configured the AspNetSqlMembershipProvider in both the Sharepoint web.config and Central Admin web.config. The Site Collection Administrators page on Central Admin site works, it retrieves a list of users. The Sharepoint site returns the following message no matter what user I try: The server could not sign you in. Make sure your user name and password are correct, and then try again. Also, every time I try to log in I receive the following message in the event log:-------------------------------------------------------Event Type: InformationEvent Source: ASP.NET 2.0.50727.0Event Category: Web Event Event ID: 1315Date: 3/3/2008Time: 9:11:22 AMUser: N/AComputer: SERVERDescription:Event code: 4006 Event message: Membership credential verification failed. Event time: 3/3/2008 9:11:22 AM Event time (UTC): 3/3/2008 3:11:22 PM Event ID: f4bd131d67c6407a89036b656638d86b Event sequence: 2 Event occurrence: 1 Event detail code: 0 Application information: Application domain: /LM/W3SVC/808052994/Root-1-128490306330781250 Trust level: WSS_Minimal Application Virtual Path: / Application Path: C:\Inetpub\wwwroot\wss\VirtualDirectories\4488\ Machine name: SERVERProcess information: Process ID: 1380 Process name: w3wp.exe Account name: NT AUTHORITY\NETWORK SERVICE Request information: Request URL: http://server:4488/_layouts/login.aspx?ReturnUrl=Membership credential verification failed.f Request path: /_layouts/login.aspx User host address: User: Is authenticated: False Authentication Type: Thread account name: SERVER\IUSR_SERVER Name to authenticate: S00091205 Custom event details: For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.-------------------------------------------------------Here is the membership portion of web.config: <membership> <providers> <clear /> <add connectionStringName="BanPort" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="true" applicationName="/" requiresUniqueEmail="false" passwordFormat="Hashed" maxInvalidPasswordAttempts="5" minRequiredPasswordLength="7" minRequiredNonalphanumericCharacters="1" passwordAttemptWindow="10" passwordStrengthRegularExpression="" name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/> </providers>I know about the "applicationName" property. I checked the database, there is only 1 application and it's path is "/".

I have this issue as well. Did you figure out how to resolve it?I tried this technique with no success:http://forums.asp.net/t/1084044.aspxOthers have reported success though. I checked and both my applicationname property and aspnet application name property match.Add it to the stack of issues. *sigh

We had this issue with the ADMembershipProvider and discovered the cause was another account with the same UPN in a different OU. In other words, it seems the Provider throws this error if it detects more than one account with the name it's trying to authenticate. We can easily create a copy of the same provider but authenticating at the OU level rather than at the root level.