vpstat return codes
All vpstat commands that verify a condition (like services running) return codes based on results of verification. Normally, vpstat return codes indicate whether checked items (defined with the vpstat command) have passed verification.
HPOM includes the following vpstat return codes:
- 0: there was no error and checking was successful.
- 1: there was no error and checking was not successful.
- negative value: if there was an error - execution of the tool failed.
Examples
- Checking single process if running:
vpstat -8 opcctla.exe
- Returns 0 if opcctla.exe process is running; otherwise it returns 1.
- Checking all processes (configured in vpstat configuration
file):
vpstat -8
- Returns 0 if all process listed in [PROCESSLIST] section of the configuration file are running; otherwise it returns 1.
If some internal error occurs during vpstat tool execution, a negative return code is returned. The following table includes all possible values.
| Error Code | Description |
| -100 | Retrieving of system platform type failed. |
| -101 | Retrieving of system memory status failed. |
| -102 | Retrieving of system disk space status failed. |
| -103 | Retrieving of system network settings failed. |
| -104 | Retrieving of system security settings failed. |
| -110 | Retrieving of information from configuration file (vpstat.conf) failed. |
| -111 | System runs out of physical memory when creating report. |
| -112 | Com internal error (cannot initialize COM library). |
| -113 | Wrong parameter is specified. |
| -114 | Specified folder was not found. |
| -115 | Error in configuration file (vpstat.conf). |
| -116 | Internal error occurs. |
| -117 | Caught internal exception. |
| -120 | Opening of service control manager database failed. |
| -121 | Enumerating services under specific service control manager failed. |
| -122 | Opening of specific service failed. |
| -123 | Retrieving configuration parameters of specified service failed. |
| -124 | Retrieving the name and status of each service that depends on the specified service failed. |
| -130 | Establishing connection to predefined registry key failed. |
| -131 | Opening of specified registry key failed. |
| -132 | Retrieving of data for specific registry key failed. |
| -133 | Converting specified string into original class identifier failed. |
| -140 | Creating of an enquiry context for viewing the elements in an endpoint map failed. |
| -141 | Server is not listening for remote procedure calls. |
| -150 | Cannot connect to specified node. |
| -151 | Operating system is not Windows. |
| -152 | Whenever establishing connection to predefined registry key failed or property under specified registry key does not exist. |
| -160 | Try to kill process failed, because process name or PID cannot be found. |
| -170 | Retrieving of handle to current process failed. |
| -171 | Enumerating of process modules failed. |
| -172 | Retrieving "exe" module failed (vpstat.exe). |
| -180 | Net-bios computer name cannot be retrieved. |
| -190 | Specified file cannot be found on specified path. |
| -191 | Patch configuration file is not specified. |
| -192 | Inserting of lines fails while patching configuration file. |
| -193 | Patching of REGLIST section in vpstat.com failed. |
| -194 | Patching of RPCLIST section in vpstat.com failed. |
| -195 | Patching of COMLIST section in vpstat.com failed. |
| -196 | Specified file cannot be found on specified path. |
| -197 | Patching of REQLIST section in vpstat.com failed. |
| -198 | Patching of PROCLIST section in vpstat.com failed. |
| -199 | Patching of CHKVER section in vpstat.com failed. |
| -200 | Patching of DEPLIST section in vpstat.com failed. |
| -210 | Saving changes to configuration file (vpstat.conf) failed. |