Re: Logon failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Tue, 25 Mar 2008 16:32:20 -0700
Waldy (someone@xxxxxxxxxxxxx) writes:
I don't know if this is an IIS or SQL Server issue. I have an ASP.Net
web application that is set up with Anonymous access turned off and
Windows Authentication turned on. The SQL 2000 server (on another
machine) is set up for Windows only authentication. The application
won't logon to SQL Server, as I get the error above. I have searched
for this error and most of the articles suggest activating mixed mode
authentication. This is at a customer site however, and they want the
server left as it is. How do I make it work as intended.
As far as I understand, best practice with IIS is to use an SQL
login with SQL Server. But an IIS forum surely has greater expertise
on the issue.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- References:
- Prev by Date: Re: Stored Proc security
- Next by Date: Creating new user default to DB_owner role
- Previous by thread: Logon failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection
- Next by thread: Creating new user default to DB_owner role
- Index(es):
Relevant Pages
|
|
