{"id":229102,"date":"2020-03-05T00:55:59","date_gmt":"2020-03-04T23:55:59","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=229102"},"modified":"2020-03-06T08:11:58","modified_gmt":"2020-03-06T07:11:58","slug":"sql-server-2019-cu-2-killt-den-sql-server-agenten","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2020\/03\/05\/sql-server-2019-cu-2-killt-den-sql-server-agenten\/","title":{"rendered":"SQL Server 2019 CU 2 killt den SQL-Server-Agenten"},"content":{"rendered":"<p><img decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline;\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2015\/01\/Stop.jpg\" align=\"left\" \/>[<a href=\"https:\/\/borncity.com\/win\/2020\/03\/05\/sql-server-2019-cu-2-breaks-sql-server-agent\/\" target=\"_blank\" rel=\"noopener noreferrer\">English<\/a>]B\u00f6se \u00dcberraschung f\u00fcr Administratoren des Microsoft SQL Server 2019, die das kumulative Update 2 vom 13. Februar 2020 installieren. Dieses kann den SQL-Server-Agenten abschie\u00dfen.<\/p>\n<p><!--more--><\/p>\n<h2>Cumulative Update 2 f\u00fcr SQL Server 2019<\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vg08.met.vgwort.de\/na\/17f1c85d8ff74794adb3640f390e01e5\" alt=\"\" width=\"1\" height=\"1\" \/>Das <a href=\"https:\/\/support.microsoft.com\/en-gb\/help\/4536075\/cumulative-update-2-for-sql-server-2019\" target=\"_blank\" rel=\"noopener noreferrer\">Cumulative Update 2<\/a> f\u00fcr den SQL Server 2019 steht sowohl f\u00fcr Linux als auch f\u00fcr SQL Server 2019 unter Windows zur Verf\u00fcgung. Es wurde wohl zum vom 13. Februar 2020 freigegeben und enth\u00e4lt Fixes, die nach dem initialen Release von SQL Server 2019 erschienen sind. Zudem werden die SQL Server und Analysis Services-Komponenten auf die nachfolgenden Builds angehoben:<\/p>\n<ul>\n<li><strong>SQL Server: <\/strong>Version 15.0.4013.40, File Version: 2019.150.4013.40<\/li>\n<li><strong>Analysis Services:<\/strong> Version 15.0.34.1, File Version: 2018.150.34.1<\/li>\n<\/ul>\n<p>Microsoft empfiehlt die fortlaufende, proaktive Installation von CUs, sobald diese gem\u00e4\u00df den im <a href=\"https:\/\/support.microsoft.com\/en-gb\/help\/4536075\/cumulative-update-2-for-sql-server-2019#hfi\" target=\"_blank\" rel=\"noopener noreferrer\">KB-Artikel<\/a> angegeben Richtlinien verf\u00fcgbar sind.<\/p>\n<h2>CU2 brickt SQL-Server-Agenten<\/h2>\n<p>Der SQL Server Agent ist f\u00fcr die Ausf\u00fchrung von Auftr\u00e4gen wie Backups und andere Wartungsaufgaben verantwortlich und kann mit\u00a0 T-SQL f\u00fcr diverse Zwecke eingesetzt werden. Bereits kurz nach Freigabe des CU2 meldeten sich Nutzer <a href=\"https:\/\/dba.stackexchange.com\/questions\/260190\/sql-server-agent-fails-after-installing-sql-server-2019-cu2\" target=\"_blank\" rel=\"noopener noreferrer\">im DBA-Forum von StackExchange<\/a>.<\/p>\n<blockquote><p>SQL Server Agent fails after installing SQL Server 2019 CU2<\/p>\n<p>After installing CU2 our SQL server agent randomly stops working. If you go to check on the status of the agent by opening Job Activity Monitor, it comes up blank for a while then throws an error:<\/p>\n<blockquote><p>Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)<\/p>\n<p>For help, click: <a href=\"https:\/\/go.microsoft.com\/fwlink?ProdName=Microsoft%20SQL%20Server&amp;LinkId=20476\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/go.microsoft.com\/fwlink?ProdName=Microsoft%20SQL%20Server&amp;LinkId=20476<\/a><\/p>\n<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212; ADDITIONAL INFORMATION:<\/p>\n<p>An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)<\/p>\n<hr \/>\n<p>A severe error occurred on the current command. The results, if any, should be discarded. (Microsoft SQL Server, Error: 0)<\/p>\n<p>For help, click: <a href=\"http:\/\/go.microsoft.com\/fwlink?ProdName=Microsoft%20SQL%20Server&amp;ProdVer=15.00.4013&amp;EvtSrc=MSSQLServer&amp;EvtID=0&amp;LinkId=20476\" target=\"_blank\" rel=\"noopener noreferrer\">http:\/\/go.microsoft.com\/fwlink?ProdName=Microsoft%20SQL%20Server&amp;ProdVer=15.00.4013<br \/>\n&amp;EvtSrc=MSSQLServer&amp;EvtID=0&amp;LinkId=20476<\/a><\/p><\/blockquote>\n<p>Any clue what could be causing this?<\/p><\/blockquote>\n<p>Andere Nutzer wiesen dann auf <a href=\"https:\/\/feedback.azure.com\/forums\/908035-sql-server\/suggestions\/39754837-ssms-18-4-sqlserver-2019-cu2-object-explorer-fails\" target=\"_blank\" rel=\"noopener noreferrer\">diesen Feedback-Eintrag<\/a> von Azure hin, und Microsoft hat das dann untersucht. Kurze Zeit sp\u00e4ter gab es dann die folgende Information:<\/p>\n<blockquote><p>The bug introduced in CU2 with xp_sqlagent_enum_jobs is now understood and a fix will ship in CU3. Meanwhile, if you're hitting this issue, revert back to CU1. We apologize for any inconvenience we may have caused.<\/p><\/blockquote>\n<p>Der Bug in CU2 soll in CU3 behoben werden. Microsoft empfiehlt Betroffenen auf CU1 zur\u00fcck zu gehen. Inzwischen ist <a href=\"https:\/\/support.microsoft.com\/en-gb\/help\/4536075\/cumulative-update-2-for-sql-server-2019#hfi\" target=\"_blank\" rel=\"noopener noreferrer\">im KB-Artikel<\/a> die am 4. M\u00e4rz 2020 nachgetragene Best\u00e4tigung des Bugs zu finden:<\/p>\n<blockquote><p>Known issue<\/p>\n<p>There is a known issue with SQL Server Agent in SQL Server 2019 CU2. This will be fixed in the next CU release (SQL Server 2019 CU3).<\/p>\n<ul>\n<li>If you are using SQL Server 2019 SQL Server Agent, it is advised to skip this CU upgrade, and wait for SQL Server 2019 CU3.<\/li>\n<li>If you have already applied SQL Server 2019 CU2 and are experiencing issues with SQL Server Agent, please revert to SQL Server 2019 CU1.<\/li>\n<\/ul>\n<\/blockquote>\n<p>Weitere Informationen sind dem <a href=\"https:\/\/support.microsoft.com\/en-gb\/help\/4536075\/cumulative-update-2-for-sql-server-2019#hfi\" target=\"_blank\" rel=\"noopener noreferrer\">KB-Artikel<\/a> zu entnehmen. Irgend jemand von euch von diesem Problem betroffen? (<a href=\"https:\/\/www.theregister.co.uk\/2020\/03\/04\/sql_server_2019_cu2_broken\/\" target=\"_blank\" rel=\"noopener noreferrer\">via<\/a>)<\/p>\n","protected":false},"excerpt":{"rendered":"<p>[English]B\u00f6se \u00dcberraschung f\u00fcr Administratoren des Microsoft SQL Server 2019, die das kumulative Update 2 vom 13. Februar 2020 installieren. Dieses kann den SQL-Server-Agenten abschie\u00dfen.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7459,185],"tags":[24,2088,4315],"class_list":["post-229102","post","type-post","status-publish","format-standard","hentry","category-software","category-update","tag-problem","tag-sql-server","tag-update"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/229102","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/comments?post=229102"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/229102\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=229102"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=229102"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=229102"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}