Troubleshooting SAP Metric Data Collector
Available from 9.2.9. If you encounter problems with measuring
utilization of SAP license metrics by using SAP Metric Data Collector,
check the log and the return code to determine the possible cause.
Log file
The trace.log file is located in the following directory.
/var/opt/BESClient/LMT/SAPTOOL/logs
C:\Program Files (x86)\BigFix Enterprise\BES Client\LMT\SAPTOOL\logs
Return codes
If the Initiate SAP Metric Data Collector task fails, an error code that indicates why the scan failed is returned. The return code is included in the log file.
You can also check the status and the return code in the BigFix console. Go to , and activate theSAP Metric Data Collector Information analysis. The analysis does not provide a return code for the connection test.
| Return code | Possible cause and solutions |
|---|---|
| 0 | No errors. |
| 1 | An unknown error occurred. Contact BigFix Support. |
| 2 | Writing in to the trace.log file could not be initiated. Ensure that the file is not used by other processes and that it is not opened in any program, for example a text editor. |
| 3 | Encryption module could not be initiated. Ensure that the keystore and keystore password are correctly configured. For more information, see: Changing the default secret key and password to the SAP Metric Data Collector keystore. |
| 4 | The specified command-line parameters are incorrect. Run the saptool.bat
or saptool.sh script with the -h parameter to see the list of
supported command-line parameters. |
| 5 | Configuration settings are invalid or missing. Ensure that all required parameters are specified and correct. For more information, see: SAP Metric Data Collector configuration parameters. |
| 6 | Connection to SAP failed. Ensure that connection to SAP is possible and that all required parameters are specified and correct. For more information, see: SAP Metric Data Collector configuration parameters. |
| 7 | The SAP Metric Data Collector process was interrupted. Run SAP Metric Data Collector again. |
| 8 | Generating .slmtag files failed. Ensure that files in the slmtags subdirectory are not locked by other processes. |
| 9 | Measuring utilization data in SAP exceeded the time limit. |
| 10 | Grouping SAP users in License Administration Workbench (LAW) failed because SAP user grouping mode is not set to automatic. Set the mode to automatic, and run SAP Metric Data Collector again. |
| 11 | The data collected from SAP is incomplete. Ensure that the consolidated results are available in LAW or LAW 2.0, and then run the SAP Metric Data Collector again. The measurement results can be retrieved and consolidated automatically in LAW when the skip_measurements parameter is set to false. If the problem persists, contact BigFix Support. |
| 12 | The status of the SAP Metric Data Collector completion could not be stored on disk. Ensure that the saptool.status file is not used by other processes and that it is not opened in any program, for example a text editor. |
| 13 | The configuration file could not be updated with the encrypted password. Ensure that none of the configuration files in the config subdirectory is used by other processes and that it is not opened in any program, for example a text editor. |
| 14 | The SAP Metric Data Collector configuration that you initiated is not supported. Contact BigFix Support. |
| 15 | SAP Java Connector is corrupted or missing. Download the SAP Java Connector again. For more information, see: Collecting utilization of SAP license metrics. |
| 16 | Currently not used. |
| 17 | SAP Metric Data Collector was run with the -encode
parameter by using a method other than the command line. Run the tool through the command line to
encode keystore password. For more information see: Changing the default secret key and password to the SAP Metric Data Collector keystore. |
| 18 | SAP Metric Data Collector tried to decrypt the stored password by using a key other than the one that was used to encrypt it. The encryption key was changed. Re-enter the password in plain text. The password will be encrypted the next time the tool is run. For more information see: Changing the default secret key and password to the SAP Metric Data Collector keystore and Collecting utilization of SAP license metrics. |
| 19 | SAP Metric Data Collector tried to encrypt the stored password by using a key other than AES or the key was stronger than the Java JCE jurisdiction policy allows. The encryption key was changed. Change the encryption key to AES with correct length. For more information see: Changing the default secret key and password to the SAP Metric Data Collector keystore. |
| 20 | A given SAP system could not find the requested function module. |
| 21 | A function module on a given SAP system failed. Please review trace.log file. |
| 22 | An error occurred when cleaning the last measurement data from the central SAP system. |
| 23 | The ABAP plug-in is not installed on the central SAP system in the landscape. For information about the installation of the code, see: Installing the ABAP plug-in on a central SAP system. |
| 24 | SAP Metric Data Collector could not find the consolidated SAP utilization data. |