Description of System Center Operations Manager 2007 R2 Connectors update

Microsoft System Center Operations Manager 2007 R2 Connectors update is now available. This update fixes the following issues in System Center Operations Manager 2007 R2 Connectors.

Issue 1: Potential high CPU usage of HP OVO Event Consumer for Windows (scinteropd.exe)

The Scinteropd.exe process of HP OVO Event Consumer for Windows sometimes increases CPU usage to a very high level. This problem occurs only in System Center Operations Manager 2007 R2 Connectors for HP Operations Manager on Windows. It occurs in all language versions of the connectors.

Cause of issue 1

The Scinteropd.exe process enters a loop when multiple transactions occur at the same time.

Note For example, multiple transactions occur when the Scinteropd.exe process is acknowledging messages from the OVO side.

Issue 2: Synchronization issue in HP OVO Connector

HP Operations Manager and System Center Operations Manager 2007 R2 may be in an asynchronous state when alerts are forwarded that have already been resolved. Open events are still present in HP Operations Manager even though the corresponding alerts in System Center Operations Manager 2007 R2 are already resolved.

Cause of issue 2

A delay occurs when an alert is marked "to be forwarded" and is actually handled by the connector service. If the forwarded alert is resolved before the connector service handles the alert, the release version of the OVO connector service forwards the resolved alert to HP OVO. Then, an active message is created in HP OVO that corresponds to the resolved alert in System Center Operations Manager 2007 R2.

Issue 3: Remedy connectors do not populate the Computer Name and Domain fields

When an alert is forwarded from System Center Operations Manager 2007 R2 to Remedy, the Computer Name field and the Domain field are left blank in the Remedy notes field. This issue occurs in the release version of System Center Operations Manager 2007 R2 Connector for Remedy 6.3 and Remedy 7.1.

Cause of issue 3

The Computer Name field and the Domain field are populated incorrectly.

Issue 4: Unresponsiveness of the Interop provider when an Enterprise Management Service (EMS) API call returns an error

The Interop provider may stop responding and not recover when an API calls to the EMS and returns an error.

Note Usually, the API calls to Remedy.

This issue typically occurs when large localized text strings in the Custom Field Alert properties are forwarded to Remedy. However, it can also occur with other properties.

Note This issue is associated with the Remedy connector. However, it might also occur with other connectors. Therefore, the update provided in this article includes the updated Unix Interop providers. However, do not apply the updated Unix Interop providers unless you are instructed to do this by a support professional. To apply the updated Unix Interop providers, you can uninstall the Interop provider and reinstall the new Unix Interop provider packages that are included in this update package.

Cause of issue 4

The Interop providers do not handle errors returned from the API calls correctly. After you apply this update, the Interop providers are updated to correctly handle errors returned from the API calls. If the forwarded alert cannot be inserted into the remote system according to the rules that apply to the remote system, the failure is logged and the provider continues to process additional forwarded alerts. This applies to all the System Center Operations Manager 2007 R2 Connectors.

Installation instructions

Notes for User Account Control-enabled systems

On a computer that is running a Windows Vista system or a Windows Server 2008 system that has User Account Control (UAC) enabled, all installations of OM2007R2Connectors-KB975774.EXE should be run at an elevated execution level. To do this, use one of the following methods:

• Right-click the OM2007R2Connectors-KB975774.EXE file, and then select Run as administrator.
• Right-click the OM2007R2Connectors-KB975774.EXE file, and then select Properties. On the General tab, click Advanced, and then click to select the Run as administrator check box.
• Right-click the OM2007R2Connectors-KB975774.EXE file, and then select Properties. On the Compatibility tab, click the Show Settings for all users and then click to select the Run as administrator check box.

To apply this update, follow these steps on both the connector service and the Windows-based Interop providers:

1. Run the OM2007R2Connectors-KB975774.exe file. Updated files are extracted to the following folder:
   %ProgramFiles%\OM2007R2Connectors-KB975774
2. In the OM2007R2Connectors-KB975774 folder, find and then run the SetupUpdateInterop.exe file.
3. Click Yes to accept the License Terms for the System Center Operations Manager 2007 R2 Connectors update.
4. The installation process displays the release notes, runs the Connectors Setup Wizard, and installs the connector and provider updates. The installation process then continues to the end without any queries.
5. Click Finish to end the installation.
6. The Setup Wizard displays one of the following messages according to the component that is installed on the system:
   Connector Patch was successfully installed
   or
   Provider Patch was successfully installed

Installation of the updated UNIX providers

