Assume that you have a regularly scheduled maintenance job to cycle the error log files without stopping and starting the server in Microsoft SQL Server 2014 or 2016.

For example, the maintenance job may resemble the following:

USE msdb ;  

EXEC dbo.sp_cycle_agent_errorlog ;  

In this scenario, the maintenance job doesn't run, and you receive error messages that resemble the following:

Msg 22022, Level 16, State 1, Line line_number
SQLServerAgent Error: 32.
The process cannot access the file because it is being used by another process


This problem is fixed in the following cumulative updates for SQL Server:

Cumulative Update 22 for SQL Server 2017

Cumulative Update 4 for SQL Server 2016 Service Pack 2

Cumulative Update 4 for SQL Server 2014 SP3

Cumulative Update 18 for SQL Server 2014 SP2

About SQL Server builds

Each new build for SQL Server contains all the hotfixes and security fixes that were in the previous build. We recommend that you install the latest build for SQL Server:

Latest cumulative update for SQL Server 2017

latest build for SQL Server 2016

Latest cumulative update for SQL Server 2014


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


Learn about the terminology Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!