Is there a way to use connection strings to connect to SQL Server? Or the string was used in an unsuccessful login attempt.
Many times I have to deal with complex systems in which I see a failure due to some service which fails to enter SQL. I'm guessing that the connection string may be wrong, but since I can not see what I'm having problems, I'm having problems finding out that in order to really add that problem, reconfigure it and it Due to being able to fix
Errors in logs just say a few: 2009-12-01 20: 16: 31.05 Logon failed with SSPI Hathyshek error code 0x8009030c when connection with integrated security was established; Connection has been closed. [Customer: 10.124.172.65] 2009-12-01 20:16:16: 31.06 Logon error: 18452, Seriousness: 14, State: 1. 2009-12-01 20: 16: 31.06 Logon login failed. Login is from an untrusted domain and can not be used with Windows authentication. [Customer: 10.234.222.13]
Can any audit be done that I can be able to smell the connection string or put the equipment so that there is a problem in the string by analyzing the string?
Not really the connection string is only a case between client applications and SQL client libraries and to monitor that tight spot There is no out-the-the-box tool for.
However, there is no one in your example Need to know the connection string, you know that the connection string was using integrated security (according to the 'SSPI handshake' definition), you know that It was trying to connect to the server on which this error was logged, you know the cause of failure (error SEC_E_LOGON_DENIED), and you know which customer has tried to connect (10.234.222.13). There is absolutely nothing in the connection string which will help in troubleshooting this problem.
The error you are seeing is an SSPI error, especially Kerberos / NTLM error and if you use Kerberos / NTLM devices and methods, most not all, if Kerberos / NTLM problems Taxation can be troubleshooting.
In your case you will find one of the common culprits:
- Services are running
- A expired password
- Try connecting with (most likely) services
No comments:
Post a Comment