![]() ![]() It's possible that the service account doesn't have privs to write to the system event log, but I've also tried setting up my audit to use the application log or a folder, and there's been no change. There's a joke in here somewhere about ring buffers and going in circles. You can also query sys.dm_os_ring_buffers where ring_buffer_type = 'RING_BUFFER_XE_LOG'. For more information, see the SQL Server error log. Without a filter, I get an XML message, with these salient points: Record type: RING_BUFFER_EXCEPTIONĪccording to sysmessages, this error code means: Audit '%.*ls' failed to %.*ls. Well, there are a couple hundred messages, but none are new and there's no change after each attempt to start auditing. OK, how about that dm_os_ring_buffers table? When filtered for the ring_buffer_type mentioned in the original error, I get nothing. The 65552 number is just an auto-incrementing value, not an error code. You can also query sys.dm_os_ring_buffers where ring_buffer_type = 'RING_BUFFER_XE_LOG'.Ĭhecking the error log, I see: Audit: Server Audit: 65552, Initialized and Assigned State: START_FAILED I've created an AUDIT and an associated AUDIT SPECIFICATION, but when I try to enable the audit, I get this message: Msg 33222, Level 16, State 1, Line 13Īudit 'X' failed to start. ![]() I'm setting up auditing on my MS SQL 2014 server. Where can I get information about the audit process failing to start?
0 Comments
Leave a Reply. |