Re: Reason: Not associated with a trusted SQL Server connection.

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Bob Barrows [MVP] (reb01501_at_NOyahoo.SPAMcom)
Date: 01/15/05 

Date: Sat, 15 Jan 2005 16:04:58 -0500

John Beschler wrote:
> "Bob Barrows [MVP]" wrote:
>
>> John Beschler wrote:
>>> Bob and Aaron,
>>>
>>> Are we really dealing with a connectivity issue here?
>>
>> Yes. obviously
>>
>>> Here's why I
>>> ask: I can access the SQL server using several other tools and
>>> applications on the XP computer.
>>
>> You're using your own user account when you do this. That's why it
>> works. ASP does not run using your user account.
>>
>
> OK, but does that mean ASP uses the IUSR account to access the SQL
> database?

Sort of. The initial "handshake" between the two computers is done under the
IUSR account, which then uses the login and password to log into the sql
server database.

> If so, why the requirement for the User ID and Password in
> the connection string? I'm still confused as to why windows is
> trying to use a trusted connection when I am using SQL server
> authentication. What am I missing in this equation?
>

There are two sets of authentications: Windows, and SQL Server. The user
needs to be accepted by Windows/network before it has access to the box on
which SQL Server is running. Without appropriate credentials on the network,
it won't even see the box on which SS is runnig. Hence, the message "server
does not exist". Once access to the box is gained, then authentication to
gain access to SS begins. If using integrated security, the SS checks to see
if the users Windows/network credentials exist in its list of logins,
allowing the user in if it does. If not, then a user id and login must be
supplied. (This is a high-level view of what takes place - don't hold me too
strongly to this story. It's been a while since I studied it and it's hazy.
But this should be close)

>
>> For example, Query Tools (George
>>> Polouse) VB 6.0, VBScript, and MS Excel. The only application that
>>> will not access the server is ASP and ASP runs fine if I try to
>>> access a local Access DB (I do not have SQL running on the XP
>>> computer.)
>>
>> You must have given the local IUSR account file-level access to the
>> folder containing your database, right? It's all permissions.
>
> Actually, I have not granted IUSR any permissions anywhere. I'm
> confused about this as well, because there is no security tab on the
> properties page for any folder on my PC. (I'm used to WIN 2K and not
> as familiar with XP yet as I'd like to be.)

So you must only have one user at a time using it on your PC. Without
granting file-level permissions to the folder containing the mdb, multi-user
activity is not possible.

If you change your XP security setting to not use Simple Security (i forget
how to do it: you'll have to google for it - i know there's an article about
it at microsoft.com), then you'll get your Security tab back.

Bob Barrows 

-- 
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

Relevant Pages