Why is my web site generating App_Data folder?

[Hugo Flores]

I created a Web Application Project in VS 2005.
The site is working fine in the development computer.
Then I transfer all my files and dll to the production computer.
I have a login form. If I try to log in, the production computer
automatically generates an App_Data folder (the development computer
doesn't have this folder at all) and it also generates an error saying
that I don't have SQL Server 2005, which of course I don't, I'm not
using it in any way.

The error I get is:
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (provider: SQL Network Interfaces, error: 26 - Error
Locating Server/Instance Specified)

So my questions are, why does the production site generates the
App_Data folder and why does the site looks for SQL Server 2005?

Thanks

[Ken Cox [Microsoft MVP]]

Hi Hugo,

Is there anything in your web.config or in your code that uses Profiles,
Roles, or Membership? ASP.NET will try to create the ASPNETDB.mdf database
for you when it encounters code that requires it. That database goes into
the App_Data folder.

http://msdn2.microsoft.com/en-us/lib...embership.aspx

Ken
Microsoft MVP [ASP.NET]

"Hugo Flores" <hu*********@ge.comwrote in message
news:11*********************@m79g2000cwm.googlegro ups.com...

>I created a Web Application Project in VS 2005.
The site is working fine in the development computer.
Then I transfer all my files and dll to the production computer.
I have a login form. If I try to log in, the production computer
automatically generates an App_Data folder (the development computer
doesn't have this folder at all) and it also generates an error saying
that I don't have SQL Server 2005, which of course I don't, I'm not
using it in any way.

The error I get is:
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (provider: SQL Network Interfaces, error: 26 - Error
Locating Server/Instance Specified)

So my questions are, why does the production site generates the
App_Data folder and why does the site looks for SQL Server 2005?

Thanks

[Hugo Flores]

No, I'm not using profiles at all, nothing on my web.config that has
anything to do with that.
Now, I've also checked that this only happens if my login fails.
I also have the new Login control, would that be causing the problem?
Do you think if I remove the Login control and use my own login form,
would solve the problem?
Ken Cox [Microsoft MVP] wrote:

Hi Hugo,

Is there anything in your web.config or in your code that uses Profiles,
Roles, or Membership? ASP.NET will try to create the ASPNETDB.mdf database
for you when it encounters code that requires it. That database goes into
the App_Data folder.

http://msdn2.microsoft.com/en-us/lib...embership.aspx

Ken
Microsoft MVP [ASP.NET]

"Hugo Flores" <hu*********@ge.comwrote in message
news:11*********************@m79g2000cwm.googlegro ups.com...

I created a Web Application Project in VS 2005.
The site is working fine in the development computer.
Then I transfer all my files and dll to the production computer.
I have a login form. If I try to log in, the production computer
automatically generates an App_Data folder (the development computer
doesn't have this folder at all) and it also generates an error saying
that I don't have SQL Server 2005, which of course I don't, I'm not
using it in any way.

The error I get is:
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (provider: SQL Network Interfaces, error: 26 - Error
Locating Server/Instance Specified)

So my questions are, why does the production site generates the
App_Data folder and why does the site looks for SQL Server 2005?

Thanks

[Ken Cox [Microsoft MVP]]

Hi Hugo,

Yes, the Login control is almost certainly causing ASP.NET to implement the
Membership system:

"If you use login controls, they will automatically use the membership
system to validate a user."

http://msdn2.microsoft.com/en-us/library/yh26yfzy.aspx

Try implementing your own and see what happens?

Ken
Microsoft MVP [ASP.NET]

"Hugo Flores" <hu*********@ge.comwrote in message
news:11**********************@p79g2000cwp.googlegr oups.com...

No, I'm not using profiles at all, nothing on my web.config that has
anything to do with that.
Now, I've also checked that this only happens if my login fails.
I also have the new Login control, would that be causing the problem?
Do you think if I remove the Login control and use my own login form,
would solve the problem?
Ken Cox [Microsoft MVP] wrote:

>Hi Hugo,

Is there anything in your web.config or in your code that uses Profiles,
Roles, or Membership? ASP.NET will try to create the ASPNETDB.mdf
database
for you when it encounters code that requires it. That database goes into
the App_Data folder.

http://msdn2.microsoft.com/en-us/lib...embership.aspx

Ken
Microsoft MVP [ASP.NET]

"Hugo Flores" <hu*********@ge.comwrote in message
news:11*********************@m79g2000cwm.googlegr oups.com...

>I created a Web Application Project in VS 2005.
The site is working fine in the development computer.
Then I transfer all my files and dll to the production computer.
I have a login form. If I try to log in, the production computer
automatically generates an App_Data folder (the development computer
doesn't have this folder at all) and it also generates an error saying
that I don't have SQL Server 2005, which of course I don't, I'm not
using it in any way.

The error I get is:
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (provider: SQL Network Interfaces, error: 26 - Error
Locating Server/Instance Specified)

So my questions are, why does the production site generates the
App_Data folder and why does the site looks for SQL Server 2005?

Thanks

[Hugo Flores]

Yep,

Implementing my own login, solved the problem, thank you very much

Ken Cox [Microsoft MVP] wrote:

Hi Hugo,

Yes, the Login control is almost certainly causing ASP.NET to implement the
Membership system:

"If you use login controls, they will automatically use the membership
system to validate a user."

http://msdn2.microsoft.com/en-us/library/yh26yfzy.aspx

Try implementing your own and see what happens?

Ken
Microsoft MVP [ASP.NET]

"Hugo Flores" <hu*********@ge.comwrote in message
news:11**********************@p79g2000cwp.googlegr oups.com...

No, I'm not using profiles at all, nothing on my web.config that has
anything to do with that.
Now, I've also checked that this only happens if my login fails.
I also have the new Login control, would that be causing the problem?
Do you think if I remove the Login control and use my own login form,
would solve the problem?
Ken Cox [Microsoft MVP] wrote:

Hi Hugo,

Is there anything in your web.config or in your code that uses Profiles,
Roles, or Membership? ASP.NET will try to create the ASPNETDB.mdf
database
for you when it encounters code that requires it. That database goes into
the App_Data folder.

http://msdn2.microsoft.com/en-us/lib...embership.aspx

Ken
Microsoft MVP [ASP.NET]

"Hugo Flores" <hu*********@ge.comwrote in message
news:11*********************@m79g2000cwm.googlegro ups.com...
I created a Web Application Project in VS 2005.
The site is working fine in the development computer.
Then I transfer all my files and dll to the production computer.
I have a login form. If I try to log in, the production computer
automatically generates an App_Data folder (the development computer
doesn't have this folder at all) and it also generates an error saying
that I don't have SQL Server 2005, which of course I don't, I'm not
using it in any way.

The error I get is:
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (provider: SQL Network Interfaces, error: 26 - Error
Locating Server/Instance Specified)

So my questions are, why does the production site generates the
App_Data folder and why does the site looks for SQL Server 2005?

Thanks