I have a SQL 2005 SP1 test server running Developer Edition on top of Windows Server 2003 SP1.ÃÂ We're testing out a 3rd party application that is using Windows Authentication to connect to SQL 2005.ÃÂ The SQL Error Log is saturated with the error message listed in the subject line.ÃÂ The text accompanying the message alternates betweenÃÂ "Login failed for user 'MYDOMAIN\TESTDA1$'. [CLIENT: <named pipe>]" and "Login failed for user 'MYDOMAIN\TESTDA1$'. [CLIENT: xxx.xxx.xxx.xxx]".
There are two strange parts to this:ÃÂ 1) The application appears to be working fine on the surface, and, 2) The MYDOMAIN\TESTDA1$ account mentioned in the error text is not the user account that we are using to connect the application to SQL 2005.ÃÂ TESTDA1 is the server name that the 3rd party software is running remotely from.
I've looked up "error state 11" using the following resource:
It describes error states 11 and 12 asÃÂ "Valid login but server access failure" but I'm not sure what that means.ÃÂ Why would SQL care about the computer account hosting the applica
View Complete Post