Im wondering if the difference in DW versions could be a issue here aswell

Thanks for the response @AlexZhu-MSFT

Sorry for the late response from my end, i didn't immediately notice your post.

Well about the Reporting Server not being installed properly, as i wrote previously, the production SCOM MGMT Server is already pointing to that reporting server and the reports seem to function fine and correct. I'm not seeing the greyed out reporting problem over there.

But the company that i'm helping this out with want to reinstall the whole test enviroment anyways so maybe that will help us and give me some more answers..

The SCOM environment is supposed to be 2019 as far as i can see.

Some components like console and web console didnt have the UR3 but all in all it should be 2019 basic version atleast on the management server, console, web console... (there is no GW). The reporting server that it incorrectly points towards is also 2019 UR3.

But how is it possible that the Operations DB is up-to-date but not the DW? I don't recall recall there to be any specific upgrade task that is performed against the SQL servers while lifting to 2019 except cleaning the ETL in the database.

Could i possibly use the solution provided here in Kevin Holmans article? Number 2 in the part with "Known Issues" where you can update the version of the SQL?

https://kevinholman.com/2021/03/31/ur3-for-scom-2019-step-by-step/

Okey, i will check that, unfortunately i wasnt here when it was lifted to 2019 but the logs should contain historic information maybe unless the upgrade to UR3 upgrade hasnt overwritten it.

But as you said, a complete reinstall would be the most convinient thing right now so that we can save time. I talked to the team that i'm helping out with this and they hinted aswell at doing a reinstall of the test enviroment.

But anyway i would like to thank you guys @LeonLaude and @AlexZhu-MSFT for your helpful comments

Hi Leon,

Thank you for the reply.

I tried launching it as admin today but no difference. Where can i check the Operations Console permissions?

Hi again,

You can ignore this one, we decided to start over and just reinstall the reporting role.

I'm sorry, didn't see your post until now, but yes everything turned out good.

Thanks for the assistance!

Hi Stoyan,

Thanks for the reply, i havent been eligible but im checking it out now, i suppose you are referring to the logs under C:\Users\<UserName>\Appdata\Local\SCOM\Logs?

I have extracted, what i think is relevant info, from the OpsMgrWiard and the Prereq logfiles under C:\Users\<UserName>\Appdata\Local\SCOM\Logs... all cehcks seemed to have passed except the one you se in the logs below.
'

149700-opsmgrsetupwizard.txt149707-scomprereqcheck.txt

Here is some extract from the logfiles.

Does the hotfix update require updating the agents to new versions aswell? Or will the current version for the UR3 remain?

Tested it, worked like a charm! Thank you!

I configured the Group Policy locally on each Hyper-V Host and not globally from the DC in case someone else is wondering,

Here are screenshots from the event on the SQL server:

Thank you for that suggestion, i will try it our tomorrow and reply with the result.

Hi, sorry for the late answer.

Yes it i can connect to the SQL instance via Management Studio, havent felt any issues there.

I think the Operations log is logging the above error message but i can verify it again just to be safe.

I dont know that the SQL is workling poorly,