Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / General / Security / November 2007

Tip: Looking for answers? Try searching our database.

login failed for user (null)

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
mecn - 13 Nov 2007 17:33 GMT
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
Ekrem Önsoy - 13 Nov 2007 20:07 GMT
Your 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.

Signature

Ekrem Önsoy

> Hi
>
[quoted text clipped - 5 lines]
>
> thanks
Sean McCown - 27 Nov 2007 15:25 GMT
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.

> Hi
>
[quoted text clipped - 5 lines]
>
> thanks
Rick Byham, (MSFT) - 30 Nov 2007 22:41 GMT
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
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.