June 4, 2008 at 8:14 am
Error: 18452 Login failed for user ‘(null)’. The user is not associated with a trusted SQL Server connection.
user having this error when they are trying to connect to sqlserver,it is also funny that he uses same workstation for accessing the Box.with different applications one application have no problem to access and other application throughs error.
Connection string ::
"Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection." Error number 18452.
June 4, 2008 at 8:27 am
Is it a web application? What are the connection strings for the applications? What are the differences in the applications?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
December 7, 2011 at 1:22 pm
I am getting the same error listed above when trying to log into management studio with Windows authentication to administer the database instance. However if I change the server name from [servername] to [.] I can log in successfully.
My Windows account is a member of the sysadmin server role.
I can login fine with SQL Server authentication.
I am remoting into the server and connecting locally to Managment Studio(No connection strings or ODBC involved).
The version of SQL Server is 9.0.4340.
Authentication is set to SQL Server and Windows Authentication mode.
Has anyone else seen this or know what might be causing it?
December 8, 2011 at 9:48 am
Have you tried creating a Login for that Windows account in SQL Server? I have seen that sometimes its best to explicitly create a Login for windows account instead of putting them in the local windows admin group.
Kaushik
Blog
http://saveadba.blogspot.com/
December 8, 2011 at 10:26 am
savethytrees (12/8/2011)
Kaushik
http://saveadba.blogspot.com[/quote%5D
Thank you for your reply. I tried what you are suggesting after posting yesterday and I still got the same results. The workaround for me is just to use [.] when I'm logging into Management Studio. It would be nice to know what's happened but this is working for now and it does not affect the application as it is using a SQL Server account to connect. Thanks again!
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply