SQL 05 EE connection problem | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

SQL 05 EE connection problem

I am not familar with this db application, clients complained that they can not connect DB, I checked the event log and sql log, found the following error message SSPI handshake failed with error code 0x80090311 while establishing a connection with integrated security; the connection has been closed. [CLIENT: 10.40.16.21] Login failed for user ”. The user is not associated with a trusted SQL Server connection. [CLIENT: 10.40.16.21]
I searched the MS support, Somebody posted this error, but no obvious answer now.
It seems more like a network issue for me.
Gurus, any idea? ——————
Bug explorer/finder/seeker/locator
——————
Refer to KB247931. and following link http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=285649&SiteID=1 Don’t know if the answer is contained in above link ——————
Bug explorer/finder/seeker/locator
——————
You may also get this when your sql server is configured to use only "Windows Athentication". Make sure your sql server is configured to mixed mode if you are using SQL login.
MohammedU.
Moderator
SQL-Server-Performance.com All postings are provided “AS IS” with no warranties for accuracy.
If you are using Named pipe and specify FQDN or ipaddress in the connection string or even use IP Address to connection the server. Also ensure there are no DNS issues for having issues with machine name. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
To MohammedU: The server is SQL 2005 EE without any SP. Mixed authentication mode is used.
To Satya: You think it is because of the Named Pipe protocol?
No DNS issues.
The strange thing is: this error only happened twice, when it happened, customer called and complained no connection to the database. We did not do anything, later customer told us the connection is OK. We just trying to find the root cause. BTW: this is a shared server, several applicaitons are using the same instance, different database. ——————
Bug explorer/finder/seeker/locator
——————
This person had same situation as me. http://education.sqlfarms.com/ShowPost.aspx?PostID=366 ——————
Bug explorer/finder/seeker/locator
——————
It could be issues with Named pipes with the DNS when using FQDN, you might switching between the protocols. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
]]>