May 24, 2011 at 10:05 am
Hello all, I am on sql server 2005. And lately we been getting these error on our sql server log.
Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: xx.xx.xx.xxx]
I am very new to sql server, looking around it said to make sure sql server is running in mixed mode and i checked. It is working mixed mode. Not sure what else i can do about it. How can i troubleshoot this error. We are having tons of thse error. The error is also being captured in event log as well. I know that this instance of sql server is being used for sharepoint....
thanks....
May 24, 2011 at 10:25 am
it means someone is trying to log in with a blank username. the connection is originating from the ip you have x'd out.
is that the same ip address as your sharepoint server?
May 24, 2011 at 10:32 am
Thanks for the info, I figured that was the issue as its giving the IP address. But that dose not seems to be the IP address for the sharepoint server.
May 24, 2011 at 12:06 pm
Try to figure out who that IP address belongs to. It could be that they are trying to log into SQL Server or they have some sort of network scanning/inventory application on their machine that tries to connect with no login name.
May 24, 2011 at 2:14 pm
could you explain what you mean when you said ---
they have some sort of network scanning/inventory application on their machine that tries to connect with no login name.
...also we got that same thing with a user name (instead of null)
Login failed for user 'us\user_name'. The user is not associated with a trusted SQL Server connection. [CLIENT: xx.xxx.xx.xxx]
May 25, 2011 at 8:16 am
anything on this ?
May 25, 2011 at 8:32 am
abdul.irfan2 (5/24/2011)
could you explain what you mean when you said ---they have some sort of network scanning/inventory application on their machine that tries to connect with no login name.
...also we got that same thing with a user name (instead of null)
Login failed for user 'us\user_name'. The user is not associated with a trusted SQL Server connection. [CLIENT: xx.xxx.xx.xxx]
By network scanning/inventory, I meant an inventory application that scans the network and notes servers/switches/routers/database servers etc. I would not rule it out, but I didn't mean to imply scanning with malicious intent. It could just be an application on someone's machine that reaches out over the network. If it finds a SQL Server, it tries to log in to inventory the instance. It could be anything, really. That's why it is important to figure out the identity of the IP in the error. If the IP is internal, you should be able to get the identity information from a network administrator. If it is external, well, it shouldn't be external.
The "user is not associated with a trusted SQL Server connection." error means your instance accepts only Windows Authentication and someone is trying to log in with a SQL Login account. Again, the IP holds the identity of the party responsible.
May 25, 2011 at 9:05 am
This error is often tied to a case where a process that is run as a local user on a workstation tries to connect to a SQL server that is NOT local using trusted connectivity.
CEWII
May 26, 2011 at 9:02 am
We get these when a user changes their password and then try to connect to SQL server.
A simple user reboot and all is OK again.
May 27, 2011 at 4:09 pm
Had same issue when running SQL Reports, using Impersonation with Stored Credentials for Data Source or using Windows Integrated Security for Data Source.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply