We have a web application that connects fine to Sql on one server but not on
another.

A console application was created and run from the same server that house
IIS. This console program can access and see the tables fine.

Both the Web Server and console program are using the same connection string
with the same user and password.

What would cause the Web Server not to connect?

Thanks,

Tom

Are both of these websites the same identical website, or are they
running two different code bases that each connect to the same
website? That wasn't entirely clear. If both webservers are running
the identical websites (the same codebase) then I would be looking at
the IIS configuration on the second server as that sounds like the
only difference.

-Eric Isaacs

This is the same website that is accessing 2 different SQL Servers
(different machines).

So codebase is the same.

Thanks,

Tom

"Eric Isaacs" <eisaacs (AT) gmail (DOT) com> wrote

Please post the error message. If you are using Windows Authentication,
check to ensure the account has access to the second SQL Server.

--
Hope this helps.

Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/

"tshad" <tfs (AT) dslextreme (DOT) com> wrote

"Dan Guzman" <guzmanda (AT) nospam-online (DOT) sbcglobal.net> wrote

Unfortunately, don't have the message.

It is on another system that we don't have access to and the only message we
have is from the application itself.

It is they that put the Console program on there system that was able to
connect and see the table.

They are the ones setting up the permissions.

We are just trying to get them things to try to solve the problem.

It works fine in our shop.

Thanks,

Tom

The console app probably uses a different security context than the IIS. In
lieu of an error message, you can try a a Profiler trace of login failed
events. Ensure IIS has the needed database server access.

--
Hope this helps.

Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/

"Dan Guzman" <guzmanda (AT) nospam-online (DOT) sbcglobal.net> wrote


Thanks,

Tom

It depends on your web.config and site settings. For example, you can
specify Impersonate=True and specify a domain account that has the needed
database access as the anonymous user. This can also be done at the app
pool level.

If you have more questions related to the IIS specific settings, post to an
IIS group.

--
Hope this helps.

Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/