This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 26%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
Hi,
I have a SCOM Test Enviroment where the only management server is pointing to the wrong Reporting Server URL, i wish to change it to the correct one (the test scom reporting server) under Administration > Settings > Reporting but it's greyed out for some reason.
What could the reason be? I pretty sure i have the required permissions to perform that change, i am a member of the role Operations Manager Administrators. It works in the production enviroment. Also, i'm not able to see the Reporting Button on the bottom left with Administration.
P.S. Also some background for the context of it, for various reasons we reinstalled the reporting server role on the reporting server, i dont remember if the problem i have on the test enviroment existed before the reinstall. THe production enviroment works fine and is connected to the reporting server.
Hi @Senad Sadikovic ,
Could be a permission issue, have you got administrator permissions on the Operations Console?
Did you run the Operations Console as an administrator?
----------
If the reply was helpful please don't forget to upvote and/or accept as answer, thank you!
Best regards,
Leon
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?
You can check under Administration -> Security -> User Roles.
What version of SCOM and Update Rollup are you currently running?
As Alex stated, there's a chance that the Reporting feature is corrupted, in this case a reinstall of the Reporting feature is recommended.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 66%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
Hi,
Thank you for sharing the detailed information about the problem. If the Reporting pane does not exist, it indicates the reporting server is not installed properly. For this issue, we may try reinstalling the reporting server in the database server, connect to the management server during the installation and check if exists when finished.
How to install the Operations Manager Reporting server
https://learn.microsoft.com/en-us/system-center/scom/deploy-install-reporting-server?view=sc-om-2019
Alex
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
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..
Im wondering if the difference in DW versions could be a issue here aswell
Looks like your DW is running SCOM SAC 1801, while the DB is running SCOM 2019 UR3, this could definitely cause problems, have you upgraded your SCOM environment from SCOM 1801 to SCOM 2019?
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/
Before doing anything I would check the SCOM installation logs and check if there was any errors during the upgrade or any inconsistencies.
If the logs provide nothing, and this is only a test environment, you might save a lot of time by simply performing a clean install of the whole environment.
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 @Leon Laude and @AlexZhu-MSFT for your helpful comments
You're welcome, keep us updated :-)