This document has not been formally reviewed for accuracy and is provided "as is" for your convenience.
Summary
Error
An attempt to start NNMi services using the "ovstart" command fails with the following Windows error:-
"C: Windows\System32\ovstart.exe" is not a valid Win32 application".
Navigating to the NNMi Install Directory, and then executing "ovstart" does start off NNMi, but this time, executing the command "ovstatus -v" shows:
"NmsEvents Service has failed. Refer to the com.hp.ov.nms.events.NmsEvents log file for details".
Example output of the command "ovstatus -v":-
C:\Windows\System32>ovstatus -v
object manager name: OVsPMD
state: RUNNING
PID: 3456
last message: -
exit status: -
object manager name: pmd
state: RUNNING
PID: 3508
last message: Initialization complete.
exit status: -
object manager name: nnmaction
state: RUNNING
PID: 5216
last message: Initialization complete.
exit status: -
object manager name: nmsdbmgr
state: RUNNING
PID: 8132
last message: Database available.
exit status: -
object manager name: ovjboss
state: RUNNING
PID: 3656
last message: Initialization complete.
exit status: -
additional info:
SERVICE STATUS
CommunicationModelService Service is started
CommunicationParametersStatsService Service is started
CustomPoller Service is started
IslandSpotterService Service is started
ManagedNodeLicenseManager Service is started
MonitoringSettingsService Service is started
NamedPoll Service is started
NmsApa Service is started
NmsCustomCorrelation Service is started
NmsDisco Service is started
NmsEvents Service has failed. Refer to the com.hp.ov.nms.events.NmsEvents log file for details.
NmsEventsConfiguration Service is started
NmsExtensionNotificationService Service is started
NmsTrapReceiver Service is started
NnmTrapService Service is started
PerformanceSpiConsumptionManager Service is started
RbaManager Service is started
SpmdjbossStart Service is started
StagedIcmp Service is started
StagedSnmp Service is started
StatePoller Service is started
TrapConfigurationService Service is started
TrapPropertiesService Service is started
TrustManager Service is started
Cause
This issue is easily reproducible, if one simply creates a bogus file named "ovstart.exe" at the "C:\Windows\System32" directory.
NNMi has no executables at the "C:\Windows\System32" directory. If such a file is present, it may have been the result of an output redirection operation gone wrong, or any other user initiated operation.