Home/ Questions/Q 84837
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T21:59:40+00:00

I just installed an application on a win2003 server and I’m getting this error:

  • 0

I just installed an application on a win2003 server and I’m getting this error:

Line 149:    <roleManager> Line 150:      <providers> Line 151:        <add name='AspNetSqlRoleProvider' connectionStringName='LocalSqlServer' applicationName='/' type='System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' /> Line 152:        <add name='AspNetWindowsTokenRoleProvider' applicationName='/' type='System.Web.Security.WindowsTokenRoleProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' /> Line 153:      </providers>   Source File: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Config\machine.config    Line: 151

I’m using a RoleProvider and it’s properly configured in web.config (it works on other servers) as follows:

<membership defaultProvider='AdminMembershipProvider'>   <providers>     <clear/>     <add name='AdminMembershipProvider' connectionStringName='SiteSqlServer' type='MyApp.Providers.AdminMembershipProvider' applicationName='MyApp' writeExceptionsToEventLog='false' enablePasswordRetrieval='false' enablePasswordReset='false' requiresQuestionAndAnswer='false' requiresUniqueEmail='false' PasswordFormat='Clear' MinRequiredNonAlphanumericCharacters='1' MinRequiredPasswordLength='8' MaxInvalidPasswordAttempts='5' PasswordAttemptWindow='10'>     </add>   </providers> </membership> <roleManager enabled='true' defaultProvider='AdminRoleProvider' cacheRolesInCookie='true'>   <providers>     <add name='AdminRoleProvider' type='MyApp.Providers.AdminRoleProvider' writeExceptionsToEventLog='true'/>   </providers> </roleManager>

Any hint on why it’s looking for configuration on machine.config instead of web.config? How can I debug this?

Thank you.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Indeed it read machine.config first, then your web.config which supercedes machine.config. But in some cases the values in the web.config are appended or included in a list so it can get a little hard to follow.

    But perusing the machine.config on a working server might shed some more light for you.

    • 0