Connection error

Question

question

chandru asked Nov 10, '10

Connection error

I have got this error when trying to connect with SQL Server 2000 from ASP.NET 2.0 using Windows Authentication. >Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. The Sql server is in Mixed Mode and it is running on Windows Server 2000. Connection String used : "Data Source=server;Initial Catalog=db;Integrated Security=SSPI" any idea? Thanks in Advance Chadru

sql-server-2000 connection connection-string

2

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

chandru commented · Nov 11, 2010 at 01:15 AM

Thanks Kev, Matt and Qleg. I just started using SQL for the time being. Meanwhile, I am trying to sort out the issues as directed by you all. Will get back to you with my solutions. Thanks again.

0 ·

Willjoe2442 chandru commented · Aug 01, 2022 at 08:25 AM

How do I fix the SQL connection errors?

For more information, see Viewing the SQL Server error log.

Step 1：Verify that the instance is running.

Step 2: Verify that the SQL Server Browser service is running.

Step 3: Verify the server name in the connection string.

Step 4: Verify the aliases on the client machines.

Step 5: Verify the firewall configuration.

Hope this helps

0 ·

Answer 1 · 2010-11-10T01:19:22Z

Kev Riley answered Nov 10, '10

You are trying to connect using windows authentication, but the account you are using is not allowed.

9

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Kev Riley ♦♦ commented · Nov 10, 2010 at 01:43 AM

But what is the application running under when it tries to connect

1 ·

chandru commented · Nov 10, 2010 at 01:40 AM

Kev, but i am able to connect using SSMS through windows authentication.

0 ·

chandru commented · Nov 10, 2010 at 01:48 AM

It works fine when we debug the web application ( ASP.NET). but it won't when we publish in IIS. We are using Integrated Windows Authentication in IIS.

0 ·

Kev Riley ♦♦ commented · Nov 10, 2010 at 02:02 AM

I'm no IIS expert, but what account does IIS run under? It's that account that you need to check the permission on

0 ·

chandru commented · Nov 10, 2010 at 02:07 AM

Yes, when we say Integrated Windows Authentication in IIS, it will consider Windows domain account (domain\user). I have also created the domain user in SQL Server.

0 ·

Kev Riley ♦♦ commented · Nov 10, 2010 at 02:24 AM

do you get an error message with error number 18456 ?

0 ·

chandru commented · Nov 10, 2010 at 03:17 AM

The error number is -2146232060

0 ·

Kev Riley ♦♦ commented · Nov 10, 2010 at 03:44 AM

Can you try connecting with SQL authentication, to see if that can narrow down the issue. If that works, we are back to checking that the account running IIS or even ASP is allowed access to SQL.

0 ·

chandru commented · Nov 10, 2010 at 03:53 AM

Thanks Kev. Earlier I was using SQL authentication and it was working perfect. But when I changed it to Windows authentication I got the error. (I could not take the project into production with SQL authentication, so I badly want it to work in Windows auth.)

0 ·

Answer 2 · 2010-11-10T05:07:12Z

Matt Whitfield answered Nov 10, '10

You could add a Windows Authentication account to the SQL Server that maps to the service process used for IIS - but it might be better not to do that, as that would mean that the IIS process would have access to your SQL Server by default.

1

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Oleg commented · Nov 10, 2010 at 06:57 AM

I believe that if you have **** in the web.config of the web app then it is totally bad because the account of the user connected to the site will be attempted to be used to connect to SQL Server, which is horrible as it will completely destroy connection pooling. if you have **** then the account used to run the IIS process will be attempted to be used (there are no App Pools in Windows Server 2000). In any case, in order for whatever credentials to be passed from the server hosting IIS to the SQL Server, one AD permission need to be set, I think it is called **Allow Kerberos to delegate requests**. If you ask any sane network admin to add it, the simple answer would be that ***it will never happen***. To make the long story short, it is not a good idea to attempt using SSPI to connect to SQL Server from the web app. Just my 2 cents.

2 ·

question