VM Manager tool return codes

If you encounter any problems while configuring or managing the VM Manager tool, refer to the log files for more information about any occurring errors. The log files for the VM Manager tool are in the following directories:

  • Trace log files: BES Client\LMT\VMMAN\logs
  • Installation log files: BES Client\LMT\VMMAN\logs\install

For more information, see: Log files.

The log file contains a return code that can help you check why the issue occurs and solve the problem.

Table 1. VM Manager tool return codes
Return code Description and possible solutions
0 No errors.
1 It failed to initialize the logs and the log files are not created. Ensure that the log4j2.xml file is located in its default directory:
  • Linux /var/opt/BESClient/LMT/VMMAN/config/
  • Windows C:\Program Files (x86)\BigFix Enterprise\BES Client\LMT\VMMAN\config\
Note: For BigFix Inventory version below 10.0.3, the log file log4j.properties is used.
2 The security module did not start successfully. Ensure that keys.jackes keystore is located in its default directory:
  • Linux /var/opt/BESClient/LMT/VMMAN/keydb/
  • Windows C:\Program Files (x86)\BigFix Enterprise\BES Client\LMT\VMMAN\keydb\
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:
  • Linux /var/opt/BESClient/LMT/VMMAN/config/
  • Windows C:\Program Files (x86)\BigFix Enterprise\BES Client\LMT\VMMAN\config\
6 The command did not complete successfully. For more information, check command output and the log file.
7 The application did not start in running mode because the service is not installed. Run the command -install and install the service.
8 The service did not start in running mode. For more information, check the log file.
10 It failed to connect to VM Manager using the command test connection. For more information, check the command output.
12 It was not possible to add the VM Manager certificate to the 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 It failed to change the password for keystore. For more information, check the command output and log files.
15 It is not possible to regenerate the encryption key for VM Manager. For more information, check the command output and log files.
16 The command run once did not perform any action because there are no VM Managers defined.