How Do I Access Published Website In Iis6.0

Question

0.00/5 (No votes)

See more:

I am using Microsoft dynamic Nav 2009 R2.. I have published my web application in IIS 6.0. Now when i attempt to access my web application from iis..i get an error " The login failed when connecting to SQL Server KRISHAB-PC. " is it that something is missed in web.config or during configuration of iis??? ny help..

Posted 11-Jan-14 17:52pm

Codes DeCodes

Add a Solution

1 solution

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)

Dave Kreskowiak · Answer 1 · 2014-01-11T18:40:00

It sounds as though you didn't change your connection string when you published the website. I also suspect your connection string uses a Trusted Connection instead of a username and password.

When published, your website code runs as the ASP.NET service account by default, no longer as you when you run it from inside Visual Studio.

You have two options.

Either change the account that the website is using to run your code to an account trusted by the SQL Server or change your connection string to use a username and password specified account instead of Trusted Connection.

What is not optional is that you have to do some research and teach yourself about IIS, Windows and SQL Server security models, along with what impacts they have on your connection string.