asked
Insufficient memory error, Error: 26073,TCP error, orphaned spids in KILLED/ROLLBACK. SQL2012 SP2, ENT ed!
Several times today these errors appear in this sequence and the server is hung until we bounce app servers/kill spids: 1. Error: 26073, Severity: 16, State: 1. 2.TCP connection closed but a child process of SQL Server may be holding a duplicate of the connection's socket. Consider enabling the TcpAbortiveClose SQL Server registry setting and restarting SQL Server. If the problem persists, contact Technical Support 3.Failed allocate pages: FAIL_PAGE_ALLOCATION 438 4.Memory dump 5.There is insufficient system memory in resource pool 'default' to run this query. 6.thousands of spids in KILLED/ROLLBACK;appear to be orphaned spids **Any help is much appreciated
This web site runs by votes. For all the helpful answers below, please indicate this by clicking on the thumbs up next to each of those answers. If any one answer lead to a solution, please indicate this by clicking the check mark next to that answer.
Microsoft SQL Server 2012 - 11.0.5058.0 (X64) May 14 2014 18:34:29 Copyright (c) Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.2 (Build 9200: )
This looks to be SP2 which has a number of memory related fixes.
https://support.microsoft.com/en-us/kb/2769594 My next questions are: 1. What is the memory of the Server and do you have min/max memory set 2. Typically how many connection do you have to your SQL Server
Along with the 'insufficient system memory' message in the error log, there should be results from DBCC MEMORYSTATUS - if those can be posted they may also help with diagnosis. In Twitter #SQLHelp, you indicated no added Resource Governor resource pools, which eliminates one potential cause of OOM messages. Is CLR being used? Or Extended Events?
Even without CLR or extended events in use, DBCC MEMORYSTATUS results from the SQL Server error log will be helpful in diagnosis.
18 People are following this question.
