Database Not Accessible During Deployment on IIS 7

Question

4.50/5 (2 votes)

See more:

hello guys... I read some articles to deploy my web site on IIS 7 which I followed exactly I was told to. Now simple aspx pages are deployed successfuly but web applications that have database with it, are not deployed as expected.
For example, I have stored my user name and password in sql server but upon entering these in text box, the web page does not directs me to the next page, instead I am redirected to the same page. What is this problem and how can I solve it..?? thnx

Posted 9-Mar-11 6:28am

AmbiguousName

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

fjdiewornncalwe · Answer 1 · 2011-03-09T09:15:00

Solution 1

You likely have the connection string for the database located in your web.config file.
Check and make sure that connection string works and that you can hit that database server from your web server. If that isn't the issue, you should have an exception of some kind being generated. Provide us information regarding this exception and we can help you further.

Posted 9-Mar-11 9:15am

fjdiewornncalwe

Comments

AmbiguousName 9-Mar-11 16:07pm

NO..actually in the PageLoad() event of the LoginForm.aspx, I am creating new SqlConnection() with the connection string as argument. Then I retrieve the userID,Pass using SqlCommand(), do the comparisons and get redirected to next page. But this is in developent envirnoment using VS 2008. Now when I deploy same application. it does not do the required job.

fjdiewornncalwe 10-Mar-11 6:49am

Sorry, I couldn't get back to you yesterday.
The point is from me is that the connection string itself that you are using in PageLoad() is probably not working. You can't connect to the database to get the user's specific username and such until you connect successfully and I suspect that this connection string is invalid. The difference may be that in your development environment your connection string is using your login credentials to gain access to the database which is ok. Once the application is deployed on a server, the application will run under a system account so the connection string credentials are now invalid for the given database, if you can even hit that from the server to start with.

Manfred Rudolf Bihy 9-Mar-11 16:48pm

OP sounds sort of clueless. 5+

fjdiewornncalwe 10-Mar-11 6:50am

In this case I get the impression that he is quite green to this so I'm putting on my "patient" hat and see where we go from here. Cheers and Thanks.

Manfred Rudolf Bihy 10-Mar-11 7:39am

I think I'll have to go and grab one of those "patient hats" myself. Do you know a good source? :)

fjdiewornncalwe 10-Mar-11 13:09pm

You could try google.... http://www.google.com/images?hl=en&rlz=&=&q=patient+hat&um=1&ie=UTF-8&source=og&sa=N&tab=wi&biw=1182&bih=792

Manfred Rudolf Bihy · Answer 2 · 2011-03-09T10:45:00

Solution 2

If you can't remotely debug your application on your IIS's server, maybe because of firewall restrictions, the second best would be to liberally sprinkle your code with logging statements. Since you seem to have problems with the DB stuff start inserting the first logging statements there. Remember that good exception handling is essential.
Maybe your DBMS isn't reachable from the server your IIS is running on. If you have remote access to the server with the IIS on it run this command from there: telnet DBMS.Server.name 1433 (if your SQL Server is listening on that port). If telnet is able to connect then a firewall is not an issue and you'll have to dig into your logfiles. If you are not yet using a logging framweork consider Log4Net[^].

Hope this gives you some ideas.

Posted 9-Mar-11 10:45am

Manfred Rudolf Bihy

Updated 9-Mar-11 10:49am

v3

Comments

AmbiguousName 10-Mar-11 3:30am

well I am very new to ASP.NET. I am not bad with DB stuff. My IIS os on the same computer onwhich I am developing web site (I mean I am deploying web site on local IIS or localhost). Since I am very much new to it, thats why probably I am unable to explain the problem.

fjdiewornncalwe 10-Mar-11 6:53am

This is exactly what my reply to you is based on. When deployed to IIS the application will not necessarily run under the same account as it will when you run it through Studio itself, so the database configured in your connection string (in your PageLoad method) is likely not able to hit the database. This is why the preferred way to deal with connection strings is to store them in the web.config file so that they can be changed and tinkered with without having to recompile the application each time.

fjdiewornncalwe 10-Mar-11 6:54am

+5 for adding logging bit. I didn't offhand think of that this time. I use log4net in pretty much all my web applications and use the liberal logging to know what's going on as well. Cheers, Manfred.