sql server 2008 is terminating because of fatal exception c0000005
-
Tuesday, January 05, 2010 1:14 PMI am getting the following error in two SQL Server 2008 servers. This happens usually every two days for a month now. The SQL Server log dump is below.
SQL Server is terminating because of fatal exception c0000005. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).
----------------------------------------------------------------------------------------------------
01/04/2010 23:52:30,spid9s,Unknown,SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
01/04/2010 23:52:30,Server,Unknown,External dump process return code 0x20000001.<nl/>External dump process returned no errors.
01/04/2010 23:52:29,Server,Unknown,Stack Signature for the dump is 0x36E6F799
01/04/2010 23:52:29,Server,Unknown,77E792A3 Module(kernel32+000392A3)
01/04/2010 23:52:29,Server,Unknown,77E761B7 Module(kernel32+000361B7)
01/04/2010 23:52:29,Server,Unknown,029B173B Module(sqlservr+019B173B)
01/04/2010 23:52:29,Server,Unknown,026AE713 Module(sqlservr+016AE713)
01/04/2010 23:52:29,Server,Unknown,026ADD78 Module(sqlservr+016ADD78)
01/04/2010 23:52:29,Server,Unknown,026AD543 Module(sqlservr+016AD543)
01/04/2010 23:52:29,Server,Unknown,77E4BEF7 Module(kernel32+0000BEF7)
01/04/2010 23:52:29,Server,Unknown,* Short Stack Dump
01/04/2010 23:52:29,Server,Unknown,* -------------------------------------------------------------------------------
01/04/2010 23:52:29,Server,Unknown,* *******************************************************************************
01/04/2010 23:52:29,Server,Unknown,* SegSs: 00000023:
01/04/2010 23:52:29,Server,Unknown,* Esp: 6319E480: 6319E58C 000042AC 00000000 00000000 77E4BEF7 00000000
01/04/2010 23:52:29,Server,Unknown,* EFlags: 00000246:
01/04/2010 23:52:29,Server,Unknown,* SegCs: 0000001B:
01/04/2010 23:52:29,Server,Unknown,* Ebp: 6319E4D4: 6319E51C 026AD543 000042AC 00000000 00000000 00000000
01/04/2010 23:52:29,Server,Unknown,* Eip: 77E4BEF7: 10C2C95E 01093D00 840FC000 00000095 F29DE950 9090FFFF
01/04/2010 23:52:29,Server,Unknown,* Edx: 0000003F:
01/04/2010 23:52:29,Server,Unknown,* Ecx: 6319EAEC: 00000000 00010007 00000000 00000000 6319EDD8 00000001
01/04/2010 23:52:29,Server,Unknown,* Ebx: 0000003F:
01/04/2010 23:52:29,Server,Unknown,* Eax: 6319E484: 000042AC 00000000 00000000 77E4BEF7 00000000 00000000
01/04/2010 23:52:29,Server,Unknown,* Esi: 00000000:
01/04/2010 23:52:29,Server,Unknown,* Edi: 00000000:
01/04/2010 23:52:29,Server,Unknown,*
01/04/2010 23:52:29,Server,Unknown,* dbghelp 671A0000 672B4FFF 00115000
01/04/2010 23:52:29,Server,Unknown,* WSOCK32 71BB0000 71BB8FFF 00009000
01/04/2010 23:52:29,Server,Unknown,* ADMWPROX 66B00000 66B10FFF 00011000
01/04/2010 23:52:29,Server,Unknown,* PSTOREC 66960000 6696DFFF 0000e000
01/04/2010 23:52:29,Server,Unknown,* msidntld 66940000 66945FFF 00006000
01/04/2010 23:52:29,Server,Unknown,* msident 66920000 6692DFFF 0000e000
01/04/2010 23:52:29,Server,Unknown,* acctres 71830000 71841FFF 00012000
01/04/2010 23:52:29,Server,Unknown,* msoeacct 668D0000 66913FFF 00044000
01/04/2010 23:52:29,Server,Unknown,* mlang 664F0000 66582FFF 00093000
01/04/2010 23:52:29,Server,Unknown,* ATL 76A80000 76A91FFF 00012000
01/04/2010 23:52:29,Server,Unknown,* credui 76B80000 76BADFFF 0002e000
01/04/2010 23:52:29,Server,Unknown,* adsldpc 76DC0000 76DE7FFF 00028000
01/04/2010 23:52:29,Server,Unknown,* ACTIVEDS 76DF0000 76E23FFF 00034000
01/04/2010 23:52:29,Server,Unknown,* inetres 66480000 6648DFFF 0000e000
01/04/2010 23:52:29,Server,Unknown,* MSOERT2 66400000 66422FFF 00023000
01/04/2010 23:52:29,Server,Unknown,* INETCOMM 66350000 663FFFFF 000b0000
01/04/2010 23:52:29,Server,Unknown,* urlmon 662A0000 6634FFFF 000b0000
01/04/2010 23:52:29,Server,Unknown,* WININET 661F0000 6629AFFF 000ab000
01/04/2010 23:52:29,Server,Unknown,* cdosys 65FE0000 661E3FFF 00204000
01/04/2010 23:52:29,Server,Unknown,* SXS 65F10000 65FCCFFF 000bd000
01/04/2010 23:52:29,Server,Unknown,* MSVBVM60 65990000 65AE1FFF 00152000
01/04/2010 23:52:29,Server,Unknown,* DegCdonts 00720000 00725FFF 00006000
01/04/2010 23:52:29,Server,Unknown,* odsole70 00700000 0070EFFF 0000f000
01/04/2010 23:52:29,Server,Unknown,* xpstar 65850000 65875FFF 00026000
01/04/2010 23:52:29,Server,Unknown,* ATL80 7C630000 7C64AFFF 0001b000
01/04/2010 23:52:29,Server,Unknown,* SQLSCM 65830000 65838FFF 00009000
01/04/2010 23:52:29,Server,Unknown,* xpstar 657D0000 6581BFFF 0004c000
01/04/2010 23:52:29,Server,Unknown,* SQLNCLIR10 65790000 657C7FFF 00038000
01/04/2010 23:52:29,Server,Unknown,* sqlncli10 65520000 6577AFFF 0025b000
01/04/2010 23:52:29,Server,Unknown,* COMRes 65430000 654F5FFF 000c6000
01/04/2010 23:52:29,Server,Unknown,* CLBCatQ 777B0000 77832FFF 00083000
01/04/2010 23:52:29,Server,Unknown,* xpsp2res 65160000 65424FFF 002c5000
01/04/2010 23:52:29,Server,Unknown,* rasadhlp 636D0000 636D4FFF 00005000
01/04/2010 23:52:29,Server,Unknown,* winrnr 636B0000 636B6FFF 00007000
01/04/2010 23:52:29,Server,Unknown,* DNSAPI 76ED0000 76EF9FFF 0002a000
01/04/2010 23:52:29,Server,Unknown,* ntdsapi 63650000 63663FFF 00014000
01/04/2010 23:52:29,Server,Unknown,* SAMLIB 7E020000 7E02EFFF 0000f000
01/04/2010 23:52:29,Server,Unknown,* WLDAP32 76F10000 76F3DFFF 0002e000
01/04/2010 23:52:29,Server,Unknown,* NTMARTA 77E00000 77E20FFF 00021000
01/04/2010 23:52:29,Server,Unknown,* wshtcpip 71AE0000 71AE7FFF 00008000
01/04/2010 23:52:29,Server,Unknown,* hnetcfg 635A0000 635F9FFF 0005a000
01/04/2010 23:52:29,Server,Unknown,* dssenh 68100000 68126FFF 00027000
01/04/2010 23:52:29,Server,Unknown,* security 621B0000 621B3FFF 00004000
01/04/2010 23:52:29,Server,Unknown,* schannel 76750000 76777FFF 00028000
01/04/2010 23:52:29,Server,Unknown,* kerberos 61EE0000 61F38FFF 00059000
01/04/2010 23:52:29,Server,Unknown,* iphlpapi 76CF0000 76D09FFF 0001a000
01/04/2010 23:52:29,Server,Unknown,* cryptdll 60920000 6092BFFF 0000c000
01/04/2010 23:52:29,Server,Unknown,* msv1_0 76C90000 76CB6FFF 00027000
01/04/2010 23:52:29,Server,Unknown,* MSCOREE 52060000 520A5FFF 00046000
01/04/2010 23:52:29,Server,Unknown,* AUTHZ 76C40000 76C53FFF 00014000
01/04/2010 23:52:29,Server,Unknown,* rsaenh 68000000 68034FFF 00035000
01/04/2010 23:52:29,Server,Unknown,* sqlevn70 4F610000 4F80DFFF 001fe000
01/04/2010 23:52:29,Server,Unknown,* instapi10 00A40000 00A49FFF 0000a000
01/04/2010 23:52:29,Server,Unknown,* psapi 76B70000 76B7AFFF 0000b000
01/04/2010 23:52:29,Server,Unknown,* odbcint 008C0000 008D6FFF 00017000
01/04/2010 23:52:29,Server,Unknown,* comctl32 77420000 77522FFF 00103000
01/04/2010 23:52:29,Server,Unknown,* BatchParser 520C0000 520DEFFF 0001f000
01/04/2010 23:52:29,Server,Unknown,* NETAPI32 71C40000 71C96FFF 00057000
01/04/2010 23:52:29,Server,Unknown,* opends60 333E0000 333E6FFF 00007000
01/04/2010 23:52:29,Server,Unknown,* WINMM 76AA0000 76ACCFFF 0002d000
01/04/2010 23:52:29,Server,Unknown,* USERENV 76920000 769E1FFF 000c2000
01/04/2010 23:52:29,Server,Unknown,* VERSION 77B90000 77B97FFF 00008000
01/04/2010 23:52:29,Server,Unknown,* odbcbcp 60950000 60955FFF 00006000
01/04/2010 23:52:29,Server,Unknown,* ODBC32 48890000 488CCFFF 0003d000
01/04/2010 23:52:29,Server,Unknown,* OLEAUT32 77D00000 77D8AFFF 0008b000
01/04/2010 23:52:29,Server,Unknown,* ole32 77670000 777A8FFF 00139000
01/04/2010 23:52:29,Server,Unknown,* SHELL32 7C8D0000 7D0CEFFF 007ff000
01/04/2010 23:52:29,Server,Unknown,* COMCTL32 77530000 775C6FFF 00097000
01/04/2010 23:52:29,Server,Unknown,* comdlg32 762B0000 762F8FFF 00049000
01/04/2010 23:52:29,Server,Unknown,* SHLWAPI 77DA0000 77DF1FFF 00052000
01/04/2010 23:52:29,Server,Unknown,* pdh 72590000 725DBFFF 0004c000
01/04/2010 23:52:29,Server,Unknown,* WS2HELP 71BF0000 71BF7FFF 00008000
01/04/2010 23:52:29,Server,Unknown,* WS2_32 71C00000 71C16FFF 00017000
01/04/2010 23:52:29,Server,Unknown,* MSWSOCK 71B20000 71B60FFF 00041000
01/04/2010 23:52:29,Server,Unknown,* MSASN1 76190000 761A1FFF 00012000
01/04/2010 23:52:29,Server,Unknown,* CRYPT32 761B0000 76242FFF 00093000
01/04/2010 23:52:29,Server,Unknown,* GDI32 77C00000 77C48FFF 00049000
01/04/2010 23:52:29,Server,Unknown,* USER32 77380000 77410FFF 00091000
01/04/2010 23:52:29,Server,Unknown,* sqlos 344D0000 344D5FFF 00006000
01/04/2010 23:52:29,Server,Unknown,* Secur32 76F50000 76F62FFF 00013000
01/04/2010 23:52:29,Server,Unknown,* RPCRT4 77C50000 77CEEFFF 0009f000
01/04/2010 23:52:29,Server,Unknown,* ADVAPI32 7D1E0000 7D27BFFF 0009c000
01/04/2010 23:52:29,Server,Unknown,* MSVCP80 7C420000 7C4A6FFF 00087000
01/04/2010 23:52:29,Server,Unknown,* msvcrt 77BA0000 77BF9FFF 0005a000
01/04/2010 23:52:29,Server,Unknown,* MSVCR80 78130000 781CAFFF 0009b000
01/04/2010 23:52:29,Server,Unknown,* kernel32 77E40000 77F41FFF 00102000
01/04/2010 23:52:29,Server,Unknown,* ntdll 7C800000 7C8C1FFF 000c2000
01/04/2010 23:52:29,Server,Unknown,* sqlservr 01000000 037BEFFF 027bf000
01/04/2010 23:52:29,Server,Unknown,* MODULE BASE END SIZE
01/04/2010 23:52:29,Server,Unknown,*
01/04/2010 23:52:29,Server,Unknown,*
01/04/2010 23:52:29,Server,Unknown,* ex_handle_except encountered exception C0000005 - Server terminating
01/04/2010 23:52:29,Server,Unknown,*
01/04/2010 23:52:29,Server,Unknown,* 01/04/10 23:52:29 spid 1248
01/04/2010 23:52:29,Server,Unknown,* BEGIN STACK DUMP:
01/04/2010 23:52:29,Server,Unknown,*
01/04/2010 23:52:29,Server,Unknown,* *******************************************************************************
01/04/2010 23:52:29,Server,Unknown,***Stack Dump being sent to D:\Program Files\Microsoft SQL Server\MSSQL10.INSST4\MSSQL\LOG\SQLDump0013.txt
01/04/2010 23:52:29,Server,Unknown,**Dump thread - spid = 0<c/> EC = 0x00000000
01/04/2010 23:52:29,Server,Unknown,Using 'dbghelp.dll' version '4.0.5'
01/04/2010 23:52:29,Server,Unknown,SQL Server is terminating because of fatal exception c0000005. This error may be caused by an unhandled Win32 or C++ exception<c/> or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error<c/> restart the server (unless SQLAgent is configured to auto restart).
01/04/2010 23:52:29,Server,Unknown,Error: 17311<c/> Severity: 16<c/> State: 1.
01/04/2010 20:01:01,Backup,Unknown,Database backed up. Database: System_db<c/> creation date(time): 2009/12/05(09:10:29)<c/> pages dumped: 748<c/> first LSN: 1268:40:57<c/> last LSN: 1268:63:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=DISK: {'D:\SQLBackups\DBs\System_db\System_db_backup_2010_01_04_200003_5932848.bak'}). This is an informational message only. No user action is required.
All Replies
-
Tuesday, January 05, 2010 3:57 PMModeratorI'd recommend that you start by checking your server hardware, specifically the disk drives to see if you have a bad drive. Beyond that, contact Product Support Services and provide them the dump files that are being generated so that they can troubleshoot the issue further.
Jonathan Kehayias
http://sqlblog.com/blogs/jonathan_kehayias/
http://www.twitter.com/SQLSarg
http://www.sqlclr.net/
Please click the Mark as Answer button if a post solves your problem! -
Tuesday, January 05, 2010 7:23 PMc0000005 denotes ACCESS VIOLATION
If the memory accessed by SQL Server is not allocated to the process, then a C0000005 exception (Access Violation) will result.
From your description looks like you see a pattern (once in two days)... So drill down further and see whether you get this whenever a job executes or when you run particular query.
You can post the output of D:\Program Files\Microsoft SQL Server\MSSQL10.INSST4\MSSQL\LOG\SQLDump0013.txt which could help us further to diagnoise the issue.
Thanks! -
Tuesday, January 05, 2010 9:03 PMThe following is the dump
---------------------------------------------------------------------------------------
Current time is 23:52:29 01/04/10.
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 10.0.1600.22
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 E5520 @ 2.27GHz.
Bios Version is PTLTD - 6040000
PhoenixBIOS 4.0 Release 6.0
2 Intel x86 level 6, 2261 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 2.
Memory
MemoryLoad = 51%
Total Physical = 3839 MB
Available Physical = 1866 MB
Total Page File = 5214 MB
Available Page File = 3501 MB
Total Virtual = 2047 MB
Available Virtual = 283 MB
**Dump thread - spid = 0, EC = 0x00000000
***Stack Dump being sent to D:\Program Files\Microsoft SQL Server\MSSQL10.4\MSSQL\LOG\SQLDump0013.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 01/04/10 23:52:29 spid 1248
*
* ex_handle_except encountered exception C0000005 - Server terminating
*
*
* MODULE BASE END SIZE
* sqlservr 01000000 037BEFFF 027bf000
* ntdll 7C800000 7C8C1FFF 000c2000
* kernel32 77E40000 77F41FFF 00102000
* MSVCR80 78130000 781CAFFF 0009b000
* msvcrt 77BA0000 77BF9FFF 0005a000
* MSVCP80 7C420000 7C4A6FFF 00087000
* ADVAPI32 7D1E0000 7D27BFFF 0009c000
* RPCRT4 77C50000 77CEEFFF 0009f000
* Secur32 76F50000 76F62FFF 00013000
* sqlos 344D0000 344D5FFF 00006000
* USER32 77380000 77410FFF 00091000
* GDI32 77C00000 77C48FFF 00049000
* CRYPT32 761B0000 76242FFF 00093000
* MSASN1 76190000 761A1FFF 00012000
* MSWSOCK 71B20000 71B60FFF 00041000
* WS2_32 71C00000 71C16FFF 00017000
* WS2HELP 71BF0000 71BF7FFF 00008000
* pdh 72590000 725DBFFF 0004c000
* SHLWAPI 77DA0000 77DF1FFF 00052000
* comdlg32 762B0000 762F8FFF 00049000
* COMCTL32 77530000 775C6FFF 00097000
* SHELL32 7C8D0000 7D0CEFFF 007ff000
* ole32 77670000 777A8FFF 00139000
* OLEAUT32 77D00000 77D8AFFF 0008b000
* ODBC32 48890000 488CCFFF 0003d000
* odbcbcp 60950000 60955FFF 00006000
* VERSION 77B90000 77B97FFF 00008000
* USERENV 76920000 769E1FFF 000c2000
* WINMM 76AA0000 76ACCFFF 0002d000
* opends60 333E0000 333E6FFF 00007000
* NETAPI32 71C40000 71C96FFF 00057000
* BatchParser 520C0000 520DEFFF 0001f000
* comctl32 77420000 77522FFF 00103000
* odbcint 008C0000 008D6FFF 00017000
* psapi 76B70000 76B7AFFF 0000b000
* instapi10 00A40000 00A49FFF 0000a000
* sqlevn70 4F610000 4F80DFFF 001fe000
* rsaenh 68000000 68034FFF 00035000
* AUTHZ 76C40000 76C53FFF 00014000
* MSCOREE 52060000 520A5FFF 00046000
* msv1_0 76C90000 76CB6FFF 00027000
* cryptdll 60920000 6092BFFF 0000c000
* iphlpapi 76CF0000 76D09FFF 0001a000
* kerberos 61EE0000 61F38FFF 00059000
* schannel 76750000 76777FFF 00028000
* security 621B0000 621B3FFF 00004000
* dssenh 68100000 68126FFF 00027000
* hnetcfg 635A0000 635F9FFF 0005a000
* wshtcpip 71AE0000 71AE7FFF 00008000
* NTMARTA 77E00000 77E20FFF 00021000
* WLDAP32 76F10000 76F3DFFF 0002e000
* SAMLIB 7E020000 7E02EFFF 0000f000
* ntdsapi 63650000 63663FFF 00014000
* DNSAPI 76ED0000 76EF9FFF 0002a000
* winrnr 636B0000 636B6FFF 00007000
* rasadhlp 636D0000 636D4FFF 00005000
* xpsp2res 65160000 65424FFF 002c5000
* CLBCatQ 777B0000 77832FFF 00083000
* COMRes 65430000 654F5FFF 000c6000
* sqlncli10 65520000 6577AFFF 0025b000
* SQLNCLIR10 65790000 657C7FFF 00038000
* xpstar 657D0000 6581BFFF 0004c000
* SQLSCM 65830000 65838FFF 00009000
* ATL80 7C630000 7C64AFFF 0001b000
* xpstar 65850000 65875FFF 00026000
* odsole70 00700000 0070EFFF 0000f000
* DegCdonts 00720000 00725FFF 00006000
* MSVBVM60 65990000 65AE1FFF 00152000
* SXS 65F10000 65FCCFFF 000bd000
* cdosys 65FE0000 661E3FFF 00204000
* WININET 661F0000 6629AFFF 000ab000
* urlmon 662A0000 6634FFFF 000b0000
* INETCOMM 66350000 663FFFFF 000b0000
* MSOERT2 66400000 66422FFF 00023000
* inetres 66480000 6648DFFF 0000e000
* ACTIVEDS 76DF0000 76E23FFF 00034000
* adsldpc 76DC0000 76DE7FFF 00028000
* credui 76B80000 76BADFFF 0002e000
* ATL 76A80000 76A91FFF 00012000
* mlang 664F0000 66582FFF 00093000
* msoeacct 668D0000 66913FFF 00044000
* acctres 71830000 71841FFF 00012000
* msident 66920000 6692DFFF 0000e000
* msidntld 66940000 66945FFF 00006000
* PSTOREC 66960000 6696DFFF 0000e000
* ADMWPROX 66B00000 66B10FFF 00011000
* WSOCK32 71BB0000 71BB8FFF 00009000
* dbghelp 671A0000 672B4FFF 00115000
*
* Edi: 00000000:
* Esi: 00000000:
* Eax: 6319E484: 000042AC 00000000 00000000 77E4BEF7 00000000 00000000
* Ebx: 0000003F:
* Ecx: 6319EAEC: 00000000 00010007 00000000 00000000 6319EDD8 00000001
* Edx: 0000003F:
* Eip: 77E4BEF7: 10C2C95E 01093D00 840FC000 00000095 F29DE950 9090FFFF
* Ebp: 6319E4D4: 6319E51C 026AD543 000042AC 00000000 00000000 00000000
* SegCs: 0000001B:
* EFlags: 00000246:
* Esp: 6319E480: 6319E58C 000042AC 00000000 00000000 77E4BEF7 00000000
* SegSs: 00000023:
* *******************************************************************************
* -------------------------------------------------------------------------------
* Short Stack Dump
77E4BEF7 Module(kernel32+0000BEF7)
026AD543 Module(sqlservr+016AD543)
026ADD78 Module(sqlservr+016ADD78)
026AE713 Module(sqlservr+016AE713)
029B173B Module(sqlservr+019B173B)
77E761B7 Module(kernel32+000361B7)
77E792A3 Module(kernel32+000392A3) -
Tuesday, January 05, 2010 9:13 PMModerator
You can post the output of D:\Program Files\Microsoft SQL Server\MSSQL10.INSST4\MSSQL\LOG\SQLDump0013.txt which could help us further to diagnoise the issue.
The Dump Text file has essentially the same information as the ErrorLog entries about the dump, it is just specific to which mdmp file it belongs and exists even if the ErrorLog entries disappear from Log rollovers caused by manually calling sp_cycle_errorlog, or subsequent service restarts. The real information for troubleshooting a consistent dump is contained in the mdmp files that are generated in the Log directory, and you will need the Microsoft internal private symbols for SQL Server along with a detailed understanding of windbg to crawl the stack and find what actually lead to the exception occurring. This is Product Support should be contacted, in most cases, you aren't going to get enough with the public symbols to really identify the issue, a PSS member can open the dump file, or have an escalation engineer open it and further troubleshoot the root cause.
Thanks!
Jonathan Kehayias
http://sqlblog.com/blogs/jonathan_kehayias/
http://www.twitter.com/SQLSarg
http://www.sqlclr.net/
Please click the Mark as Answer button if a post solves your problem! -
Wednesday, January 06, 2010 1:41 PMHow often does this happen?
From the snippets provided so far, I have the following observation:
1. You have COM objects active on the system
2. You are also using CDO to send out emails. It might be that sp_OAcreate is being used for sending the mails using CDO.
The first thing to do for an Access Violation issue would be to scour through the System/Application logs (as suggested by Jon) and find out if there are any system level issues.
Then check if you can move mail sending component out of SQL Server's memory space. Also, you can evaluate the use of DB Mail instead of using CDO to send mail.
Ref: http://support.microsoft.com/kb/243428
Or you could always open a case with Microsoft CSS and the support engineers can assist you with the RCA.
This posting is provided "AS IS" with no warranties, and confers no rights. My Blog: Troubleshooting SQL -
Wednesday, January 06, 2010 1:48 PMModeratorIt appears you are running the original RTM version of SQL 2008, 10.0.1600.22. Before contacting MS Support, I would suggest you install the current SP and cumulative update to see if the problem is already fixed.
-
Wednesday, January 06, 2010 1:55 PM
It appears you are running the original RTM version of SQL 2008, 10.0.1600.22. Before contacting MS Support, I would suggest you install the current SP and cumulative update to see if the problem is already fixed.
Oh now that's a nice spot, well done chap.
John Sansom | Blog: www.johnsansom.com | SQL Server DBA at Expedia, consultant with Santech Solutions -
Wednesday, January 06, 2010 5:58 PMModerator
It appears you are running the original RTM version of SQL 2008, 10.0.1600.22. Before contacting MS Support, I would suggest you install the current SP and cumulative update to see if the problem is already fixed.
While I can't argue with this recommendation, I really doubt that it has anything to do with the actual crashes that are occuring. I keep up with most of the fixes and bugs in 2005 and 2008 through the RSS feeds for KB articles and I've never seen anything remotely familiar to this. However, being on the latest Service Pack after testing is always a good recommendation.
Jonathan Kehayias
http://sqlblog.com/blogs/jonathan_kehayias/
http://www.twitter.com/SQLSarg
http://www.sqlclr.net/
Please click the Mark as Answer button if a post solves your problem! -
Wednesday, January 06, 2010 6:18 PMThank you. I will try the Service Packs and let you know.
-
Thursday, January 07, 2010 8:30 AMModeratorHi STABS,
I have found an internal record that indicates this should be a known issue, and has been solved in cumulative update 4 for SQL Server 2008 Service Package 1.
The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
Jin Chen - MSFT -
Thursday, January 07, 2010 1:40 PMModerator
Hi STABS,
I have found an internal record that indicates this should be a known issue, and has been solved in cumulative update 4 for SQL Server 2008 Service Package 1.
The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
Jin Chen - MSFT
Jin,
Which one of the changes in that hot fix are associated with this fix, and why doesn't the documentation reflect that, or is this an undocumented fix? I can take the issue up separately with Microsoft, but if there is a crash causing bug fixed in an update, it should have been documented in the CU notes properly. Under what scenarios would the above crash actually be triggered on a server that doesn't have CU4 applied to it?
Since there are other known issues with applying CU4 to SP1 on standalone machines, I would recommend CU5 which would have any updates in CU4 but has yet to contain the issues listed for CU4.
In addition the link you provided is incomplete, the domain information for blogs.msdn.com is not included, it is only a relative path:
http://blogs.msdn.com/sqlreleaseservices/archive/2009/09/22/cumulative-update-4-for-sql-server-2008-sp1.aspx
Jonathan Kehayias
http://sqlblog.com/blogs/jonathan_kehayias/
http://www.twitter.com/SQLSarg
http://www.sqlclr.net/
Please click the Mark as Answer button if a post solves your problem! -
Friday, January 08, 2010 9:05 AMModeratorHi Jonathan,
The document is published with the confidentiality of MSInternal, and the document has mentioned the issue is fixed in Cumulative Update 4 for SQL Server 2008 Service Pack 1.
I will try to connect the Product Team to check the issue.
Sorry for my mistake, cumulative update 4 for SQL Server 2008 SP1 is available on:
http://support.microsoft.com/kb/973602
However, as you mentioned, CU5 has fixed other known issues. I agree with you.
Cumulative update 5 for SQL Server 2008 SP1 is available on:
http://support.microsoft.com/kb/975977
Best regards,
Jin Chen
Jin Chen - MSFT -
Friday, January 08, 2010 2:33 PMI appreciate all your help.
We did the cumulative update 4 for SQL Server 2008 SP1 yesterday and still the database server stopped with the
same error. I do not see any mention of this error in Update 5 . -
Friday, January 08, 2010 5:02 PMIf this is very frequent, then I would suggest referring the points from my last post or opening a support ticket with CSS. The error text from the Errorlog is not sufficient enought to determine the root cause without analyzing the dump file.
This posting is provided "AS IS" with no warranties, and confers no rights. My Blog: Troubleshooting SQL -
Wednesday, January 13, 2010 5:09 PM
I opened a ticket with MS and they anlysed the dump and the crash is caused by MSVBVM60.dll
1) Update the MSVBVM60.dll to latest version. I checked our server and we have a version of 6.0.97.82 of the msvbvm60.dll and they suggest to update it like below from a licensed version of the Vista machine. In my XP pro machine I have the version 6.0.98.2.
2) Modify the stored procedure to run the dll in its own process
http://msdn2.microsoft.com/en-us/library/aa238863(SQL.80).aspx
3) Change the mail component to use database mail.
So I will be trying the above steps one by one- Marked As Answer by Jinchun ChenMicrosoft Employee, Moderator Monday, February 08, 2010 1:48 AM
-
Friday, February 12, 2010 2:35 PMUpdating the MSVBVM60.dll to latest version seem to fix the problem. The issue didn't happen again as of today.
-
Monday, October 22, 2012 12:42 PM
Iam getting the same error on our Server, and I was wondering
- How can I check the current version of msvbvm60.dll, and how can I update this?
- Currently I do not have any Service Packs installed for SQL Server, Does Installing Service Pack resolve this issue?
Thanks
-
Monday, October 22, 2012 1:39 PM
Hi, I assume you're talking about the same problem you posted here. In your case msvbvm60.dll is not loaded in SQL address space so the issue might be different than this one. Please follow the suggestions provided on your own post.Iam getting the same error on our Server, and I was wondering
- How can I check the current version of msvbvm60.dll, and how can I update this?
- Currently I do not have any Service Packs installed for SQL Server, Does Installing Service Pack resolve this issue?
Thanks
This posting is provided “AS IS” with no warranties, and confers no rights.
If this reply answers your question, please mark it as Answered for others to find it easily.
If this reply help you resolving the problem, please vote the post as Helpful.
