Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Words and Phrases
| Search for | Example | Results |
|---|---|---|
| A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
|
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Using Boolean Operators
| Search for | Operator | Example |
|---|---|---|
|
Two or more words in the same topic |
|
|
| Either word in a topic |
|
|
| Topics that do not contain a specific word or phrase |
|
|
| Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
| A combination of search types | ( ) parentheses |
|
Known Issues and Workarounds
Integration services are missing from the ovc command output.
Symptom
Not all entries related to the OpsCx for Microsoft SCOM integration services (HPBsmIntSCOM <Version> Event, HPBsmIntSCOM <Version> TopologyHPBsmIntSCOM <Version> Metricsovc -status command.
Action
Registration of some integration services might not have been successful. To manually register a missing integration service, follow the steps:
-
Open a Command Prompt window with administrative privileges.
-
Run the following command:
ovcreg %OvDataDir%datafiles\HPBsmIntSCOM\<InstanceID>\<ServiceName>.xmlIn these command, in places of
<InstanceID>and<ServiceName>, specify the actual values. For information about the integration services and their naming convention, see Integration Services topic.
Integration service stops immediately after it is started.
Symptom
When you attempt to start an OpsCx for Microsoft SCOM integration service, it starts for a moment and then stops.
Action
Configuration file of this integration might have been manually edited and contains syntax errors. Proceed as follows:
-
Check the validity of the configuration file. For basic syntax guidelines, see Integration Configuration Files topic.
-
Correct the errors accordingly.
-
To start the affected integration service, run the
ovc -start <ServiceName>command.In this instance,
<ServiceName>is the actual value. For information about the integration services and their naming convention, see Integration Services topic.
An integration service status is "Stopped" instead of "Running".
Symptom
When you run the ovc -status command, the command output indicates some OpsCx for Microsoft SCOM services are not running.
Action
For each integration service that is not running, run the following command to start it:
ovc -start <ServiceName>
In this instance, <ServiceName> is the actual value. For information about the integration services and their naming convention, see Integration Services topic.
Event integration component appears registered with a wrong hostname.
Symptom
In the Events & Connector Registration page of the Configuration Utility, before registering your product connector for collection of events, when you check for the product connector's registration status, OpsCx for Microsoft SCOM reports the connector as already registered from a different system.
Action
Another instance of the event integration component seems to be already registered as a product connector with your Microsoft SCOM server. Product connectors cannot share Microsoft SCOM data. Cancel registration of the already registered product connector on the remote host.
Some events are not forwarded from Ops Connector for SCOM to OMi.
Symptom
While the event integration of OpsCx for Microsoft SCOM properly collects and forwards events in general, some of them are missing in the OMi web interface when a large number of events are generated in a very short period of time.
Action
Increase the amount of time allowed for the events to be processed in Microsoft SCOM. For instructions, see the Microsoft knowledge base article available on the web page http://support.microsoft.com/kb/2277825.
Delays in data forwarding to Operations Connector, excessive CPU usage on the OpsCx for Microsoft SCOM host.
Symptom
The data relayed from Microsoft SCOM reaches Operations Connector with a noticeable delay. OpsCx for Microsoft SCOM processes take up unreasonably high proportion of the CPU time.
Action
Inspect the corresponding OpsCx for Microsoft SCOM log file. If there are entries related to frequent poll retries, they might indicate a too short polling interval. Data cannot be passed on and the integration keeps retrying until it succeeds. In this case, increase the data polling interval by modifying the value of the interval option in the integration configuration file.
Events relayed to OMi do not have the External ID property set.
Symptom
In the Event Perspective context of the OMi web interface, when you inspect the events forwarded to OMi from a Microsoft SCOM instance, there are values missing in the External ID column of the Forwarding Information pane.
Action
Configure Operations Connector as a connected server for OMi by adding it to the connecter servers group in OMi.
Even though the topology integration is correctly configured, the topology data is not visible in OMi.
Symptom
When you start the topology integration service, the topology data seems not to be relayed to OMi even though installation of the topology synchronization package, its registration with OMi, and configuration of the topology integration were properly performed.
Action
Wait for a few topology collection intervals (the intervals are defined in the interval option of the topology integration configuration file). If topology data does not show up in the OMi web interface, the topology synchronization package might not have been registered successfully. To resolve the issue, restart OMi.
Configuration items for some objects monitored by Ops Connector for SCOM are not created in OMi.
Symptom
There are configuration items (CIs) missing in the Microsoft SCOM topology that is presented in the OMi web interface.
Action
Adjust the size of the External ID attribute of the Data configuration item (CI) type in OMi. For instructions, see Adjusting OMi Settings.
Configuration items relayed to OMi have the Monitored By property incorrectly set to OMi.
Symptom
In the CIT Instance window of the Administration > RTSM Administration > Modeling > CI Type Manager context of the OMi web interface, the Monitored By column contains the value [OM] instead of the proper identification of the connected server which is [BSM Connector:<Hostname>:<FQDN>].
Action
Configure Operations Connector as a connected server for OMi by adding it to the connecter servers group in OMi.
Changes made to the Ops Connector for SCOM topology are not reflected correctly in OMi.
Symptom
In the OMi web interface, unusual topology hierarchy is presented. For example, some configuration items (CIs) might appear isolated from the rest of the collected topology, although they should not because they are related to other monitored Ops Connector for SCOM objects.
Action
By default, the Detect deltas option is selected in the Operations Connector policy for Ops Connector for SCOM topology. With such a configuration, only recent changes in the Ops Connector for SCOM topology are propagated to OMi. In some cases these changes provide insufficient information resulting in incorrect representation of the topology in OMi. Perform the following steps:
-
Log on to the Operations Connector web interface.
-
Right-click the OpsCx for Microsoft SCOM <InstanceID> (3.02) - Topology Integration policy and select Edit.
-
Click the Source tab.
-
In the Source page, clear the Detect deltas option.
-
Click Save and Close to apply the change.
Required metrics are not available in the Configuration Utility after import of the Ops Connector for SCOM management packs.
Symptom
The metrics that you intend to collect are not available in the Configuration Utility in the Metric Collection Scope part of the Metrics page, even though you imported the bundled Microsoft SCOM management packs and the corresponding monitoring rule is enabled in Microsoft SCOM.
Action
Manually edit the metric filter configuration file and add the required metrics to it. For instructions, see Adding Custom Metrics to the Collection Scope topic.
There are visual glitches in the Configuration Utility when non-English language is used in its interface.
Symptom
After you launch the Configuration Utility in a non-English language, minor visual inconsistencies are visible on the pages: labels overlapping boxes, cropped button labels, and similar. These problems are particularly apparent on Windows Server 2012 systems.
Action
Launch the Configuration Utility so that it displays its interface text in English.
Warnings keep getting logged into the operating system event log.
Symptom
When you inspect the Windows event log using Event Viewer, there are entries of the Warning level that originate from the Bid source.
Action
The Microsoft SCOM Built-In Diagnostics (BID) Loader Stub might not be available to OpsCx for Microsoft SCOM. For instructions on how to obtain and install it, see Installing the Built-In Diagnostics Loader Stub topic.
Configuration Utility reports an error in the Command Prompt window from where it is launched.
Symptom
When you launch the Configuration Utility by running a command in a Command Prompt window (for example, to launch it in a non-English language), and then select a process set on the Processes page, the following error is reported in the Command Prompt window:
genintcrypt: Failed to load credential store!
Action
None. You can safely ignore the error message.
Before Contacting Software Support
If you cannot solve your issue, report it. Before contacting Software Support, make sure that:
-
You have performed the general checks.
-
You have verified your problem is not described in this topic.
-
You have collected relevant data that might be required to send to Software Support: a description of your problem, characteristics of your environment, related entries logged in the operating system event log or in the OpsCx for Microsoft SCOM log files.
Software Support personnel will then provide you with further instructions. Among other things, you may be asked to change the OpsCx for Microsoft SCOM logging severity level, to repeat or perform particular operations in your OpsCx for Microsoft SCOM environment, and to collect specific data from your system and send them to the respective service provider.
The Software Support personnel are not qualified to solve the issues related to third‑party software or hardware.
To contact Software Support, see the web site at https://softwaresupport.softwaregrp.com.
Related topics
Integration Configuration Files
Adding Custom Metrics to the Collection Scope
Installing the Microsoft SCOM Built-In Diagnostics Loader Stub
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to ovdoc-asm@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: