February 9, 2021 at 4:37 pm
We're upgrading from 2012 to 2019 and I'm running into multiple issues with SSRS 2019. But let me start with the basic one.
How do we install the dev version of this as a named instance? It installs as "SSRS" but I want to install it as our old instance name so we don't have to redo pointers.
What am I missing?
February 10, 2021 at 10:28 am
No more named SSRS instances since SQL 2017 https://itsalljustelectrons.blogspot.com/2018/01/Installing-SSRS-2017.html
February 10, 2021 at 7:32 pm
So I'm not going to be able to directly upgrade my 2012 ReportServer database to 2019?
And we're not going to be able to have multiple instances? That sucks and poses a potential problem for me.
Okay, so I tried uninstalling and re-installing SSRS, removing my restored DBs, and tried creating a new database. Now we're getting this error (see attached picture).
Everything I find on this error relates to older versions of SSRS. Any thoughts?
February 11, 2021 at 9:58 am
February 11, 2021 at 4:30 pm
That link refers to SQL 2017 and apparently Microsoft had to go in and fix the installer package because the user had to re-download and use the Upgrade option.
I'll try downloading the 2019 file again, but if I have to go to Microsoft for a fix, then that's going to screw up our upgrade schedule.
Does anyone have any options that might include me being able to fix it myself?
February 12, 2021 at 8:21 am
Maybe farfetched but is your sql server still RTM? I had problems with SCOM 2019 installation when the sql server was already patched and the "versions" didn't match (had to revert to RTM)
February 12, 2021 at 7:38 pm
Our version is Microsoft SQL Server 2019 (RTM-CU8-GDR) (KB4583459) - 15.0.4083.2 (X64)
Nov 2 2020 18:35:09
Copyright (C) 2019 Microsoft Corporation
Developer Edition (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor)
So are you saying I might need to uninstall SQL, reinstall to initial SQL and then install SSRS before updating the SQL version?
What problems did you have?
February 12, 2021 at 9:58 pm
SCOM 2019 SSRS would refuse to install because the version was too high (it needed the RTM SQL Server (sigh)). I'll try it again on my laptop (uninstall sql, install sql, install SSRS, install CU)
February 17, 2021 at 11:59 am
Well, we did get SSRS installed. We just can't create a new database or get it to restore encryption keys when we restore the 2012 ReportServer and ReportServerTempDB databases to the new server.
To test this, I spent all day uninstalling SQL from the server and trying to set up SSRS with the RTM version of SQL 2019. I kept getting the same result. SSRS would install but wouldn't create the new databases (same error as above). Finally I gave up, and restored SQL 2019 to the CU8 version we had. I've got another thread on Microsoft's website about the issue and they recommended the same SQL 2017 steps (Upgrade Edition) that you posted and I tried without success. I've tried everything I can think of. I think it might be time to open an official case with MS.
March 4, 2021 at 6:04 pm
BWAHAHAHAHAHAHA... or maybe that should be WAAAAAAAAAAAAAAAHHHHHHH.
I opened a ticket with Microsoft regarding this issue. After an entire week of back and forth (and the version of ProcMon they had me download that would not work, so I had to get a copy of the executable from a coworker), we found the issue.
As of SQL 2017, Microsoft added a lot of new processes and ports for those processes to their software. One of those ports is also the default listening port for McAfee anti-virus. The only way to change the McAfee port is to change it for the entire company, which is unacceptable per our internal security team. The Microsoft Rep is going back to her team to discuss alternatives. She doesn’t know if there is a way to change the port for SSRS to work because this is not an SSRS setting, but a Remote Procedure Call setting in Windows.
I'll update this thread when I have an actual solution. But now I know it's two things butting heads over the same port.
March 4, 2021 at 9:38 pm
One of those ports is also the default listening port for McAfee anti-virus.
The only thing I can say to this is "aw h*ll NO!"
Sometime in the coming months we're going to be moving to SQL 2019, I knew about the "only one instance" which will be a bit of a problem as we've got a couple (OK, 2) customers using SSRS (and 1 is trying to get off it,) but if it's going to cause problems with McAfee it's going to be a complete non-starter...
Time to start a chat with the boss on Monday to start getting plans worked up, because the customer using SSRS is using it HEAVY.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply