crash dump when creating database auditing specification - by Frans van der Geer

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 700304 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 11/10/2011 3:05:05 AM
Access Restriction Public

Description

When exploring the new auditing enhancements I ran into a crash dump.

(12DC:1534) 11/10/11 11:37:51, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges () completed with status (00000514)
(12DC:1534) 11/10/11 11:37:51, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(12DC:1534) 11/10/11 11:37:51, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, 	Parameter 1: 688
(12DC:1534) 11/10/11 11:37:51, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, 	Parameter 2: 0
(12DC:1534) 11/10/11 11:37:51, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, 	Parameter 3: 0:0
(12DC:1534) 11/10/11 11:37:51, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, 	Parameter 4: 00D61B60
(12DC:1534) 11/10/11 11:37:51, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(12DC:1534) 11/10/11 11:37:51, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 688
(12DC:1534) 11/10/11 11:37:51, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
(12DC:1534) 11/10/11 11:37:51, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
(12DC:1534) 11/10/11 11:37:51, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
(12DC:1534) 11/10/11 11:37:51, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00D61B60
(12DC:1534) 11/10/11 11:37:51, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
(12DC:1534) 11/10/11 11:37:51, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
(12DC:1534) 11/10/11 11:37:51, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
(12DC:1534) 11/10/11 11:37:51, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
(12DC:1534) 11/10/11 11:37:51, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
(12DC:1534) 11/10/11 11:37:51, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
Sign in to post a comment.
Posted by Microsoft on 12/23/2011 at 10:23 AM
Hi Franz,

I just wanted to let you know that this bug will be fixed in the first service pack for SQL2012.

Thanks,
Il-Sung.
Posted by Microsoft on 11/10/2011 at 8:09 PM
Hi Franz,

Thank you very much for bringing this issue to our attention. After investigation, we acknowledge that this is bug in our code and we will fix it as soon as possible. Unfortunatley, it's too late to make the change for SQL Server 2012 RTM (the code is already locked down) but we will make sure the fix is available at the first opporutnity afterwards.

Please note that, for now, if you don't add the AUDIT_CHANGE_GROUP to your audit spec, you will be able to shut down the audit and avoid the AV. Otherwise, you will have to start the server with the "-f" flag (minimal configuration) and then you will be able to shut down the audit.

Thanks,
Il-Sung.