Connection Failed: SQLState :'01000' SQL server error:'11001' [Microsoft] [ODBC Sql server driver] [TCP/IP sockets]ConnectionOpen (connect()).

• trentg

  Mr or Mrs. 500

  Points: 548

  More actions

  August 4, 2015 at 9:33 am

  #320301

  Good Morning.

  So I just rolled out 5 brand new shiney workstations with the latest and greatest UPS worldship 2015 on them in a master/slave environment. Everything is working great thanks to my UPS consultant that helped us (For FREE - I might add). Everything included the keyed import "was" working great yesterday, until the end of the day.

  Now intermittently, I get this error when trying to pull from/write back to our worldship db (SQL 2012), I also get this in the ODBC settings when trying to connect/test password:

  Connection Failed:

  SQLState :'01000'

  SQL server error:'11001'

  [Microsoft] [ODBC Sql server driver] [TCP/IP sockets]ConnectionOpen (connect()).

  Connection Failed:

  SQLState :'08001'

  SQL server Error: 6

  [Microsoft] [ODBC SQL server driver] [TCP/IP Sockets]Specified SQL server not found.

  Our New workstations are a mix of Win 7 and win 8.1, the SQL box is SQL 2012, and server 08 R2 is where the worldship db resides. I have 3 UPS machines here in our main site, and 2 down in our branch office. The ones in the branch office are the ones getting the error. We are connected via a 4.5mb/ bonded t-1 tunnel MPLS connection with very little lag.

  Thoughts? I have read in some older posts it has something to do with TCP/IP sockets timing out, but nothing to do with SQL 2012. I don't want to start making cross my fingers moves on a production SQL box. It also runs our ERP software Epicor P21.

  Thanks for the help,

  Trent Greenawalt - IT Manager

  Anderson Pump & Process - Industrial Distributor of Fluid Process Equipment

  Brookfield, WI 53045

  http://www.aaaco.com

  Trentg@aaaco.com

• trentg

  Mr or Mrs. 500

  Points: 548

  More actions

  August 4, 2015 at 9:38 am

  #1817210

  Also, I have checked all of the SQL server protocols to ensure TCP/IP is running, the SQL browser is running. What is weird when I went to "check" the settings, and hadn't changed anything it started working again. This will be an intermittent problem I would like to solve.

  Thanks for the help,

  Trent