Sqlstate 08s01 ошибка соединения

RRS feed

  • Remove From My Forums
  • Question

  • I’m getting this error in a VMWare ESX environment.  The application establishes a new connection for each transaction (yes, I know that’s not a good idea) but subsequent transactions generally succeed after I get a few of these failures. 

    I’m opening a support incident with VMWare, since it doesn’t seem to occur in a non-virtual environment, but I thought I’d post here too in case someone has seen something similar.

    Thanks for your help,
    Martin

All replies

  • We’re seeing the same thing as we’re supporting a company that runs an application that creates a new connection for each command.

    Their hardware setup is a Dell 1800 w/Dual 3GHz Xeons and raid array, connected to a Cisco 2948 catalyst switch for network.

    The database is running the 2005 version of msde… SQL Express i believe.

    A host of errors they get… at least a few times a day

    Error: 08S01 — Communication link failure

    Error: 01000 — ConnectionWrite (send())

  • I have the same issue. Got any solution.

  • I have the same issue at around 1400 connections to SQL.   Any resolution?

  • We have the same errors.. «Communication link failure» often preceeded by the «ConnectionWrite(send())» error.  This is on a 3rd party application so we don’t know the internals of how it functions.  Suspect that it likewise creates a new connection for each command but not really sure.

    The application runs on multiple app servers and they connect to a dedicated database server.

    Database server is 64 bit Server 2003 with 64 bit SQL 2005, 4 dual core processors, and 16 GB RAM.

    We have looked at almost everything and cannot isolate the problem or find a solution.

    Any suggestions would be appreciated.

  • I’ve got a customer with the same issue. They are the only customer I have running the queries over the WAN.

    I had one example where trying to connect to one SQLServer server I got the message. Trying to connect to another server, did not get the problem. Rebooting the client machine solved (and typically solves) this problem.

    If anyone has info on this, it would be greatly appreciated. Doesn’t look like this question’s getting much attention.

  • I got a similar message. I’m working on a VM and it says OLE DB error: OLE DB or ODBC error: Communication link failure; 08S01; Shared Memory Provider: No process is on the other end of the pipe.
    ; 08S01.

    When I try to process an Analysis Services cube.

    Any ideas anyone?

  • Same here, please respond if there is any available solution.

  • I have an application that uses ADO to create recordsets on the fly and throw them away after reading data, using one connection object.

    If used on a local

    SQL Server 2005, the communication link failure occures when network connection broke down between two uses of recordsets. The temporary disrupted network connection (eg. WLAN) has nothing to do with the communication between application and server (local), and the connection is not broken at the time the error occures. This can be reproduced by temporary disconnecting any network connection.

    The property Connection.Connected is still true after network connetcion failed temporary. So my workaround is to catch up the error at Recordset.Open, reconnect if Error.SQLState is 08S01 (setting

    Connection.Connected to false and true), and try again.

  • Martin, i know this is a very very old thread but we are seeing this same issue. Did VMWare ever help on the issue (you had said you had a case open with them)? Brent

  • TruckinITGuy (Brent)…  Did you ever determine a cause and get a fix for this?  We are having the same problem on ESX.  I found another article that suggested changing the value of SynAttackProtect (below).  We probably have that set
    to 1 for better security, I am going to try to set that back to 0 and see if that helps.  But if you made headway, I would appreciate knowing how.  Jeff


    The following parameters can be used with this registry value:

    • 0 (default value): No SYN attack protection
    • 1: Set SynAttackProtect to 1 for better protection against SYN attacks. This parameter causes TCP to adjust the retransmission of SYN-ACKS. When you set SynAttackProtect to 1,
      connection responses time out more quickly if the system detects that a SYN attack is in progress. Windows uses the following values to determine whether an attack is in progress:

      • TcpMaxPortsExhausted
      • TCPMaxHalfOpen
      • TCPMaxHalfOpenRetried
  • I know this thread is old.  Did anyone ever get this issue resolved?  I am experiencing the same issue with VM running on ESXi 3.5 and the system had been running fine since 2008. Nothing has changed in the system, but users are getting disconnected
    several times a day from our ERP system for two weeks now. SQL 2005 SP3 On Windows 2003 64 Bit.


    ra

    • Proposed as answer by

      Monday, October 28, 2013 5:48 PM

  • We are also getting the out of memory error when processing an AS cube that had previously run fine.

      «OLE DB error: OLE DB or ODBC error: Communication link failure; 08S01; Communication link failure; 08S01; Shared Memory Provider: No process is on the other end of the pipe.»

    The Windows System Event Viewer Log revealed a ‘Resource-Exhuastion-Detector’ Warning:

        «Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: sqlservr.exe (1280) consumed 13694660608 bytes, msmdsrv.exe (5464) consumed 10279247872 bytes, and Ssms.exe (4032)
    consumed 775794688 bytes.»

    We are expanded the PageFile on the VM and will see if that helps.  We are also rebooting the server and performing delayed monthly maintenance, so that may also contribute to the solution.

    The lack of memory has also caused the MSSQLSERVEROLAPService to crash and stop itself. 

        «The description for Event ID 22 from source MSSQLServerOLAPService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the
    component on the local computer.

       If the event originated on another computer, the display information had to be saved with the event.

       The following information was included with the event:

       Internal error: An unexpected exception occurred.

       the message resource is present but the message is not found in the string/message table»

    ———-

    UPDATE: Expanding the PageFile on the VM seemed to have resolved the problem.  The AS Cube processed successfully.

    • Proposed as answer by
      ColSanders
      Tuesday, October 29, 2013 10:55 PM
    • Edited by
      ColSanders
      Wednesday, October 30, 2013 3:54 AM

