OvEpStatusEngine stopped after install KB4056898

  • KM03079470
  • 23-Jan-2018
  • 23-Jan-2018

This document has not been formally reviewed for accuracy and is provided "as is" for your convenience.

Summary

After install Microsoft security patch "KB4056898", OvEpStatusEngine will not start.

Question

After install Microsoft security patch "KB4056898", OvEpStatusEngine will not start

OWM Version 9

>vpstat -3 -l
============================================================
running: E:\\Program Files\\HP\\HP BTO Software\\bin\\win64\\vpstat.exe
version: A.6.0.115.7
now: Fri Jan 19 02:43:35 2018
============================================================
============================================================
==================== Services Information ==================
============================================================
Configuration file: G:\\ProgramData\\HP\\HP BTO Software\\conf\\vpstat\\vpstat.conf
Ver: 09.00.00231
Date: Wed Sep 1 21:53:52 2010
Remark: HP Operation Manager - Performance.
Services on : LOCAL MACHINE
(NT Services) :
SERVICE_RUNNING : OvAutoDiscovery Server ( OvAutoDiscovery Server )
SERVICE_RUNNING : OvCtrl ( HP OpenView Ctrl Service )
SERVICE_RUNNING : OvDnsDscr ( OvDnsDiscoveryService )
SERVICE_RUNNING : OvEpMessageActionServer ( OvEpMessageActionServer )
SERVICE_STOPPED : OvEpStatusEngine ( OvEpStatusEngine )
SERVICE_RUNNING : OvMsmAccessManager ( OvMsmAccessManager )
SERVICE_RUNNING : OvOWReqCheckSrv ( OvOWReqCheckSrv )
SERVICE_RUNNING : OvowWmiPlatProv ( OvowWmiPlatProv )
SERVICE_RUNNING : OvPmad ( OvPmad )
SERVICE_RUNNING : OvSecurityServer ( OvSecurityServer )
SERVICE_RUNNING : OvServerMonitor ( OvServerMonitor )
SERVICE_RUNNING : OVServiceLogger ( OVServiceLogger )
SERVICE_RUNNING : OvStoreProv ( OvStoreProv )

ERROR: SERVICE_STOPPED : OvEpStatusEngine

Answer

There is a known issue on KB4056898 that would directly affect our product:
https://support.microsoft.com/en-us/help/4056898/windows-81-update-kb4056898

The symptom is:
When calling CoInitializeSecurity, the call fails if passing RPC_C_IMP_LEVEL_NONE under certain conditions.
When calling CoInitializeSecurity, the call may fail if passing RPC_C_AUTHN_LEVEL_NONE as the authentication level. The error message that is returned on the failure is: STATUS_BAD_IMPERSONATION_LEVEL.
This issue is resolved in KB4057401, install the following hotfix on top of the security fix and see if the status engine now starts:
https://support.microsoft.com/en-us/help/4057401/windows-81-update-kb4057401