Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 260
  • Last Modified:

ASP Login

I have a new ASP.Net 2.0 website I developed and am using the default ASPNETDB.MDF under the APP_DATA folder to store user name and passwords that I create using the Web Site Administration Tool.

I am trying to deploy this Web Site on a separate Windows 2003 server box and have copied the contents of my Web Project Folder into c:\Inetpub\wwwroot. So the APP_DATA is now a sub-folder of wwwroot.

When I run the Web Site in a browser it will not accept any logins that I had created on the development server, acts as if there are no user's setup. I have installed SQL Server Express on the production server but still no luck. Why?
0
michouis
Asked:
michouis
  • 2
  • 2
1 Solution
 
silemoneCommented:
in the webconfig or where ever your connection string is for your db, is it pointing to the right db server?
0
 
guru_samiCommented:
As mentioned in post above....first thing to check is it is pointing to correct database....
There could be may other reasons...
check this:
http://www.codeproject.com/KB/aspnet/LoginControlError.aspx
0
 
michouisAuthor Commented:
There is no connection string defined for this Express database file in my webconfig. I used the built-in ASP Login control and selected the default SQL Express provider. Then I setup user's using the Website Admin tool. Works great on the development server. Does not work on the production server. The ASPNET.MDF file is in C:\Inetpub\wwwroot\App_Data folder. Like i said, i installed Express SQL Server 2005 on the production box. Why is it not working?? I am typing the login/password values manually, same as i do on the development server... Must be some setting in SQL Express on the production server. Also, when you install Express SQL Server there is no Enterprise Managment tool included. How are you supposed to create any tables?
0
 
guru_samiCommented:
Since you don't have any setting in your web.config...the default settings are used from your machine.config.
Check the machine.config in your dev and prod machines ...look the connectionStrings section....
you will get better idea...

Try this:
In web.config.... add membership provider section as it is in the link in my previous post....
0
 
michouisAuthor Commented:
I have solved this by adding a customized provider to use our main SQL Server 2005 database... thanks for your clues..
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now