I have a basic WSS 3.0 site set up with an ASP.NET membership database and default forms login. There is no custom code or any customization on the entire site.
When I try to log in, I get 'unknown error', regardless of whether username/pass is correct or not. An iisreset fixes this for the rest of the day. When I check the site again in the morning, same unknown error.
Only error in /12/logs:
01/11/2010 12:00:39.11 w3wp.exe (0x02FC)
0x0D58 Windows SharePoint Services
General
8dzz High Exception Type: System.ArgumentNullException Exception Message: Value cannot be null. Parameter name: value
EDIT: Here's my membership/role providers in web.config:
<membership defaultProvider="FormsMember">
<providers>
<add
connectionStringName="ConnectionString"
enablePasswordRetrieval="false"
enablePasswordReset="true"
requiresQuestionAndAnswer="false"
applicationName="/"
requiresUniqueEmail="false"
passwordFormat="Hashed"
maxInvalidPasswordAttempts="5"
minRequiredPasswordLength="1"
minRequiredNonalphanumericCharacters="0"
passwordAttemptWindow="10"
passwordStrengthRegularExpression=""
name="FormsMember"
type="System.Web.Security.SqlMembershipProvider,System.Web,Version=2.0.0.0,Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" />
</providers>
</membership>
<!-- role provider -->
<roleManager enabled="true" defaultProvider="FBARole">
<providers>
<add
connectionStringName="ConnectionString"
applicationName="/"
name="FBARole"
type="System.Web.Security.SqlRoleProvider,System.Web,Version=2.0.0.0,Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" />
</providers>
</roleManager>
EDIT 2:
After making the suggested changes to web.config to view the error, here's what the site now says once the login fails:
Value cannot be null. Parameter name: value at System.String.EndsWith(String value, StringComparison comparisonType)
at Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.PostAuthenticateRequestHandler(Object oSender, EventArgs ea) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
EDIT 3:
I am still having this issue.