Connection Failed: SQLState 08001 SQL Server Error: 11001

• jeffsaks

  Old Hand

  Points: 333

  More actions

  January 12, 2016 at 12:41 pm

  #324015

  Love your forum!

  Here's the story.

  I have 20 computers running an MS ACCESS application, all connected via ODBC (SQL Server Native Client 11.0) to a SQL Server 2012.

  Everything works great, however, randomly different stations get this error:

  Connection Failed: SQLState 08001 SQL Server Error: 11001

  (See screenshot attached)

  This generally only happens to one computer at a time. It can happen while the application is idle, or running a process.

  Some computers get it once a week, some once a day.

  The fix to allow MS Access to reconnect, is either restarting the computer, or running cmd - gpupdate.exe /force which fixes the

  issue instantly.

  I've spent hours combing the web and haven't found someone with a similar issue where the error is random.

  Thanks in advance.

• Eirikur Eiriksson

  SSC Guru

  Points: 182912

  More actions

  January 12, 2016 at 1:07 pm

  #1851405

  jeffsaks (1/12/2016)

  ---

  Love your forum!

  Here's the story.

  I have 20 computers running an MS ACCESS application, all connected via ODBC (SQL Server Native Client 11.0) to a SQL Server 2012.

  Everything works great, however, randomly different stations get this error:

  Connection Failed: SQLState 08001 SQL Server Error: 11001

  (See screenshot attached)

  This generally only happens to one computer at a time. It can happen while the application is idle, or running a process.

  Some computers get it once a week, some once a day.

  The fix to allow MS Access to reconnect, is either restarting the computer, or running cmd - gpupdate.exe /force which fixes the

  issue instantly.

  I've spent hours combing the web and haven't found someone with a similar issue where the error is random.

  Thanks in advance.

  Quick questions, is the sql server instance a default or a named instance? Is sql server browser service running? What are the DNS and DHCP setup/config?

  😎

• jeffsaks

  Old Hand

  Points: 333

  More actions

  January 12, 2016 at 1:26 pm

  #1851412

  It is a Named Instance

  Sql Server is Running

  Sql Server Agent is NOT

  Sql Server Browser is Running

  Can you elaborate on the DNS/DCHP questions.

  Thanks!

  Btw: When running a connectivity test (while its working) this is the results:

  Microsoft SQL Server Native Client Version 11.00.2100

  Running connectivity tests...

  Attempting connection

  Connection established

  Verifying option settings

  INFO: A network alias was found for the DSN server. 'Protocol: DBMSSOCN; Address: MySERVER\TestServer,1433' was used to establish the connection.

  Disconnecting from server

  TESTS COMPLETED SUCCESSFULLY!

• johnwalker10

  SSCrazy Eights

  Points: 9124

  More actions

  January 12, 2016 at 10:15 pm

  #1851485

  Make sure that you have entered the correct server name, and that you can resolve the name of the server from the client. To check TCP/IP name resolution, use ping command in the Windows operating system.

• jeffsaks

  Old Hand

  Points: 333

  More actions

  January 13, 2016 at 10:15 am

  #1851656

  Hi John,

  The issue is not at startup. The issue occurs randomly while successfully using MS Access that is connected to the SQL Server...

  So wouldn't that would mean that it was entered correctly?