The article will explain how to resolve OBM agent deployment errors by restoring the missing “ovcd.exe” file and restarting the service.

Environment

Operations Bridge Manager (OBM) all versions
Operations Agent (OA) Windows

Situation

When running an "ovdeploy" command from OBM, the agent returns the following error:

Output:
ERROR: (depl-228) Could not get OS type.
(bbc-42) Unable to connect to the OV Communication Broker. The
connection error returned was: <null>
(xpl-331) connect() to '[IP]:383' failed.
(WIN-0)
(xpl-331) connect() to '[IP]:383' failed.
(WIN-0)

Checking the port 383 and it is available.

Checking the service “HP OpenView ctrl service” and it was stoped, however, it fails to start.

Checking the file "C:\Program Files\HP\HP BTO Software\bin\win64\ovcd.exe" and we notice that ovcd.exe does not exist.

For the solution, check the complete knowledge article