FAQ: Why Doesn’t the SCOM Web Console URL in SCSM Work (403 or 404 Error)?
Published Feb 15 2019 01:14 PM 627 Views
First published on TECHNET on May 22, 2012

When you have an SCOM alert-generated incident selected in SCSM you have two additional tasks available to click on in the task pane: View Alert Details and View CI Health State.

When you click on these tasks they will take you directly in context to the SCSM web console alert details or health explorer:

Alert Details Health Explorer

However, in some cases, you may get a 403 error message – Forbidden: Access is denied. - like this:

Or a a 404 error message – The resource cannot be found. – like this:

Here are some common reasons why you might be getting these errors:

403 – You need to log into the SCOM web console in a browser window to create an authenticated session prior to clicking the task link in SCSM.  I don’t think this was necessary in SCOM 2007 R2 but due to the architectural changes to the SCOM web console in 2012 it seems that this is now necessary, at least for now.

404 – You may have the wrong SCOM web console URL configured in SCSM.  You might think it is http://<servername>:<port>/OperationsManager since that is how you access the SCOM web console.  You might also have the SCOM 2007 R2 URL configured – e.g. http://<servername>:<port> .  The web console URL has changed from 2007 R2 to 2012.  The URL for accessing the SCOM web console for these two tasks is now :/MonitoringView">:/MonitoringView">http://<servername>:<port>/MonitoringView

The documentation on TechNet is out of date on this topic and will be updated soon.

Version history
Last update:
‎Mar 11 2019 09:20 AM
Updated by: