Yeah, he's right. It's trying to connect with a windows acct that doesn't
have rights in the DB. Either give it rights, or switch to sql auth.
Or the application is trying to connect using Windows Authentication when no
one is logged in, and it doesn't have a user context. I've seen this when
people set it up using Windows Authentication when they are logged in, and
expect it to work when no one is logged in.

Signature
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
> Yeah, he's right. It's trying to connect with a windows acct that doesn't
> have rights in the DB. Either give it rights, or switch to sql auth.
[quoted text clipped - 9 lines]
>>
>> thanks
Ekrem Önsoy - 30 Nov 2007 23:18 GMT
Hmm.. Good point!
Thanks for sharing.

Signature
Ekrem Önsoy
> Or the application is trying to connect using Windows Authentication when
> no one is logged in, and it doesn't have a user context. I've seen this
[quoted text clipped - 14 lines]
>>>
>>> thanks