Hi All,I am trying to find out the root cause for SQL Server crash. A timeout (30000 milliseconds) was reached while waiting for a transaction response from the MSSQLSERVER service.The SQL Server (MSSQLSERVER) service terminated unexpectedly. It has done this 5 time(s).AutoRestart: Unable to restart the MSSQLSERVER service (reason: An instance of the service is already running)This file is generated by Microsoft SQL Server version 12.0.4213.0 upon detection of fatal unexpected error. Please return this file, the query or program that produced the bugcheck, the database and the error log, and any other pertinent information with a Service Request. Computer type is Intel(R) Xeon(R) CPU E5-2670 v2 @ 2.50GHz. Bios Version is Xen - 0 Revision: 1.221 32 X64 level 8664, 10 Mhz processor (s). Windows NT 6.2 Build 9200 CSD . Memory MemoryLoad = 94% Total Physical = 249999 MB Available Physical = 14127 MB Total Page File = 267338 MB Available Page File = 28793 MB Total Virtual = 134217727 MB Available Virtual = 133598094 MB ***Stack Dump being sent to D:\tempdataroot\MSSQL12.MSSQLSERVER\MSSQL\LOG\SQLDump0039.txt SqlDumpExceptionHandler: Process 159 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process. * ******************************************************************************* * * BEGIN STACK DUMP: * 07/29/16 16:21:52 spid 159 * * * Exception Address = 000000007A93E615 Module(cwbodbc+000000000005E615) * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION * Access Violation occurred reading address 000000006029E2CA * Input Buffer 48 bytes - * _GetTransfers * This dump is generated frequently. The SP name changes. We have a linked server which gets the data from AS400 using cwbodbc(IBM iSeries) driver. This is a primary node of AG setup. After primary node failed the automatic failover kicked in but dint succeed. Following errors were reported. The lease between availability group 'P1AG' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover Cluster. To determine whether the availability group is failing over correctly, check the corresponding availability group resource in the Windows Server Failover ClusterAlwaysOn Availability Groups connection with secondary database terminated for primary database 'a' on the availability replica 'P2' with Replica ID: {}. This is an informational message only. No user action is required. The availability group database "a" is changing roles from "PRIMARY" to "RESOLVING" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required.Unable to access availability database 'a' because the database replica is not in the PRIMARY or SECONDARY role. Connections to an availability database is permitted only when the database replica is in the PRIMARY or SECONDARY role. Try the operation again later.Please help me troubleshoot this.
↧