VM Manager Tool return codes
If you encounter problems while configuring or managing the VM Manager Tool, refer to the log files for more information about the occurring errors.
Location of the log files
Location of the VM Manager Tool logs depends on the type of
the VM Manager Tool.
- For local VM Manager Tool
opt/ibm/LMT/VMMAN/logs
C:\Program Files\ibm\LMT\VMMAN\logs
- For central and distributed VM Manager Tool
-
/var/opt/BESClient/LMT/VMMAN/logs
-
C:\Program Files (x86)\BigFix Enterprise\BES Client\LMT\VMMAN\logs
- For disconnected VM Manager Tool
-
VM Manager Tool install dir/logs
-
VM Manager Tool install dir\logs
The log file contains a return code that can help you check why the issue occurs and solve the problem.
Return codes
| Return code | Description and possible solutions |
|---|---|
| 0 | No errors. |
| 1 | Initializing logs failed and the log files are not created. Ensure that the
log4j.properties or the log4j2.xml file is located in its
default directory.
|
| 2 | The security module did not start successfully. Ensure that
keys.jceks keystore is located in its default directory:
|
| 3 | It failed to lock the .lock file. When the file is locked, it means that the application is working properly. Locking the file might fail because the application is already running or because some other process is blocking the file. To solve the issue, find the process that is blocking the .lock file and stop it. |
| 4 | The used command is incorrect. Follow the displayed instructions and type the correct command. |
| 5 | It is not possible to read the configuration files. Ensure that the following
folder contains all configuration files and that they are correct:
|
| 6 | The command did not complete successfully. For more information, check the command output and the log file. |
| 7 | The application did not start in the running mode because the service is not
installed. Run the -install command and install the service. |
| 8 | The service did not start in the running mode. For more information, check the log file. |
| 10 | Connecting to the VM manager by using the -testconnection
command failed. For more information, check the command output. |
| 12 | It was not possible to add the VM manager certificate to the VM Manager Tool keystore. The alias that was used to create the certificate already exists. Use another alias. |
| 13 | Adding the certificate did not complete successfully. For more information, see the log files. |
| 14 | Changing the VM Manager Tool keystore password failed. For more information, check the command output and log files. |
| 15 | It is not possible to regenerate the encryption key for the VM manager. For more information, check the command output and log files. |
| 16 | The -runonce command did not perform any action because there
are no VM managers defined. |