Это сообщение в блоге было создано, чтобы помочь вам в случае возникновения odbc sqlstate подразумевает ошибку 08s01.Microsoft описывает всю причину отказа соединения SQLState 08S01 как ошибку, которая возникает, когда соединение между транспортным средством и корнем данных, к которому был подключен наш собственный драйвер, было неудачным до обработки задачи.

Так случилось, что недавно у нас были проблемы с потерей сети в каждой из наших компаний с SQLSTATE, что означает концепцию ошибки 08S01 или SQLSTATE = 08001. Нам нужно несколько сотрудников, которые запускают приложения, подключаемые к клиентским системам, которые будут помогать, а затем извлекать данные. Одна из наших компаний и клинеров имеет клиентскую базу сервера Microsoft MySQL. Однако хост mySQL и другое устройство, с которым общаются клиенты, создают проблемы с сетью. Если они подключены напрямую, то есть к серверу через подключение к удаленному рабочему столу, скорее всего, проблем с сетью не будет, что необычно, поскольку они всегда подключаются к серверу через какой-то тип сети. Либо эти концепции, проблемы точно не возникают по какой-то конкретной причине, они все случайны и неожиданны. Иногда мы можем прожить эти дни без каких-либо проблем, в то время как в другое время у нас возникают проблемы каждый час или несколько условий в день.

Ошибка odbc sqlstate соответствует 08s01

Серверные операционные системы: 64-разрядная версия Windows 2008 R2 SP1, в которой есть все обновления, включая все корпоративное обновление 2775511. http: и / support.microsoft .org / kb / 2775511

ошибка odbc sqlstate = 08s01

Клиентские ПК: 64-разрядная версия Windows 7 с пакетом обновления 1 (SP1) во всех обновлениях, включая накопительное обновление 2775511 для бизнеса. http: / / support.microsoft.com/ kb / 2775511

Используемое телевизионное оборудование: коммутатор Dell PowerConnect 5324 (главный коммутатор), коммутатор Cisco sf200-24p (много в компании), точка доступа Netgear WNDAP660 (основная точка доступа), SonicWall 210 tz (основной межсетевой экран)

