Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
What are the return codes of Kiuwan Local Analyzer?
| Table of Contents |
|---|
Successful return codes
...
Kiuwan Local Analyzer command scripts (agent.cmd and agent.sh) return 0 after a successful execution.
- In Windows you can check return code in %ERRORLEVEL%
- In Unix you can check it in $?
...
Error return codes
Non-zero (error) codes are the following:
...
Return Code | Error | Meaning/Reasons | Action | -wr needed? |
|---|---|---|---|---|
1 | Analyzer execution error | Run-time execution error (out of memory, etc.) | Review log files to find the exact cause. Visit Troubleshooting |
...
to find help on this error. Contact Technical Support. |
| ||
10 | Audit overall result = FAIL | Audit associated to the analyzed application did not pass
| See audit report for exact reasons of non compliance (checkpoints not passed, etc.) Visit Audits Management |
...
for further help | Yes
|
11 | Invalid analysis configuration |
...
A configuration parameter has a wrong value | Review log files to find the exact cause. Visit Troubleshooting |
...
to find help on this error. |
| |
12 | The downloaded model does not support any of the discovered languages | The model specified for the application does not |
...
contain rules for the technologies being analyzed | Select an appropriate model or modify the model to include those technologies not currently supported. Visit Troubleshooting |
...
to find help on this error. |
| |
13 | Timeout waiting for analysis results | After finishing the local analysis, the results were uploaded to the Kiuwan |
...
website but the second phase (index calculation) timed out. A very common reason for this problem is when your account has reached the maximun number of analyzed locs |
...
for 24h. In this case, your analysis |
...
has been added to the queue and local analyzer |
...
has timed out. |
...
The analysis has not failed |
...
, |
...
it will be processed as soon as the limit is over. |
...
You do not need to execute |
...
the analysis again, |
...
it will |
...
run automatically.
| Visit the log page associated to the analysis. |
...
If there is not enough information in the logs, contact Kiuwan Technical Support. | Yes | |
14 | Analysis finished with an error in Kiuwan | Although local analysis finished successfully, there was |
...
an error during analysis processing in the cloud. | Visit the log page associated to the analysis. |
...
If there is not enough information in the logs, contact Kiuwan Technical Support |
...
| Yes | ||
| 15 | Timeout: killed the subprocess | Local analysis has timed out | Increase timeout value to a higher value. Visit Troubleshooting |
...
to find help on this error. | |
| 16 | Baseline analysis not permitted for current user |
...
The user does not have |
...
the permissions to run baseline analysis for the current application. | Check if the user has “Write" |
...
permissions on the application. | |
| 17 | Delivery analysis not permitted for current user |
...
| The user does not have |
...
| the permissions to run delivery analysis for the current application. | Check if the user has “Execute |
...
| Deliveries" permissions on the application. | |
| 18 | No analyzable extensions found |
...
The source files' extensions are not recognized by Kiuwan. Possible Reasons:
| Visit Troubleshooting - No analyzable extensions found and Kiuwan Supported Technologies to find help on this error.
| |||
| 19 | Error checking license | Error while getting or checking Kiuwan license | Contact Kiuwan Technical Support |
...
Kiuwan’s Cloud Services error
This return code will be deprecated and no longer returned by 2017 Sept 5th.
Return codes >20 will be used instead.
...
Error returned from Kiuwan’s services:
- Denied access (not authorized access)
- Authentication errors
- Application not found (and –c option not set)
- Max number of API calls to Kiuwan services is exceeded
...
Take appropriate action depending on specific error condition.
...
| 21 | Invalid CLI parameter | No arguments specified or unrecognized arguments in the command line | Check the passed arguments to the CLI script. You can also execute agent.[cmd|sh] --help for inline information or refer to Kiuwan Local Analyzer CLI - Command Line Interface. |
...
| 22 | Access denied | Lack of permissions to access |
...
| a Kiuwan entity (application analyses, deliveries, etc) | Review log files to find exact cause and contact your Kiuwan administrator. | |||
| 23 | Bad Credentials | User-supplied credentials are not valid. | Contact your Kiuwan administrator. | |
| 24 | Application Not Found | The invoked action cannot be completed because the associated application does not exist. | Review log files to find exact cause and contact your Kiuwan administrator. | |
| 25 | Limit Exceeded for Calls to Kiuwan API | Limit of max Kiuwan API calls per hour (1000) has been exceeded. | Contact Kiuwan Technical Support if you have any question on your acccount’s limits. | |
| 26 | Quota Limit Reached |
...
| A limit in the Kiuwan account is reached (max number of account’s analysis |
...
| , etc.) | Contact Kiuwan Technical Support if you have any question on your acccount’s limits. | |||
| 27 | Analysis Not Found | The invoked action cannot be completed because the associated analysis does not exist. | Review log files to find the exact cause. Contact Kiuwan Technical Support | |
| 28 | Application already exists | Try to create an already existing application. | Review log files to find exact cause and contact your Kiuwan administrator |
...
| . | ||
| 31 | No engine available | The analysis fails because there |
...
| is no |
...
| available engine to process the source files. This |
...
| could be |
...
| caused by a failed update. | If possible, delete the Kiuwan Local Analyzer installation and download a new one from Kiuwan website. In case it |
...
is not possible to delete the current installation, please contact Kiuwan Technical Support. | |
| 32 | Unexpected error |
...
| Unexpected error | Contact Kiuwan Technical Support. | |
| 33 | Out of Memory | The analysis fails because the configured |
...
| maximum memory is not enough to finish the analysis. | Increase the max memory as described in |
...
| Timeout Killed the Subprocess | ||||
| 34 | JVM Error | Error at JVM level | Contact Kiuwan Technical Support. |