The connection name 'LocalSqlServer' was not found in the applications configuration or the connection string is empty.

Last post 11-07-2007 6:40 AM by jocker_wow. 6 replies.

Sort Posts:

  • Angry [:@] The connection name 'LocalSqlServer' was not found in the applications configuration or the connection string is empty.

    09-27-2007, 8:12 AM
    • Loading...
    • jocker_wow
    • Joined on 01-19-2007, 3:20 AM
    • Egypt
    • Posts 81

    Hi,

    I'm having a BIG problem, this is my 3rd day looking for answer !

    I'm trying to create a custom membership provider with MS SQL database 2005 but not the default ASPNETDB.
    I've changed the web.config to be as following:

    <connectionStrings>

    <
    add name="sqlConn" connectionString="Data Source=.;Integrated Security=True;Initial Catalog=ASPNETDB;"
    providerName="System.Data.SqlClient" />

    </
    connectionStrings> <system.web>

    <
    trace enabled="true" />
    <
    roleManager enabled="true" />
    <
    authentication mode="Forms" />

    <membership defaultProvider="MySqlProvider">
    <
    providers>

    <
    remove name="AspNetSqlProvider"/>
    <
    add name="MySqlProvider" connectionStringName="SqlConn"
    type="System.Web.Security.SqlMembershipProvider" applicationName="/" />

    </
    providers>
    </
    membership>

    But when I try to login to the site using the login control the following error occurs:

    Server Error in '/etest' Application.

    Configuration Error

    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 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


    Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.213

     It is clear that this is a prblem with my Machine.Config file - since I've "worked!" on this file for a while. But when I've checked the Machine.config file I've found the LocalSqlServer connection it is talking about! Tongue Tied .

    I'm lost and I dunno what to do, can anyone help?

    Here is the mahine.config in case if you need it:

    <connectionStrings>

    <add name="LocalSqlServer" connectionString="data source=.;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User Instance=true" providerName="System.Data.SqlClient" />

    </connectionStrings>

    <system.data>

    <DbProviderFactories>

    <add name="Odbc Data Provider" invariant="System.Data.Odbc" description=".Net Framework Data Provider for Odbc" type="System.Data.Odbc.OdbcFactory, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />

    <add name="OleDb Data Provider" invariant="System.Data.OleDb" description=".Net Framework Data Provider for OleDb" type="System.Data.OleDb.OleDbFactory, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />

    <add name="OracleClient Data Provider" invariant="System.Data.OracleClient" description=".Net Framework Data Provider for Oracle" type="System.Data.OracleClient.OracleClientFactory, System.Data.OracleClient, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />

    <add name="SqlClient Data Provider" invariant="System.Data.SqlClient" description=".Net Framework Data Provider for SqlServer" type="System.Data.SqlClient.SqlClientFactory, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />

    <add name="SQL Server CE Data Provider" invariant="Microsoft.SqlServerCe.Client" description=".NET Framework Data Provider for Microsoft SQL Server 2005 Mobile Edition" type="Microsoft.SqlServerCe.Client.SqlCeClientFactory, Microsoft.SqlServerCe.Client, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" />

    </DbProviderFactories>

    </system.data>

    <system.web>

    <processModel autoConfig="true" />

    <httpHandlers />

    <membership>

    <providers>

    <add name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" connectionStringName="LocalSqlServer" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="true" applicationName="/" requiresUniqueEmail="false" passwordFormat="Hashed" maxInvalidPasswordAttempts="5" minRequiredPasswordLength="7" minRequiredNonalphanumericCharacters="1" passwordAttemptWindow="10" passwordStrengthRegularExpression="" />

    </providers>

    </membership>

    <profile>

    <providers>

    <add name="AspNetSqlProfileProvider" connectionStringName="LocalSqlServer" applicationName="/" type="System.Web.Profile.SqlProfileProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />

    </providers>

    </profile>

    <roleManager>

    <providers>

    <add name="AspNetSqlRoleProvider" connectionStringName="LocalSqlServer" applicationName="/" type="System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />

    <add name="AspNetWindowsTokenRoleProvider" applicationName="/" type="System.Web.Security.WindowsTokenRoleProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />

    </providers>

    </roleManager>

    </system.web>

    Regards...
    M.Nagieb
    Jocker_Wow
  • Re: The connection name 'LocalSqlServer' was not found in the applications configuration or the connection string is empty.

    09-27-2007, 9:02 AM
    Answer
    • Loading...
    • pkellner
    • Joined on 11-12-2004, 10:42 AM
    • San Jose, California
    • Posts 3,440
    • Moderator
      TrustedFriends-MVPs

    I'm having a little trouble following your example, but let me post a very simple working example I use that basically does the same thing.  Hopefully this will keep you from a fourth day.

     

    <connectionStrings>  
       <add name="CMS"
         connectionString="Data Source=2.2.2.2;Initial Catalog=DBDev;Persist Security Info=True;User ID=db;Password=db1"
         providerName="System.Data.SqlClient"/>
    </connectionStrings>


     <system.web>

     <roleManager defaultProvider="SqlRoleProvider" enabled="true" cacheRolesInCookie="true" cookieName=".ASPROLES" cookieTimeout="30" cookiePath="/" cookieRequireSSL="false"   cookieSlidingExpiration="true" cookieProtection="All">
        <providers>
         <clear/>
         <add name="SqlRoleProvider" type="MyMembership.SqlRoleProvider" connectionStringName="CMS"
           applicationName="DB" writeExceptionsToEventLog="false"/>
        </providers>
       </roleManager>
       <membership defaultProvider="SqlMembershipProvider" userIsOnlineTimeWindow="15">
        <providers>
         <clear/>
         <add name="SqlMembershipProvider" type="MyMembership.SqlMembershipProvider" connectionStringName="CMS"
           applicationName="DB" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="false"
           requiresUniqueEmail="true" passwordFormat="Hashed" minRequiredNonalphanumericCharacters="0" writeExceptionsToEventLog="false"
           minRequiredPasswordLength="1" passwordStrengthRegularExpression="" passwordAttemptWindow="10" maxInvalidPasswordAttempts="8" />
        </providers>
       </membership>
      

    Peter Kellner
    http://73rdstreet.com and blogging at
    http://PeterKellner.net
    MVP, ASP.NET
  • Re: The connection name 'LocalSqlServer' was not found in the applications configuration or the connection string is empty.

    09-27-2007, 9:03 AM
    Answer
    • Loading...
    • FerVitale
    • Joined on 02-16-2007, 8:29 PM
    • Buenos Aires
    • Posts 184

     Hi there,

                  try overriding the roleManager node in the Web.config file; actually you are not setting your role custom provider. Here is an example

        <roleManager defaultProvider="MySqlRoleProvider" enabled="true" >
          <providers>
            <clear />
            <add name="MySqlRoleProvider" connectionStringName="SqlConn" type="System.Web.Security.SqlRoleProvider" applicationName="/" />
          </providers>
        </roleManager>


                  I hope it helps.

     

    Regards,

    Fernando 

  • Re: The connection name 'LocalSqlServer' was not found in the applications configuration or the connection string is empty.

    10-02-2007, 8:23 PM
    • Loading...
    • fhdesouza
    • Joined on 06-18-2007, 11:39 PM
    • Posts 18

    It works for me.

     

    Thanks Fernando!

  • Re: The connection name 'LocalSqlServer' was not found in the applications configuration or the connection string is empty.

    10-03-2007, 1:39 PM
    • Loading...
    • norchnou
    • Joined on 01-08-2007, 1:41 AM
    • Posts 232

    your problem was on a local machine or on the hosted server?

    I have the same kind of problem

  • Re: The connection name 'LocalSqlServer' was not found in the applications configuration or the connection string is empty.

    11-07-2007, 6:36 AM
    • Loading...
    • jocker_wow
    • Joined on 01-19-2007, 3:20 AM
    • Egypt
    • Posts 81

    pkellner,

    Thank you very much about your reply, which - unfortunalty- was not been tracked by me from the first place to fix my problem since I gaved up and stared building everything all over again!

    I wish I gave it another shoot and look for answers for my post! But thanks anyway for your reply Smile

     

    Regards...
    M.Nagieb
    Jocker_Wow
  • Re: The connection name 'LocalSqlServer' was not found in the applications configuration or the connection string is empty.

    11-07-2007, 6:40 AM
    • Loading...
    • jocker_wow
    • Joined on 01-19-2007, 3:20 AM
    • Egypt
    • Posts 81

    norchou,

    It was in the local machine, but I can assume that the same problem will happen in the host server too since the membership provider was not configured correctly.

    Regards...
    M.Nagieb
    Jocker_Wow
Page 1 of 1 (7 items)
Microsoft Communities
Page view counter