Ensign Ensign
Ensign
396 views

HPOMW 9 Web Console

Hello all.

We're running HPOMW 9.

Below is our current patch level.

Our data center staff use the web console to monitor and manage events.

It has been working fine for years.

Suddenly yesterday it stated generating "Server Error, 500 - Internal server error.,There is a problem with the resource you are looking for, and it cannot be displayed." messages and a web console session cannot be established.

Tried a reboot of the HPOMW management server but that didn't help.

I see nothing useful in the IIS logs.

Nothing has changed on the HPOMW management server.

Any ideas what would cause this issue to suddenly happen and how to fix?

Any help would be greatly appreciated.

 

Thanks everyone.

-Tom

The latest installed patches are:
INFSPIWIN_00008, MSSSPIOMW9_00001, OAAIX_00032, OAHPUX_00032, OALIN_00032,
OALIN_DEB_00032, OASOL_00032, OAWIN_00032, OMW_00161, OMW_00185, OMW_00203,
OMW_00204

 

Labels (1)
0 Likes
1 Reply

Hello Tom Wolf_3, 

Please find recommendations below:

  • Check domain:

Please check whether your current domain also has child domains. If child domains have been turned off, it might result in the domain list taking some time for users who are part of the child domains, creating then a disconnection by TIME_ . If they were turned off, try to turn them on again and see whether issue has disappeared.

 

  • Validate services:
    1. Close any browser that you used to connect to Web Console before
    2. In OMW Server use Task Manager and check whether OvBLXmlMessageServer process is running. If yes then kill it
    3. Restart the w3wp process (be sure that this will affect any other Web server based product)
    4. Now launch http://<<omwservername>> where <<omwservername>> is the shortname of the OMW server. If it launches the default IIS website, use:  http://<<omwservername>>/ovoweb
    5. If Web Console still failing, use Task Manager and verify that OvBLXmlMessageServer is running (and it should be running under HP-OVE-User).
    6. Finally check that the %ovsharedir%\webconsole\userdata\status-options_.xml file (here will be the name of the user who launched Web Console) exists?

 

  • Validate port and connection:

If you have a Reporter integration, make sure whether PM installed and OMW console are not using same port. PM uses Apache on port 80, this is conflict to Reporter IIS which is running on port 80 by default and this is impact to Reporter integration menu in OMW Web Console where is unable to open. Validate with network security team to define whether this is the issue.

If none of above options resolve issue, I recommend you open a ticket with Support team to see issue deeper.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.