To update the UNIX providers, you must uninstall the release version of the UNIX providers and then install the version that is included in this update. However, do not apply the updated Unix Interop providers unless you are instructed to do this by a support professional.

To update the Unix Interop providers, follow these steps:

1. Uninstall the following Interop providers:
   
   Universal Connector
   • For AIX: installp –u MSFTscinteropUnv.rte
   • For HPUX 11iv3 (IA-64): swremove MSFTscinteropUnv
   • For HPUX 11iv3 (IA-64): swremove MSFTscinteropUnv
   • For Solaris 10 SPARC: pkgrm MSFTscinteropUnv
   • For RHEL 5.1: rpm –e MSFTscinteropUnv
   • For SLES 10: rpm –e MSFTscinteropUnv
   Connector for IBM Tivoli Enterprise Console
   • For AIX: installp –u MSFTscinteropTec.rte
   • For Solaris 10 SPARC: pkgrm MSFTscinteropTec
   Connector for HP Operations Manager for UNIX
   • For HPUX 11iv3 (IA-64): swremove MSFTscinteropOvo
   • For HPUX 11iv3 (IA-64): swremove MSFTscinteropOvo
   • For Solaris 10 SPARC: pkgrm MSFTscinteropOvo
2. Install the appropriate new Interop providers:
   
   Universal Connector
   • For AIX:
     gzip –d /tmp/scinterop-<build-number>.aix.5.3.pcc-unv.lpp.gz
     installp -X -d /tmp/scinterop-<build-number>.aix.5.3.ppc-unv.lpp MSFTscinteropUnv.rte
   • For HPUX 11iv3 (IA-64):
     uncompress /tmp/scinterop-<build-number>.hpux.11iv3.ia64-unv.depot.Z
     swinstall -s /tmp/scinterop-<build-number>.hpux.11iv3.ia64-unv.depot MSFTscinteropUnv
   • For HPUX 11iv3 (PA-RISC):
     uncompress /tmp/scinterop-<build-number>.hpux.11iv3.parisc-unv.depot.Z
     swinstall -s /tmp/scinterop-<build-number>.hpux.11iv3.parisc-unv.depot MSFTscinteropUnv
   • For Solaris 10 SPARC:
     gzip –d /tmp/scinterop-<build-number>.solaris.10.sparc-unv.pkg.gz
     pkgadd -d /tmp/scinterop-<build-number>.solaris.10.sparc-unv.pkg MSFTscinteropUnv
   • For RHEL 5.1: rpm –i MSFTscinteropUnv-<build number>.rhel.5.x86.rpm
   • For SLES 10: rpm –i MSFTscinteropUnv-<build number>.suse.10.x86.rpm
   Connector for IBM Tivoli Enterprise Console
   • For AIX:
     gzip –d /tmp/scinterop-<build-number>.aix.5.3.pcc-tec.lpp.gz
     installp -X -d /tmp/scinterop-<build-number>.aix.5.3.ppc-tec.lpp MSFTscinteropTec.rte
   • For Solaris 10 SPARC:
     gzip –d /tmp/scinterop-<build-number>.solaris.10.sparc-tec.pkg.gz
     pkgadd -d /tmp/scinterop-<build-number>.solaris.10.sparc-tec.pkg MSFTscinteropTec
   Connector for HP Operations Manager for UNIX
   • For HPUX 11iv3 (IA-64):
     uncompress /tmp/scinterop-<build-number>.hpux.11iv3.ia64-ovo.depot.Z
     swinstall -s /tmp/scinterop-<build-number>.hpux.11iv3.ia64-ovo.depot –x ask=true MSFTscinteropOvo
   • For HPUX 11iv3 (PA-RISC):
     uncompress /tmp/scinterop-<build-number>.hpux.11iv3.parisc-ovo.depot.Z
     swinstall -s /tmp/scinterop-<build-number>.hpux.11iv3.parisc-ovo.depot –x ask=true MSFTscinteropOvo
   • For Solaris 10 SPARC:
     gzip –d /tmp/scinterop-<build-number>.solaris.10.sparc-ovo.pkg.gz pkgadd -d /tmp/scinterop-<build-number>.solaris.10.sparc-ovo.pkg MSFTscinteropOvo

Update information

A supported update is available from Microsoft. However, this update is intended to correct only the problem that is described in this article. Apply this update only to systems that are experiencing the problem described in this article. This update might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this update.

If the update is available for download, there is a "Update download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the Update.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific update. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

Note The "Update download available" form displays the languages for which the update is available. If you do not see your language, it is because a update is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You do not have to restart the computer after you apply this update.

Update replacement information

This update does not replace any other updates.

File information

The English version of this update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.