Вторичное расположение DNS: второй сервер, на котором размещены другие компьютерные приложения, которым известно, что наши клиенты подключаются.

  • Брандмауэр Windows отключен во всех системах
  • Все функции энергосбережения системы, в том числе сетевая карта, часто отключены.
  • Проверил конфигурацию DHCP и убедился, что все действительно правильно настроено.
  • Убедитесь, что нет конфликтов в IP-адресах или странной аренды IP-адресов.
  • Может загружаться из nslookup обоими методами с IP или именем системы. (Однако, если есть разница, серверы недоступны, более того, с ними вы даже не можете пинговать их.)
  • Проверены контактные штыри и заменены все сетевые кабели, отвечающие самым высоким требованиям к серверам и ключевым точкам. (Поскольку раздражение исходит от всей компании, я вполне уверен, что это не все кабели, но, скорее всего, кабели, идущие обратно к серверу, на котором размещено мое устройство DHCP, на котором может быть разорвано кабельное соединение, просто вот так, это не т. помогло)
  • Пробовал один раз и выполнил все шаги, описанные в этой рекламной статье, благодаря Microsoft: http: / за support.microsoft.com/ kb и < wbr> 942861
  • Все точки доступа и серверы, компьютерные принтеры получают свои собственные статические IP-адреса, и, как видите, на лучших клиентских ПК включена аренда DHCP.
  • Проверьте конфигурацию DNS человека, и все в порядке. (Возможно, я что-то не упустил)
  • Системные ресурсы действительно проверены, и мы производим много ресурсов, включая оставшиеся ресурсы, и сетевой оператор не должен перегружать сетевой трафик.
  • К сожалению, депутат по поводу выключателей, к которым они подключены, наверное, проблему не решил.
  • Подключается к небольшому количеству систем непосредственно к главному элементу управления, к которому подключены серверы, чтобы гарантировать, что другие коммутаторы, которые мы предлагаем у поставщика услуг, могут быть неисправными, хотя все еще существуют препятствия в системах, ближайших к хосту.
  • Я рискнул на многое, но пока не помню, чтобы отдыхал.

Любая помощь должна быть оценена по достоинству. Пожалуйста, дайте мне знать, если вам понадобятся другие вопросы, чтобы помочь решить этот вопрос. Эта проблема существует уже несколько месяцев, и, как следствие, мы просто не можем понять, что может вызвать эту проблему. Спасибо заранее!

v <время>

г.

I am getting this error (not so frequently):

2013-05-08 16:44:35,786  WARN (JDBCExceptionReporter.java:100) [org.hibernate.util.JDBCExceptionReporter, logExceptions] - SQL Error: 0, SQLState: 08S01
2013-05-08 16:44:35,786 ERROR (JDBCExceptionReporter.java:101) [org.hibernate.util.JDBCExceptionReporter, logExceptions] - Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
2013-05-08 16:44:35,833 ERROR (AdminDaoImpl.java:297) [com.myapp.admin.db.AdminDaoImpl, createFilePackage] - data-upload: Exception while adding new file package
org.hibernate.exception.JDBCConnectionException: Cannot open connection
    at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:97) [hibernate-core-3.3.2.GA.jar:3.3.2.GA]
    at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) [hibernate-core-3.3.2.GA.jar:3.3.2.GA]
    at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:52) [hibernate-core-3.3.2.GA.jar:3.3.2.GA]
    at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:449) [hibernate-core-3.3.2.GA.jar:3.3.2.GA]
    at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:167) [hibernate-core-3.3.2.GA.jar:3.3.2.GA]
    at org.hibernate.jdbc.JDBCContext.connection(JDBCContext.java:142) [hibernate-core-3.3.2.GA.jar:3.3.2.GA]
    at org.hibernate.transaction.JDBCTransaction.begin(JDBCTransaction.java:85) [hibernate-core-3.3.2.GA.jar:3.3.2.GA]
    at org.hibernate.impl.SessionImpl.beginTransaction(SessionImpl.java:1354) [hibernate-core-3.3.2.GA.jar:3.3.2.GA]
    at com.myapp.admin.db.AdminDaoImpl. createFilePackage(AdminDaoImpl.java:182) [AdminDaoImpl.class:na]
    at com.myapp.admin.ctrl.UploadController.processUploadZip(UploadController.java:217) [UploadController.class:na]
    at sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source) [na:na]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [na:1.6.0_35]
    at java.lang.reflect.Method.invoke(Method.java:597) [na:1.6.0_35]
    at org.springframework.web.method.support.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:212) [spring-web-3.1.0.RELEASE.jar:3.1.0.RELEASE]
    at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:126) [spring-web-3.1.0.RELEASE.jar:3.1.0.RELEASE]
    at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:96) [spring-webmvc-3.1.0.RELEASE.jar:3.1.0.RELEASE]
    at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:617) [spring-webmvc-3.1.0.RELEASE.jar:3.1.0.RELEASE]
    at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:578) [spring-webmvc-3.1.0.RELEASE.jar:3.1.0.RELEASE]
    at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:80) [spring-webmvc-3.1.0.RELEASE.jar:3.1.0.RELEASE]
    at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:900) [spring-webmvc-3.1.0.RELEASE.jar:3.1.0.RELEASE]
    at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:827) [spring-webmvc-3.1.0.RELEASE.jar:3.1.0.RELEASE]
    at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882) [spring-webmvc-3.1.0.RELEASE.jar:3.1.0.RELEASE]
    at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:789) [spring-webmvc-3.1.0.RELEASE.jar:3.1.0.RELEASE]
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:647) [servlet-api.jar:na]
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) [servlet-api.jar:na]
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) [catalina.jar:7.0.35]
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) [catalina.jar:7.0.35]
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) [catalina.jar:7.0.35]
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) [catalina.jar:7.0.35]
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) [catalina.jar:7.0.35]
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) [catalina.jar:7.0.35]
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) [catalina.jar:7.0.35]
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) [catalina.jar:7.0.35]
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) [catalina.jar:7.0.35]
    at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:200) [tomcat-coyote.jar:7.0.35]
    at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) [tomcat-coyote.jar:7.0.35]
    at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310) [tomcat-coyote.jar:7.0.35]
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [na:1.6.0_35]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [na:1.6.0_35]
    at java.lang.Thread.run(Thread.java:662) [na:1.6.0_35]
Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

