Symptoms
Assume that you run Microsoft SQL Server 2016 and 2017 and haveĀ c2 audit mode enabled. After you install Service Pack 2 (SP2) on the server, the SQL Service shuts down, and you receive an error message that resembles the following:
Date time spid54 Error: 566, Severity: 21, State: 1.
Date time spid54 An error occurred while writing an audit trace. SQL Server is shutting down. Check and correct error conditions such as insufficient disk space, and then restart SQL Server. If the problem persists, disable auditing by starting the server at the command prompt with the "-f" switch, and using SP_CONFIGURE.
Date time spid54 SQL Server shutdown has been initiated
Date time SQL Trace was stopped due to server shutdown. Trace ID = '2'. This is an informational message only; no user action is required.
Date time spid54 Error: 19099, Severity: 16, State: 1.
Date time spid54 Trace ID '1' was stopped because of an error. Cause: 16534123(failed to retrieve text for this error. Reason: 317). Restart the trace after correcting the problem.
Date time spid54 Audit: Server Audit: 65536, State changed from: STARTED to: SHUTTING_DOWN
Resolution
A fix for this issue is included in the following cumulative updates for SQL Server:
Cumulative Update 11 for SQL Server 2017
Cumulative Update 3 for SQL Server 2016 Service Pack 2.
About SQL Server builds
Each new build for SQL Server 2016 contains all the hotfixes and security fixes that were in the previous build. We recommend that you install the latest builds for SQL Server:
Workaround
To work around this issue, uninstall Service Pack 2 for SQL Server 2016.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the terminology Microsoft uses to describe software updates.