{"id":2305,"date":"2016-09-24T23:44:01","date_gmt":"2016-09-24T21:44:01","guid":{"rendered":"http:\/\/blog.hosebei.ch\/?p=2305"},"modified":"2016-09-24T23:44:01","modified_gmt":"2016-09-24T21:44:01","slug":"configmgr-in-place-upgrade-of-sql-from-2012-to-2016","status":"publish","type":"post","link":"https:\/\/blog.hosebei.ch\/?p=2305","title":{"rendered":"ConfigMgr &#8211; In-Place Upgrade of SQL from 2012 to 2016"},"content":{"rendered":"<p>Hi,<br \/>\ntoday I did an In-Place Upgrade of my SQL Installation from SQL 2012 to the 2016 Release which is also supported by System Center Configuration Manager Current Branch (1606).<br \/>\nEverything went fine except the Report Service, I received the following errors within the upgrade:<br \/>\n<code>Action required:<br \/>\nThe upgrade process for SQL Server failed. Use the following information to resolve the error, and then repair your installation by using this command line: setup \/action=repair \/instancename=MSSQLSERVER<\/p>\n<p>Feature failure reason:<br \/>\nAn error occurred during the setup process of the feature.<\/p>\n<p>Error details:<br \/>\n\u00a7 Error installing SQL Server Reporting Services<br \/>\nA HTTPS sertificate is not configured on the Web site.<br \/>\nError code: 0x80131500<br \/>\nVisit http:\/\/go.microsoft.com\/fwlink?LinkId=20476&amp;ProdName=Microsoft+SQL+Server&amp;EvtSrc=setup.rll&amp;EvtID=50000&amp;ProdVer=13.0.1601.5&amp;EvtType=0x589E8944%400x8285294C&amp;EvtType=0x589E8944%400x8285294C to get help on troubleshooting.<\/p>\n<p>TITLE: Microsoft SQL Server 2016 Setup<br \/>\n------------------------------<\/p>\n<p>The following error has occurred:<\/p>\n<p>The Report Server WMI provider cannot create the virtual directory. This error occurs when you call SetVirtualDirectory and the UrlString is already reserved. To continue, clear all URL reservations by calling RemoveURL and then try again.<\/p>\n<p>For help, click: http:\/\/go.microsoft.com\/fwlink?LinkID=20476&amp;ProdName=Microsoft%20SQL%20Server&amp;EvtSrc=setup.rll&amp;EvtID=50000&amp;ProdVer=13.0.1601.5&amp;EvtType=0x589E8944%25400x9A8ECB73<\/code><\/p>\n<p>And within ConfigMgr, the srsrp.log showed up with the following errors:<br \/>\n<a href=\"http:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/09\/sql_update01.png\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/09\/sql_update01.png?w=300\" alt=\"sql_update01\" width=\"300\" height=\"121\" class=\"aligncenter size-medium wp-image-2306\" srcset=\"https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/09\/sql_update01.png 924w, https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/09\/sql_update01-300x121.png 300w, https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/09\/sql_update01-768x309.png 768w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a><br \/>\n<!--more--><\/p>\n<p><code>The request failed with HTTP status 503: Service Unavailable.\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:13:20\t5420 (0x152C)<br \/>\n(!) SRS not detected as running\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:13:20\t5420 (0x152C)<br \/>\nSTATMSG: ID=7403 SEV=E LEV=M SOURCE=\"SMS Server\" COMP=\"SMS_SRS_REPORTING_POINT\" SYS=hosebeisccm01.deheim.hosebei.ch SITE=S01 PID=2808 TID=5420 GMTDATE=Sa Sep 24 19:13:20.480 2016 ISTR0=\"hosebeisccm01.deheim.hosebei.ch\" ISTR1=\"\" ISTR2=\"\" ISTR3=\"\" ISTR4=\"\" ISTR5=\"\" ISTR6=\"\" ISTR7=\"\" ISTR8=\"\" ISTR9=\"\" NUMATTRS=0\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:13:20\t5420 (0x152C)<br \/>\nFailures reported during periodic health check by the SRS Server hosebeisccm01.deheim.hosebei.ch.\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:13:20\t5420 (0x152C)<br \/>\nRegistry change\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:13:20\t5420 (0x152C)<br \/>\nWaiting for changes for 1 minutes\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:13:20\t5420 (0x152C)<br \/>\nTimed Out...\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:14:20\t5420 (0x152C)<br \/>\nSet configuration\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:14:20\t5420 (0x152C)<br \/>\nCheck state\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:14:20\t5420 (0x152C)<br \/>\nCheck server health.\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:14:20\t5420 (0x152C)<br \/>\nSuccessfully created srsserver\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:14:20\t5420 (0x152C)<br \/>\nReporting Services URL from Registry [https:\/\/hosebeisccm01.deheim.hosebei.ch\/ReportServer\/ReportService2005.asmx]\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:14:20\t5420 (0x152C)<br \/>\nThe request failed with HTTP status 503: Service Unavailable.\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:14:20\t5420 (0x152C)<br \/>\n(!) SRS not detected as running\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:14:20\t5420 (0x152C)<br \/>\nFailures reported during periodic health check by the SRS Server hosebeisccm01.deheim.hosebei.ch.\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:14:20\t5420 (0x152C)<br \/>\nRegistry change\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:14:20\t5420 (0x152C)<br \/>\nWaiting for changes for 1 minutes\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:14:20\t5420 (0x152C)<br \/>\nTimed Out...\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:15:21\t5420 (0x152C)<br \/>\nSet configuration\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:15:21\t5420 (0x152C)<br \/>\n<\/code><\/p>\n<p>After some research it seemed to be the best option to go as follows:<br \/>\n1. Uninstall Report Services<br \/>\n2. Reboot Server<br \/>\n3. Reinstall Report Services<br \/>\n4. Configure Report Services<br \/>\n5. Reinstall the Report Service Role in ConfigMgr<\/p>\n<p>But this did not solve the issue, and the srsrp.log did show another error:<br \/>\n<a href=\"http:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/09\/sql_update02.png\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/09\/sql_update02.png?w=300\" alt=\"sql_update02\" width=\"300\" height=\"69\" class=\"aligncenter size-medium wp-image-2308\" srcset=\"https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/09\/sql_update02.png 896w, https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/09\/sql_update02-300x69.png 300w, https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/09\/sql_update02-768x177.png 768w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a><br \/>\n<code><br \/>\nSet configuration\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:35:25\t5348 (0x14E4)<br \/>\nCheck state\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:35:25\t5348 (0x14E4)<br \/>\nCheck server health.\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:35:25\t5348 (0x14E4)<br \/>\nSuccessfully created srsserver\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:35:25\t5348 (0x14E4)<br \/>\nReporting Services URL from Registry [https:\/\/hosebeisccm01.deheim.hosebei.ch\/ReportServer\/ReportService2005.asmx]\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:35:25\t5348 (0x14E4)<br \/>\nSystem.Web.Services.Protocols.SoapException: The feature: \"Scale-out deployment\" is not supported in this edition of Reporting Services. ---&gt; Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: \"Scale-out deployment\" is not supported in this edition of Reporting Services.~   at Microsoft.ReportingServices.Library.ReportingService2005Impl.GetItemType(String Item, ItemType&amp; Type)~   at Microsoft.ReportingServices.WebServer.ReportingService2005.GetItemType(String Item, ItemTypeEnum&amp; Type)\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:35:37\t5348 (0x14E4)<br \/>\n(!) SRS not detected as running\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:35:37\t5348 (0x14E4)<br \/>\nFailures reported during periodic health check by the SRS Server hosebeisccm01.deheim.hosebei.ch.\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:35:37\t5348 (0x14E4)<br \/>\nRegistry change\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:35:37\t5348 (0x14E4)<br \/>\nWaiting for changes for 1 minutes\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:35:37\t5348 (0x14E4)<br \/>\nTimed Out...\tSMS_SRS_REPORTING_POINT\t24.09.2016 21:36:37\t5348 (0x14E4)<br \/>\n<\/code><\/p>\n<p>I then opened the &#8220;Report Services Configuration Manager&#8221; Console and simply deleted the encryption content:<br \/>\n<a href=\"http:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/09\/sql_update03.png\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/09\/sql_update03.png?w=300\" alt=\"sql_update03\" width=\"300\" height=\"257\" class=\"aligncenter size-medium wp-image-2309\" srcset=\"https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/09\/sql_update03.png 972w, https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/09\/sql_update03-300x257.png 300w, https:\/\/blog.hosebei.ch\/wp-content\/uploads\/2016\/09\/sql_update03-768x659.png 768w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a><\/p>\n<p>Afterwards the Report Services were installed from ConfigMgr successfully, even my self-created Reports were back there.<\/p>\n<p>Hope this helps.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Hi, today I did an In-Place Upgrade of my SQL Installation from SQL 2012 to the 2016 Release which is also supported by System Center Configuration Manager Current Branch (1606). Everything went fine except the Report Service, I received the following errors within the upgrade: Action required: The upgrade process for SQL Server failed. Use [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[15,19,20,36],"tags":[59],"class_list":["post-2305","post","type-post","status-publish","format-standard","hentry","category-configmgr","category-general","category-homelab","category-setup","tag-rsoperationnotsupported"],"_links":{"self":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts\/2305","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2305"}],"version-history":[{"count":0,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts\/2305\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2305"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2305"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2305"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}