Re: Problem deploying forms authorization

Dear Steven,
I was away for a couple days so I'm sorry for the delay. I did find some old posts of yours which indicated to me that the problem is with the Membership provider. My login screen uses the .net login control and I think the application is looking for the default sql membership provider. Its apparently looking for another instance of SQL server and cannot find it. The error seems to be comming from the Framework and not my code.

Even though I don't use the provider membership tables, I installed the sql membership provider to my database using the tool from the command prompt, and then recopied the database to my production server. Now I do not get the same error. I get a new one: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'

I made the NT Authority\Network Service a member of all the asp_net roles which were added as a result of the membership provider, but I still get the same message. Again when I look at the SQL profiler, my sql statements are being run without problems. I believe I'm having problems with permissions for the membership provider.

Below are the error message and web.config file:

*****************
Error Message:
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[SqlException (0x80131904): Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.]
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +437

System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82

System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
System.Web.DataAccess.SqlConnectionHolder.Open(HttpContext context, Boolean revertImpersonate) +84
System.Web.DataAccess.SqlConnectionHelper.GetConnection(String connectionString, Boolean revertImpersonation) +197
System.Web.Security.SqlRoleProvider.GetRolesForUser(String username) +771
System.Web.Security.RolePrincipal.IsInRole(String role) +272

System.Web.Configuration.AuthorizationRule.IsTheUserInAnyRole(StringCollection roles, IPrincipal principal) +120
System.Web.Configuration.AuthorizationRule.IsUserAllowed(IPrincipal user, String verb) +300

System.Web.Configuration.AuthorizationRuleCollection.IsUserAllowed(IPrincipal user, String verb) +191
System.Web.Security.UrlAuthorizationModule.OnEnter(Object source, EventArgs eventArgs) +3394990

System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

*****************

Web Config
*******************

<?xml version="1.0"?>
<!--
Note: As an alternative to hand editing this file you can use the
web admin tool to configure settings for your application. Use
the Website->Asp.Net Configuration option in Visual Studio.
A full list of settings and comments can be found in
machine.config.comments usually located in
\Windows\Microsoft.Net\Framework\v2.x\Config
-->
<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0";>
<appSettings/>
<connectionStrings>
<add name="FishConnectionString1" connectionString="Data Source=myserver;Initial Catalog=Fish;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="FishConnectionString" connectionString="Data Source=myserver;Initial Catalog==Fish;Integrated Security=True"
providerName="System.Data.SqlClient" />
</connectionStrings>
<system.web>
<!--
Set compilation debug="true" to insert debugging
symbols into the compiled page. Because this
affects performance, set this value to true only
during development.

Visual Basic options:
Set strict="true" to disallow all data type conversions
where data loss can occur.
Set explicit="true" to force declaration of all variables.
-->
<authorization>
<allow roles="admin"/>
<allow roles="manager"/>
<allow roles="user"/>
<deny users="?" />

</authorization>
<identity impersonate="true"/>

<!--<roleManager enabled="true"/>-->
<roleManager enabled="true">

<providers>

<remove name="AspNetSqlRoleProvider" />

<add connectionStringName="FishConnectionString1" applicationName="/"

name="AspNetSqlRoleProvider" type="System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />

<remove name="AspNetWindowsTokenRoleProvider" />

</providers>

</roleManager>
<membership>

<providers>

<remove name="AspNetSqlMembershipProvider" />

<add connectionStringName="FishConnectionString1" 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>

</membership>
<compilation debug="true" strict="false" explicit="true"/>
<pages>
<namespaces>
<clear/>
<add namespace="System"/>
<add namespace="System.Collections"/>
<add namespace="System.Collections.Specialized"/>
<add namespace="System.Configuration"/>
<add namespace="System.Text"/>
<add namespace="System.Text.RegularExpressions"/>
<add namespace="System.Web"/>
<add namespace="System.Web.Caching"/>
<add namespace="System.Web.SessionState"/>
<add namespace="System.Web.Security"/>
<add namespace="System.Web.Profile"/>
<add namespace="System.Web.UI"/>
<add namespace="System.Web.UI.WebControls"/>
<add namespace="System.Web.UI.WebControls.WebParts"/>
<add namespace="System.Web.UI.HtmlControls"/>
</namespaces>
</pages>
<webParts>

<personalization defaultProvider="AspNetSqlPersonalizationProvider">

<providers>

<remove name="AspNetSqlPersonalizationProvider" />

<add name="AspNetSqlPersonalizationProvider"


type="System.Web.UI.WebControls.WebParts.SqlPersonalizationProvider"

connectionStringName="FishConnectionString1"

applicationName="/" />

</providers>

</personalization>

</webParts>



<!--
The <authentication> section enables configuration
of the security authentication mode used by
ASP.NET to identify an incoming user.
-->
<authentication mode="Forms">
<forms loginUrl="Logon.aspx" name=".ASPXFORMSAUTH">
</forms>


</authentication>


<!--
The <customErrors> section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.

<customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
<error statusCode="403" redirect="NoAccess.htm" />
<error statusCode="404" redirect="FileNotFound.htm" />
</customErrors>
-->

<customErrors mode="Off"/>

</system.web>
</configuration>


Steven Cheng[MSFT] wrote:
Hi Haim,

Any progress on this issue? Since we're continouslly monitoring this issue, please feel free to post here if there is anything we can help.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no rights.


.