Error (2912) When You Try to Update VMM Agent on Hosts

Recently I’ve stumbled on the following error when trying to update VMM agent on hosts:

Error (2912)
An internal error has occurred trying to contact the server: NO_PARAM: NO_PARAM.

Continue reading “Error (2912) When You Try to Update VMM Agent on Hosts”

PowerShell 3.0

Final version of PowerShell 3.0 is here and it is now available for Windows 7 SP1, Windows Server 2008 R2 SP1 & Windows Server 2008 SP2 systems. PowerShell 3.0 is provided ad windows update that actually contains updates for several technologies:

  • Windows PowerShell 3.0
  • WMI
  • WinRM
  • Management OData IIS Extensions
  • Server Manager CIM Provider
    The update and additional information can be found here.
    Note: This update requires .Net Framework 4.0

Update KB2585542 causes HP OpenView connector for SCOM not send alerts to OMU server

Once again I’ve stumbled on another interesting SCOM issue. First here is the environment:

SCOM01 – RMS server, HP OpenView connector service – Active

SCOM01 – MS server, OpsMgr DB, DW DB, Report server, HP OpenView connector service – Passive

OMU01 – HP Operations Manager for Unix server

SCOM01 is sending alerts to OMU01 via HP OpenView connector. After patching SCOM01 and SCOM02 the connector service stops sending alerts to OMU01. When the following command is ran on SCOM01:

winrm identify –r:OMU01:1270 –auth:basic –u:username –p:password –encoding:utf-8

HTTP error 501 is given. I’ve found similar issue with communication with Unix/Linux servers:

As SCOM is using winrm for communication with Unix\Linux and connectors the resolutions is the same:

  1. Uninstall the update KB2585542 
  2. Make a registry modification to disable the SecureChannel changes implemented in the update
  3. Modifying the registry to disable the SecureChannel changes:

    A “FixIt” package is available in the KB article under the Known Issues section that can be used to disable the security update
    Alternatively, you can add the 32bit DWORD value:
    SendExtraRecord = 2

After implementing those changes the connector started to work properly again.

Another case solved.

VMM Troubleshooting: Windows Remote Management (WinRM) and Configuring Fabric Resources

Two more articles for troubleshooting VMM from Microsoft Wiki.

Troubleshooting Windows Remote Management article can be found here:

Troubleshooting Configuring Fabric Resources article can be found here: