Microsoft Access Providers to Replace the Built-In SQL Server Providers

turben_1 · March 13th, 2010, 02:55 PM

Using the Microsoft Access Providers to Replace the Built-In SQL Server Providers
When I uploaded a membership login web site to my web site, I get an error when I go to the login.aspx page.
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: The connection name 'LocalSqlServer' was not found in the applications configuration or the connection string is empty.
Source Error:

Line 163: <roleManager>
Line 164: <providers>
Line 165: <add name="AspNetSqlRoleProvider" connectionStringName="LocalSqlServer" applicationName="/" type="System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
Line 166: <add name="AspNetWindowsTokenRoleProvider" applicationName="/" type="System.Web.Security.WindowsTokenRoleProvider , System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
Line 167: </providers>

Source File: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Conf ig\machine.config Line: 165
________________________________________
Version Information: Microsoft .NET Framework Version:2.0.50727.3082; ASP.NET Version:2.0.50727.3082

Can you help?

Imar · March 14th, 2010, 05:57 AM

Hi turben_1,

As I said in my personal message, you need to supply details. A lot. In particular, I asked for the following:

What OS are you using? Which version of IIS is being used? What's the physical file / folder structure of your web site. What's the virtual structure? How did you configure IIS? Are you using sub folders to host your site and if so, did you mark them as Virtual Folders / Application in IIS? How exactly do your config files look like? What did you change with regard to membership and profile settings?

In other words, it's impossible to say something useful based on this error message alone. Somewhere, somehow, someone tries to find a LocalSqlServer config setting which isn't there. Without details, it's impossible to tell what the problem is.

Cheers,

Imar