login failed for user (null)

Hi
I have .net app got this error below,
Connection failed: sqlstate:28000 sql server error: 18452 login failed for
user(null). reason: not associated with a trusted SQL server connection
Any ideas
thanksYour SQL Server Authenticaton could be Windows Authentication and a user
tries to connect using his\her SQL Server login.
Another possibility, that user might not be a member of your domain and
tries to connect to your SQL Server instance.
Ekrem nsoy
"mecn" <mecn2002@.yahoo.com> wrote in message
news:e45jDthJIHA.3516@.TK2MSFTNGP02.phx.gbl...
> Hi
> I have .net app got this error below,
> Connection failed: sqlstate:28000 sql server error: 18452 login failed for
> user(null). reason: not associated with a trusted SQL server connection
> Any ideas
> thanks
>|||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.
"mecn" wrote:

> Hi
> I have .net app got this error below,
> Connection failed: sqlstate:28000 sql server error: 18452 login failed for
> user(null). reason: not associated with a trusted SQL server connection
> Any ideas
> thanks
>
>|||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.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sean McCown" <SeanMcCown@.discussions.microsoft.com> wrote in message
news:2EA9BABD-7F69-4758-BD14-A7809FAB6657@.microsoft.com...[vbcol=seagreen]
> 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.
>
> "mecn" wrote:
>|||Hmm.. Good point!
Thanks for sharing.
Ekrem ?nsoy
"Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
news:6E02C41D-1A5E-4A9A-9218-BC5BF1746759@.microsoft.com...
> 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.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Sean McCown" <SeanMcCown@.discussions.microsoft.com> wrote in message
> news:2EA9BABD-7F69-4758-BD14-A7809FAB6657@.microsoft.com...
>