I have two web (spring mvc + hibernate + mysql) applications hosted on shared server:

1) main app to show files for download (which is inserted through admin app)

2) admin app with CRUD operations

This error appears sometime, when I am using «admin» application to upload files for «main» app, lets say may be after successfully uploading/processing around 100-120 files/requests and on each request hitting database with 10-20 insert/update queries.

Hosting Details:

Private tomcat hosting
java 1.6.0_35-b10
tomcat 7.0.35
heap size 288MB
MySQL Server 5
commons-dbcp 1.2.2
mysql-connector-java 5.1.9

Database + Hibernate + DBCP properties:

<bean id="dbDataSource" class="org.apache.commons.dbcp.BasicDataSource">
    <property name="driverClassName" value="com.mysql.jdbc.Driver" />
    <property name="username" value="test" />
    <property name="password" value="test" />
    <property name="url" value="jdbc:mysql://localhost/my_database?useUnicode=yes&characterEncoding=UTF-8" />

    <!-- DBCP Connection Pool Settings -->
    <property name="defaultAutoCommit" value="true" />
    <property name="initialSize" value="10" />
    <property name="maxActive" value="500" />
    <property name="maxIdle" value="8" />
    <property name="minIdle" value="0" />
    <property name="maxWait" value="30000" />
    <property name="validationQuery" value="SELECT 1" />
    <property name="testOnBorrow" value="true" />
    <property name="testOnReturn" value="false" />
    <property name="testWhileIdle" value="false" />
    <property name="timeBetweenEvictionRunsMillis" value="-1" />
    <property name="numTestsPerEvictionRun" value="3" />
    <property name="minEvictableIdleTimeMillis" value="180000" />
    <property name="poolPreparedStatements" value="true" />
    <property name="maxOpenPreparedStatements" value="25" />
    <property name="accessToUnderlyingConnectionAllowed" value="false" />
    <property name="removeAbandoned" value="false" />
    <property name="removeAbandonedTimeout" value="300" />
    <property name="logAbandoned" value="false" />
</bean>

hibernate.dialect=org.hibernate.dialect.MySQLDialect
hibernate.hbm2ddl.auto=none
hibernate.jdbc.batch_size=100
hibernate.show_sql=false
hibernate.format_sql=false
hibernate.cache.use_second_level_cache=true
hibernate.cache.use_query_cache=false
hibernate.cache.provider_class=org.hibernate.cache.NoCacheProvider
hibernate.current_session_context_class=thread

Concerned Code:

