April 15, 2009 at 1:16 pm
Anyone knows how to fix this? Thank you
April 15, 2009 at 1:20 pm
Yes, you are trying to login with Windows Authentication when you are not authenticated on the domain. Either authenticate on the domain - or, use Runas to run as a domain user.
For example:
C:\Runas /netonly /user:domain\user sqlwb.exe
The above will launch SSMS with the domain credentials you need to authenticate.
Other than that, you can change to SQL Authentication and just enter the SQL username and password.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
April 15, 2009 at 1:23 pm
yulichka (4/15/2009)
Anyone knows how to fix this? Thank you
Unfortunately, there is no context with regard to this error, so actually no, I can't tell you how to fix this.
April 15, 2009 at 1:24 pm
Thank you,but I am not login in, I am trying to see why I have this in SQL Logs, Our application is using websised and I am getting this error a lot during the day, so I am trying to see why is this happening.Thank you
April 15, 2009 at 1:26 pm
yulichka (4/15/2009)
Anyone knows how to fix this? Thank you
If I may, you may want to take a few minutes and read this: The Flip Side.
April 15, 2009 at 1:29 pm
If you are seeing this message in your logs, then you have a user/service/application trying to login to SQL Server using Windows Authentication when that user/server/application has not authenticated on the domain (i.e. provided the windows credentials).
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
April 15, 2009 at 1:31 pm
April 15, 2009 at 1:35 pm
There are two reasons for this error which means SQL Server does not know the user which could even be an application runtime as Asp.net or SSRS. So if you are connecting from Asp.net you need to disable anonymous user and enable impersonation in IIS not SQL Server. And if you are connecting directly from SQL Server then you must enable both Windows authentication and SQL authentication. And no authentication to AD is not authentication to Asp.net because Asp.net permissions are resolved with IIS and SQL Server not AD and AD profile is not relevant.
Kind regards,
Gift Peddie
Viewing 8 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply