Recently we have this issue in active node which is part of failover cluster instance. The active node shutdown automatically and transfer all roles to the passive node. Upon checking the sql error log.
Error:
AppDomain 3 (XXX_XX.dbo[runtime].2) is marked for unload due to memory pressure.
AppDomain 2 (XXX.dbo[runtime].1) is marked for unload due to memory pressure.
AppDomain 3 (XXX_XX.dbo[runtime].2) unloaded
AppDomain 2 (XXX.dbo[runtime].1) unloaded.
AppDomain 5 (XXX.dbo[runtime].4) created.
See dump files created for more details:
Current time is 16:31:17 06/19/17.
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 11.0.5058.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-4607 v2 @ 2.60GHz.
Bios Version is HP - 2
48 X64 level 8664, 2 Mhz processor (s).
Windows NT 6.2 Build 9200 CSD .
Memory
MemoryLoad = 99%
Total Physical = 131037 MB
Available Physical = 235 MB
Total Page File = 162458 MB
Available Page File = 23377 MB
Total Virtual = 8388607 MB
Available Virtual = 8115635 MB
**Dump thread - spid = 0, EC = 0x0000001566B37F40
*
* User initiated stack dump. This is not a server exception dump.
*
***Stack Dump being sent to F:\MSSQL11.OHREP\MSSQL\LOG\SQLDump0010.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 06/19/17 16:31:19 spid 2320
*
* FIRST OCCURRENCE: Common Language Runtime escalation on critical resource.
*
* Input Buffer 78 bytes -
* ܧ SELECT dbo.fn_Guid() AS guid
*
*
* MODULE BASE END SIZE
* sqlservr 000007F761250000 000007F7612A9FFF 0005a000
* ntdll 000007FEA1FE0000 000007FEA219DFFF 001be000
* KERNEL32 000007FE9F6C0000 000007FE9F7F6FFF 00137000
* KERNELBASE 000007FE9F060000 000007FE9F153FFF 000f4000
* ADVAPI32 000007FEA1B40000 000007FEA1C1DFFF 000de000
* MSVCR100 000000005DD60000 000000005DE31FFF 000d2000
* MSVCP100 000000005DCC0000 000000005DD57FFF 00098000
* sqlos 000000005B130000 000000005B136FFF 00007000
* NETAPI32 000007FE9D4E0000 000007FE9D4F4FFF 00015000
* pdh 000007FE95DA0000 000007FE95DEBFFF 0004c000
R8: 00000029E6094AF1: 3635313030303030 0030344637334236 0000000000000000 0000000000000000 00000000 00000000 0000000000000000
Rip: 000007FE9F0A7B8C: 000000C0248C8B48 FFFB9954E8CC3348 C3000000D8C48148 CCD6EB0038246483 90909090 90909090 8D485508245C8948
Here is the eventlog error:
The computer has rebooted from a bugcheck.
The bugcheck was: 0x0000007a (0xfffff8a019eda6c0, 0xffffffffc000026e, 0x000000097e44b8c0, 0xfffff880196d8060).
A dump was saved in: C:\Windows\MEMORY.DMP.
Report Id: 061917-61343-01
Here is the function code:
CREATE FUNCTION [dbo].[fn_Guid]()
RETURNS [uniqueidentifier] WITH EXECUTE AS CALLER
AS EXTERNAL NAME
[Gcs.Sys.Data.DatabaseAssembly].[UserDefinedFunctions].[NewSequentialId]
Does anyone encountered this?
Thanks, Joel
It looks like you may have a memory bug in your CLR function [Gcs.Sys.Data.DatabaseAssembly].[UserDefinedFunctions].[NewSequentialId]
. I'm not sure why you are using a CLR function to get a new sequential GUID rather than the built in NEWSEQUENTIALID()
SQL Server function:
Why not use:
SELECT NEWSEQUENTIALID() AS Guid
User contributions licensed under CC BY-SA 3.0