Rick,

>Could also be that the 1.1 app was running under a different account? Maybe System or soem other admin account.

Yesterday I seemed to remember some setting in the machine.config, so I went and checked it out earlier today. Sure enough, the machine.config under 1.1 had userName="SYSTEM", but there was no such setting in the 2.0 machine.config. HOWEVER ... changing these did not make any difference (setting userName="SYSTEM" in the 2.0 machine.config still didn't allow a login to SQL Server, and getting rid of it in the 1.1 machine.config still allowed me access).

>Something's different there and you can use the < %= Environment.Username % > to compare which users you are in fact dealing with.

So, that's what I did, and the Environment.Username told me that the 1.1 app was running under "SYSTEM" (I'm assuming that the 2.0 app is running under ASPNET because of the error messages I was getting).

I still don't know how the 1.1 ASP.NET had a "SYSTEM" username though, since when I took the userName="SYSTEM" out of the 1.1 machine.config, the 1.1 app still worked and it still said the Username was "SYSTEM", so it looks like it's also getting set somewhere else.

I'm not too concerned, since this is my development machine, but I'd sure like to know how it got set that way, just for my own knowledge (and in case I need to impart this knowledge to a customer <g>). Any more ideas where I might look?

~~Bonnie


>>The same applies for Web Services, correct?
>>
>>We can suggest configurations all we want to customers, but if they want to use a Trusted Connection, then they're going to do it. <g> So, I needed to figure out how to get it to work, regardless of whether I do it that way or not.
>>
>>If you read the other posts in this thread, you'll see that I solved the issue by adding the login MyComputerName\ASPNET to my Sql Server security. I assume this was the correct way to handle it. It works anyway. <g>
>>
>>Still, I don't understand why I didn't need to do anything for a 1.1 Web Service.
>
>Could also be that the 1.1 app was running under a different account? Maybe System or soem other admin account.
>
>I could also be that ASPNET was part of a group that already has rights...
>
>IAC, I don't think there's anything that's different in the way that this works - the IIS worker process account determines the security environment the same in 1.1 as in 2.0. Something's different there and you can use the < %= Environment.Username % > to compare which users you are in fact dealing with.
>
>+++ Rick ---