{"id":1964,"date":"2020-06-07T11:26:32","date_gmt":"2020-06-07T11:26:32","guid":{"rendered":"http:\/\/www.theSQLReport.com\/?p=1964"},"modified":"2020-06-07T11:26:32","modified_gmt":"2020-06-07T11:26:32","slug":"there-are-no-sql-server-instances-or-shared-features-that-can-be-updated-on-this-computer","status":"publish","type":"post","link":"https:\/\/www.theSQLReport.com\/?p=1964","title":{"rendered":"There Are No SQL Server Instances Or Shared Features That Can Be Updated On This Computer"},"content":{"rendered":"

Someone asked me to look at this error when applying a cumulative update on an instance of SQL Server 2016.\u00a0\u00a0 It was a strange error because I was able to connect to the SQL Server instance on that server.\u00a0 The error “there are no SQL Server instances or shared features that can be updated on this computer.”<\/p>\n

\"there<\/a><\/p>\n

After I clicked on the OK button on the pop-up box, I clicked on the MSSQLSERVER check box in the middle panel.\u00a0 The “Description” panel on the right populated with helpful information.\u00a0 This patch thinks that SQL Server has no service packs applied.\u00a0 When I queried in SQL Server instance,\u00a0 it was showing and see that the instance was at SP2-CU4.<\/p>\n

\"clicked<\/a><\/p>\n

When I did a search “13.1.4001.0” in the Windows Registry, I found that a developer had added Reporting Services to patched SQL Server instance, with out applying any Service Packs to the Reporting Services.\u00a0 I had to re-run the install for Service Pack 2, then I was able to apply the cumulative update.<\/p>\n

\"search<\/a><\/p>\n

Final Note:\u00a0 if you should encounter the error “there are no SQL Server instances or shared features that can be updated on this computer”, recommend applying the last Service Pack to see what components that have not been updated are keeping from the cumulative update from applying.<\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Someone asked me to look at this error when applying a cumulative update on an instance of SQL Server 2016.\u00a0\u00a0 It was a strange error because I was able to … Continue Reading →<\/a><\/p>\n","protected":false},"author":1,"featured_media":1967,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[185,182],"class_list":["post-1964","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-sql-server","tag-cumulative-update","tag-service-pack"],"_links":{"self":[{"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=\/wp\/v2\/posts\/1964"}],"collection":[{"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1964"}],"version-history":[{"count":8,"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=\/wp\/v2\/posts\/1964\/revisions"}],"predecessor-version":[{"id":2111,"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=\/wp\/v2\/posts\/1964\/revisions\/2111"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=\/wp\/v2\/media\/1967"}],"wp:attachment":[{"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1964"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1964"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.theSQLReport.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1964"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}