-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Occasional failure of test_invalid_ntlm_creds due to timeout #98
Comments
I've never seen this one failing on my setup. What is your setup? Mac/windows/linux? SQL server on same machine or remote (high latency network)? |
I usually run on Windows 10 with SQL server running on the same machine. Occasionally run on Mac. |
Windows 10, SQL Server running on the same machine. None of the other tests ever give me connection errors. |
I could not get it to happen today. It might only happen when on VPN. I'll test again next time I work from home. |
I had it happen today on a dev spec'd azure DB. After the first timedout connection it worked fine. Not sure if anything should change for this, but on the first connection for a cold server this may be happening. |
This issue is happening intermittently for me and also seems to timeout after only about 1.2 seconds. The documentation says that the default The SQL Server Logs show this when the error occurs:
Here's the stack trace from my client app:
|
You are using old version, new version has a better retry mechanism, try upgrading |
Not sure if this is indicative of a real problem or not, but I get occasional failure (maybe 50% of the time) of test_invalid_ntlm_creds due to a socket timeout. Debugging into it I found the timeout seemed to be 1.2 seconds which seems awfully short?
The text was updated successfully, but these errors were encountered: