Skip to content
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

added a check to net.Error.Timeout() before returning driver.ErrBadConn #175

Merged
merged 1 commit into from
Nov 26, 2016

Conversation

melignus
Copy link
Contributor

@melignus melignus commented Oct 7, 2016

I believe this doesn't necessary close #134 or #105 but I think it will help troubleshoot in the future and addresses problems that were brought up in both issue threads.

net.Error has a method .Timeout() that returns a bool if the error was because of an expired timeout. I added a check before the return of the driver.ErrBadConn.

@denisenkom denisenkom merged commit ecf5301 into denisenkom:master Nov 26, 2016
@denisenkom
Copy link
Owner

merged, thanks!

@etangle
Copy link

etangle commented Mar 24, 2017

I am getting error:
2017/03/24 05:08:22 Prepare failed:Login error: read tcp 127.0.0.1:50303->127.0.0.1:1433: wsarecv: An established connection was aborted by the software in your host machine.
exit status 1

Running netstat, I don't see any connection attempt from it, nor putting wrong credentials show login error in sql server logs

Running Windows Server 2008 R2 with SQL Server EXPRESS 2005

It works with SQL Server 2008

odeke-em pushed a commit to orijtech/go-mssqldb that referenced this pull request Jul 26, 2020
Add mongodb driver to Dockerfile
gabrielcorado pushed a commit to gravitational/go-mssqldb that referenced this pull request Oct 4, 2024
* Update dependencies

* support dataverse endpoint
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Azure SQL driver: bad connection
3 participants