Error with impersonation: Login failed for user '(null)'. Reason: Not associated with a trusted SQL

  • Thread starter Thread starter Mark
  • Start date Start date
M

Mark

We are using impersonation so that a user on our domain will login into our
SQL Server using their own domain login and/or associated domain groups. To
do this, we've added:

<authentication mode="Windows" />
<identity impersonate="true"/>

to our web.config file. In IIS, annonymous access is unchecked, digest
authentication is unchecked, basic authentication is unchecked, and
Integrated Windows Authentication is checked.

The problem: This works like a charm on my local pc running IIS and
connecting to SQL Server A, but the momemnt I load it up on our development
web site with the same web.config file and same IIS settings, the connection
to SQL Server A bombs with the error message:
"Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection." Note that the rest of the site that does not use a
connection to SQL Server works just fine.

Any ideas?? Thanks in advance for your help! We appreciate it.

Mark
(e-mail address removed)
 
Hello, Mark!
We are using impersonation so that a user on our domain will login into our
SQL Server using their own domain login and/or associated domain groups. To
do this, we've added:

<authentication mode="Windows" />
<identity impersonate="true"/>

to our web.config file. In IIS, annonymous access is unchecked, digest
authentication is unchecked, basic authentication is unchecked, and
Integrated Windows Authentication is checked.

The problem: This works like a charm on my local pc running IIS and
connecting to SQL Server A, but the momemnt I load it up on our development
web site with the same web.config file and same IIS settings, the connection
to SQL Server A bombs with the error message:
"Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection." Note that the rest of the site that does not use a
connection to SQL Server works just fine.

Any ideas?? Thanks in advance for your help! We appreciate it.
Click to expand...


Use the Integrated Security keyword for Connection String, set to a value of
SSPI, to specify Windows Authentication
 
Back
Top