Funny John ... I've been meaning to update this thread for the past few days to mention that I got the problem partially solved.

Anyway, it's actually fully solved ... I found out what I had to do to get it to work. But, the question as to why it's different for ASP.NET 2.0 vs 1.1, I never did find out.

Here's what a guy on the MSDN forums told me:

>OK, so that tells me that authentication is falling back to Anonymous because it's failing on Integrated Windows authentication. So if the app is not configured for impersonation then the worker process for your ASP.NET app is running under the local ASPNET account. This is consistent so far with the error message you're getting from SQL Server.

In order for integrated security (trusted connection) to work at this point you will need to allow access for the the local ASPNET account to SQL Server. You can add the local ASPNET account (BONNIEB\ASPNET) as a user for your SQL Server database using Enterprise Manager or SQL Server Management Studio Express.

So, I did the following:

Go into Enterprise Manager, and go to Security, Logins ... add a new Login (named it ASPNET) that I simply set up as Windows Authentication and put BONNIEB under the domain name (and then of course had to mess with the permits for various databases on the server).

That's it! Works perfectly. The only thing I can think of as to why this didn't need tweaking with 1.1 was that they've possibly changed the account that ASP.NET runs under to a different name. Perhaps the original account name was included under the default "BUILTIN\Administrators" login and the new one isn't?

~~Bonnie





>Did you ever figure this one out. I'm curious about the result.
>
>
>>I'm sure this is a known problem, but I can't seem to find the fix.
>>
>>My VS2005 app connects to the SQL Server database through web services. If I connect with a connection string that uses userid and password, no problem. But, if I change that to use a Trusted_Connection instead, it won't work.
>>
>>This worked fine when the app was compiled under VS2003, but has not since migrating it to VS2005. Is there some setting I need to tweak somewhere? In IIS maybe? This is only a problem with Web Services.
>>
>>TIA,
>>
>>~~Bonnie