Re: Why do I get "name 'LocalSqlServer' was not found" when my app uses MySQL?

Tech-Archive recommends: Fix windows errors by optimizing your registry

That error is telling you that the SQL Server specified in your Provider

connectionStringName="LocalSqlServer"

can't be found.

If you're using MySQL as your database platform as a custom Provider,
you beed to have somthing akin to :

<add name="MySqlProfileProvider"

in web.config.

See :

http://www.codeproject.com/aspnet/MySQLMembershipProvider.asp

for sample access code to MySql using ASP.NET 2.0.



Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"webonomic" <webonomic@xxxxxxxxx> wrote in message
news:1150167336.760393.145950@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
"The connection name 'LocalSqlServer' was not found in the applications
configuration or the connection string is empty."

I get the error above. It tells me the error is in
Line 120: <profile>
Line 121: <providers>
Line 122: <add name="AspNetSqlProfileProvider"
connectionStringName="LocalSqlServer" applicationName="/"
type="System.Web.Profile.SqlProfileProvider, System.Web,
Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
Line 123: </providers>
Line 124: </profile>

in the machine.config.

Ok that's all fine and dandy, but why the heck is it even looking for
LocalSqlServer? I am using MySQL as the DB. I don't have a SQL
Express or other Microsoft DB in the app. There is nothing in my
Web.Config or my code (unless it was autogenerated without my
knowledge) that suggests I am using a SQL Express or MSSQL or MSAccess
DB.

So what is it about an Asp.net application to make it search for the
LocalSqlServer? How can I stop it from doing that?



.

Relevant Pages