Assume that you use Microsoft SQL Server 2019. You notice that you cannot expand the jobs node in SQL Server Management Studio (SSMS) Object explorer, view job status in Job Activity Monitor, view job details, or make changes to jobs. The program may stop responding, or you may receive error messages that resemble the following:
Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
A severe error occurred on the current command. The results, if any, should be discarded. (.Net SqlClient Data Provider)
Additionally, you notice that SQLAGENT.EXE shows elevated use of CPU time on one or more processors. Tracking the activity within SQL Server may reveal that the queries against xp_sqlagent_enum_jobs do not return any information within the time-out period.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This issue is fixed in the following cumulative update for SQL Server:
About cumulative updates for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
To work around the issue, you can use the following methods:
- Avoid changing the jobs which have a next run timestamp that is less than current timestamp.
- Use CU1 for SQL Server 2019.