public String createFilePackage(FilePackage package) {
    String message = "";

    Session session = getSessionFactory().openSession();
    Transaction tx = null;
    try {
        tx = session.beginTransaction();

        // handling package, around 10-14 DB insert, 10 SELECT and 5 update queries on same session

        tx.commit();

    } catch(Exception e) {
        logger.error("file-upload: Exception while adding new font package", e);
        if(tx != null) { tx.rollback(); }
    } finally {
        session.close();
    }
    return message;
}

any advise how to solve this issue?

@mathieuk I noticed two cases:

  1. When «— SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} —» is handled properly, there is «+++ killed by SIGKILL +++» in response and the worker (php artisan queue:work) end.

Strace

vagrant@dev:/var/www/e2$ strace -e 'trace=!all' php artisan queue:work --queue=default --timeout=10 --tries=1
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=13324, si_uid=1000, si_status=0, si_utime=0, si_stime=0} ---
[2019-01-11 14:49:44] Processing: App\Jobs\CreateJob
Start!
Query!
--- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} ---
+++ killed by SIGKILL +++
Killed

Error Log

[2019-01-11 14:49:54] local.ERROR: App\Jobs\CreateJob has been attempted too many times or run too long. The job may have previously timed out. {"exception":"[object] (Illuminate\\Queue\\MaxAttemptsExceededException(code: 0): App\\Jobs\\CreateJob has been attempted too many times or run too long. The job may have previously timed out. at /var/www/e2/vendor/laravel/framework/src/Illuminate/Queue/Worker.php:394)

  1. When it’s not handled properly, nothing happens, the worker is not killed and is doomed. Whenever a new Job arrives, it gets the link failure exception.

Strace

vagrant@dev:/var/www/e2$ strace -e 'trace=!all' php artisan queue:work --queue=default --timeout=10 --tries=1
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=13120, si_uid=1000, si_status=0, si_utime=0, si_stime=0} ---
[2019-01-11 14:31:59] Processing: App\Jobs\CreateJob
Start !
Query !
--- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} ---
[2019-01-11 14:32:09] Failed:     App\Jobs\CreateJob
[2019-01-11 14:33:25] Processing: App\Jobs\CreateJob
Start !
Query !
[2019-01-11 14:33:25] Failed:     App\Jobs\CreateJob
[2019-01-11 14:34:08] Processing: App\Jobs\CreateJob
Start !
Query !
[2019-01-11 14:34:08] Failed:     App\Jobs\CreateJob
[2019-01-11 14:36:39] Processing: App\Jobs\CreateJob
Start !
Query !
[2019-01-11 14:36:39] Failed:     App\Jobs\CreateJob
[2019-01-11 14:48:30] Processing: App\Jobs\CreateJob
Start !
Query !
[2019-01-11 14:48:30] Failed:     App\Jobs\CreateJob

Error Log

