Web Console Installation Fails When UR2 is Installed (not really, see answer)

Question

Hi All!

We ended up in a situation where we had to uninstall the web consol, or rather… the "repair" function did it for us.
In this Environment we intend to run the web console on all management servers behind a load balancer, but that's irrelevant for this issue, but it is the reason we want it on the management servers.

The problem we're facing is that since UR2 is installed on the management server, we are now blocked from installing the Web Console again. The setup simply crashes when trying to verify the website.
We've tried the "version fix" where you change the version number back to RTM of the management server in the OperationsManager database, but that didn't help.

Is there another work-around or a setup with UR2 slipstreamed available anywhere?

Cheers!

Answer 1

Yes, that was the issue. Ran the setup with regained permissions on the SQL servers and it worked.

So, to sum it up.

The Connection I made between the web console installation failing and UR2 was wrong and coincidental. I, apparently, lost most of my privileges on the SQL Server instance (still dbo on OperationsManager database) about the same time we had to re-install the web console and that was the reason our setup failed.
The previous issues of installing reporting with UR2 already installed led me astray and had me chasing version numbers.

Once again, we are reminded that it is important to pay attention to the setup logs!

Btw, the easiest way to track what is going on during the setup is to "tail" the logs using powershell. Like so:

Get-Content -Path "C:\Users\<USERNAME>\AppData\Local\SCOM\LOGS\OpsMgrSetupWizard.log" -Wait

The -Wait command will make the command keep listening to changes to the file and print them as they appears, just like a "tail" in linux. This way you can see exactly what happens when you click around in the setup UI.

It's still a bit unfortunate that the setup simply crashes without any messages and that the pre-requisite check doesn't catch that permissions are missing.

Answer 2

Ok, looking at the logs, this seems to be a bit of an unfortunate timing.
Seems like the DBA:s have revoked a few permissions our installer account had on the SQL cluster.

I'm, spotting things like this in the logs:
Error Message: VIEW DATABASE STATE permission denied in database 'master'

Answer 3

Seems you found the cause of your issue by yourself, but as a sidenote, note that running the web console behind a load balancer is not supported (even though it is still technically doable, you'll find blogs explaining how to) : https://learn.microsoft.com/en-us/system-center/scom/deploy-install-web-console?view=sc-om-2019