Troubleshooting the BMC ProactiveNet Operations Console


This section lists how to troubleshoot issues that may arise in the BMC ProactiveNet Operations Console.

Events are not visible in the Operations Console

Events are not visible in the event list on the Operations Console.

Solution

If you modify the structure of an event class on a cell (add a slot to an existing class or add a new class), you must restart BMC ProactiveNet server for the events to be visible on the Operations Console. You can restart BMC ProactiveNet server by running the pw system start command. See How-event-classes-are-structured.

Access to the Groups view is blocked

With the Java Runtime Environment 7 update 51, newer self-signed applets are blocked by default and cannot be accessed by a Web browser. Because of this, access to the Groups view in the Operations Console may be blocked.

Workaround

  1. Execute the C:\Program Files (x86)\Java\jre7\bin\javacpl.exe command.
  2. Click the Security tab.
  3. Add the main URL to the exception list by editing the Exception list as follows: http://<hostname>/
  4. Confirm the settings, close the browser and reopen it.

Some events are not localized in the Operations Console

Some events in the Operations Console may not be localized even though the locale and LANG environment variable are set to be non-English.

Workaround

Run the pw system start command to restart BMC ProactiveNet.

The Abnormality Grid view does not display

Sometimes, because of some database activities that are in progress, the Abnormality Grid view does not open and displays an internal server error when the request times out.

Workaround

Close the page and try opening it after some time.

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC ProactiveNet 9.6