[2019-01-11 14:32:09] local.ERROR: SQLSTATE[08S01]: [Microsoft][ODBC Driver 17 for SQL Server]Communication link failure (SQL: insert into [failed_jobs] ([connection], [queue], [payload], [exception], [failed_at]) values (beanstalkd, default, {"displayName":"App\\Jobs\\CreateJob","job":"Illuminate\\Queue\\CallQueuedHandler@call","maxTries":null,"timeout":null,"timeoutAt":null,"data":{"commandName":"App\\Jobs\\CreateJob","command":"O:18:\"App\\Jobs\\CreateJob\":9:{s:29:\"\u0000App\\Jobs\\CreateJob\u0000className\";s:35:\"App\\Jobs\\CreatableJob\\GrosseRequete\";s:24:\"\u0000App\\Jobs\\CreateJob\u0000args\";a:0:{}s:6:\"\u0000*\u0000job\";N;s:10:\"connection\";N;s:5:\"queue\";N;s:15:\"chainConnection\";N;s:10:\"chainQueue\";N;s:5:\"delay\";N;s:7:\"chained\";a:0:{}}"}}, PDOException: SQLSTATE[08S01]: [Microsoft][ODBC Driver 17 for SQL Server]TCP Provider: Error code 0x2714 in /var/www/e2/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:142
[2019-01-11 14:33:25] local.ERROR: SQLSTATE[08S01]: [Microsoft][ODBC Driver 17 for SQL Server]Communication link failure (SQL: insert into [failed_jobs] ([connection], [queue], [payload], [exception], [failed_at]) values (beanstalkd, default, {"displayName":"App\\Jobs\\CreateJob","job":"Illuminate\\Queue\\CallQueuedHandler@call","maxTries":null,"timeout":null,"timeoutAt":null,"data":{"commandName":"App\\Jobs\\CreateJob","command":"O:18:\"App\\Jobs\\CreateJob\":9:{s:29:\"\u0000App\\Jobs\\CreateJob\u0000className\";s:35:\"App\\Jobs\\CreatableJob\\GrosseRequete\";s:24:\"\u0000App\\Jobs\\CreateJob\u0000args\";a:0:{}s:6:\"\u0000*\u0000job\";N;s:10:\"connection\";N;s:5:\"queue\";N;s:15:\"chainConnection\";N;s:10:\"chainQueue\";N;s:5:\"delay\";N;s:7:\"chained\";a:0:{}}"}}, PDOException: SQLSTATE[08S01]: [Microsoft][ODBC Driver 17 for SQL Server]Communication link failure in /var/www/e2/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:142

So we’ve been having issues with network connection loss at our company with the SQLSTATE = 08S01, or SQLSTATE =08001 error message. We have multiple servers which have applications running on them that client systems connect to and retrieve data from. One of our servers has a Microsoft mySQL Server database running on it. However both the mySQL server and the other server that clients connect to are having network issues. If they get connected to the server straight through a remote desktop connection, they do not experience any network issues, which is odd because they are still connected through the network to the server. Either way, these problems don’t happen at a given time, they are completely random, and unexpected. Sometimes we can go a full day without an issue, while other times we can have the issue multiple times within an hour or day.

Server OSs: Windows 2008 R2 64-bit SP1 with all Updates, including the 2775511 enterprise hotfix rollup updated. http:/ Opens a new window/support.microsoft.com/kb/2775511

Client PCs: Windows 7 64-bit SP1 with all Updates, including the 2775511 enterprise hotfix rollup updated. http:/ Opens a new window/support.microsoft.com/kb/2775511

Network Hardware we use: Dell PowerConnect 5324 Switch (Main Switch), Cisco sf200-24p Switch ( multiple all around the company), Netgear WNDAP660 AP (Main AP), SonicWall TZ 210 (Main Firewall)

DHCP and DNS location: Main Server hosting the mySQL server

Secondary DNS location: Second server hosting other accounting applications our clients connect to.

Here is what I have tried:

  • Disabled Windows Firewall on all systems
  • Disabled all Power Saving Features on all the system, including the NIC.
  • Checked DHCP configuration, and made sure everything is set up correctly.
  • Made sure there are no IP conflicts or odd IP leases.
  • Can do nslookup on all systems both with IP, or system name. (However, when the issue happens, the servers are not available, and you cannot even ping them)
  • Checked cable connections and replaced all network cables going to the servers and key locations. (Since the whole company is having the issue I am fairly sure it is not all cables, but most likely the cables going to the server hosting the DHCP server that might have a bad cable, either way, that didn’t help)
  • Tried following and performed all steps in this support article by Microsoft: http:/ Opens a new window/support.microsoft.com/kb/942861
  • All APs, Servers, and Printers have their own static IP address, and only client PCs have DHCP leasing enabled.
  • Double checked on DNS configuration, and everything seems to be set up fine. (Hopefully I’m not missing something)
  • Checked system resources and we have plenty of resources left, and the network is not overwhelmed with network traffic.
  • Replaced the Switch the servers are connected to, but did not fix the issue.
  • Connected a few systems straight to the main switch that the servers are connected to, to see if perhaps the other switches we have around the company might be faulty, but the systems connected closest to the server are still experiencing the issues.
  • I tried many other things but I can’t seem to remember the rest for now.

Any help would be really appreciated. Please let me know if you have additional questions that might help troubleshoot this issue. We’ve been having this issue for months, and we cannot figure out what might be causing it. Thanks in advance! 

attach_file
Attachment

20130719_080617.jpeg
465 KB

Понравилась статья? Поделить с друзьями:
  • Sql сервер ошибка 18456
  • Sqlite ошибка database disk image is malformed
  • Sqlcmd ошибка подключения
  • Sqlstate 08001 ошибка безопасности ssl
  • Sqlcmd ошибка входа пользователя