Windows 10: SSRS 2019 not getting migrated from Sql 2016

Hi team,I am unable to migrated SSRS 2016 to SSRS 2019 getting below errorswhile restoring encryption key getting this error Microsoft.ReportingServices.WmiProvider.WMIProviderException: An error occurred when attempting to connect to the report server remote procedure call RPC end point. Verify that the Report Server Windows service is running, and then retry the operation. ---> System.Runtime.InteropServices.COMException: The RPC server is not listening. Exception from HRESULT: 0x800706B3 --- End of inner exception stack trace --- at Microsoft.ReportingServices.WmiProvider.RSWmi

:)

 

SQL server 2019 upgrade checkpoints from SQL 2016

What are the pros and cons while migrating from sql 2016 to 2019.

 

SQL server 2019 upgrade checkpoints from SQL 2016

Hello Meraj,

I am Jaspreet Singh an independent advisor.

The main Pro of upgrading to SQL server 2019 will be the long term support which 2016 will be getting to the end of in 2021 (mainstream support ending)

Other Pro will be that 2019 update brought a bunch of new cutting edge features that have since been started to be used.

here is a comparison of these new features in 2019 with availability among 2016 and 2017 :

https://www.microsoft.com/en-in/sql-server/sql-...

But since most of these features are new 2019 update has all the issues that plague new releases and you should be ready to keep the updates rolling because you will be getting a lot of patches on pretty significant issues. Alongside that since the update has
been relatively new you will have to work out issues popping up on your own.

This blog summarizes it pretty well :
https://www.brentozar.com/archive/2019/01/which...

Disclaimer: this is a non Microsoft website. The page appears to be providing accurate and safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (potentially unwanted products). Throughly research any product
advertised on the site before you decide to download and install it

 

CASE # 30643426 - SQL 2016 SSIS/SSRS not recognizing Oracle 19c 64 Bit Client

We have opened a case with Microsoft, but are not getting any response on this. How do we get Microsoft to actually pay attention to a Support Ticket?

We have several SQL 2012 servers with SSIS/SSRS on them, using Oracle Clients for connecting to Oracle DBs. As 2012 is going out of support, we need to migrate these to SQL 2016 SSIS/SSRS. While we can get 2012 to properly reference and use the installed Oracle Clients (12.2 and 19c), SQL 2016 does not seem to even recognize that an Oracle Client is even installed on the server.

We have installed the Oracle 19c 64 Bit Client on the server. Also, the additional commands were run to load several Oracle component references into the GAC on the server (this is what typically fixed the issue with SQL 2012). In particular, we need to use the "Oracle Database" type of connection for establishing the connection to an Oracle DB, as this apparently references the .Net ODAC drivers for Oracle. We have a large number of reports that were built using this connection type, but cannot get these to work on the 2016 server.

Below are the commands we use to load the Oracle components to the GAC. These work when done on a SQL 2012 server, but don't seem to do what is needed for SQL 2016 to be able to use the installed Oracle 19c Client.

D:\SrvApps\Oracle\product\19.0.0\client_1\odp.net\bin\4\OraProvCfg.exe /action:gac /providerpath:"D:\SrvApps\Oracle\product\19.0.0\client_1\odp.net\bin\4\Oracle.DataAccess.dll"



D:\SrvApps\Oracle\product\19.0.0\client_1\odp.net\bin\4\OraProvCfg.exe /action:gac /providerpath:"D:\SrvApps\Oracle\product\19.0.0\client_1\odp.net\PublisherPolicy\4\Policy.4.112.Oracle.DataAccess.dll"



D:\SrvApps\Oracle\product\19.0.0\client_1\odp.net\bin\4\OraProvCfg.exe /action:gac /providerpath:"D:\SrvApps\Oracle\product\19.0.0\client_1\odp.net\PublisherPolicy\4\Policy.4.121.Oracle.DataAccess.dll"



D:\SrvApps\Oracle\product\19.0.0\client_1\odp.net\bin\4\OraProvCfg.exe /action:config /productdp /frameworkversion:v4.0.30319 /providerpath:"D:\SrvApps\Oracle\product\19.0.0\client_1\odp.net\bin\4\Oracle.DataAccess.dll"

Any advice would be appreciated.