Page tree
Skip to end of metadata
Go to start of metadata

What are the return codes of Kiuwan Local Analyzer?

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 page 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 page 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 page 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 page 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

15Timeout: killed the subprocessLocal analysis has timed out

Increase timeout value to a higher value.

Visit Troubleshooting page to find help on this error.

 
16Baseline 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.

 
17Delivery analysis not permitted for current userThe 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. 
18No analyzable extensions found

The source files' extensions are not recognized by Kiuwan.

Possible Reasons:

  • Source code directory does not exist or does not contain source code files
  • If you have modified the default supported extensions (Kiuwan Supported Technologies) please check that your source files match any of them
  • If you are using default extensions, check if you are analyzing a Kiuwan supported technology and, if so, check that the extensions of your files are among those considered by Kiuwan for that technology.

Visit Troubleshooting - No analyzable extensions found  and Kiuwan Supported Technologies to find help on this error.

 

 
19Error checking licenseError while getting or checking Kiuwan licenseContact Kiuwan Technical Support 
21Invalid CLI parameterNo arguments specified or unrecognized arguments in the command lineCheck 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. 
22Access deniedLack of permissions to access a Kiuwan entity (application analyses, deliveries, etc)Review log files to find exact cause and contact your Kiuwan administrator. 
23Bad CredentialsUser-supplied credentials are not valid.Contact your Kiuwan administrator. 
24Application Not FoundThe invoked action cannot be completed because the associated application does not exist.Review log files to find exact cause and contact your Kiuwan administrator. 
25Limit Exceeded for Calls to Kiuwan APILimit 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. 
26Quota Limit ReachedA 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. 
27Analysis Not FoundThe invoked action cannot be completed because the associated analysis does not exist.

Review log files to find the exact cause.

Contact Kiuwan Technical Support

 
28Application already existsTry to create an already existing application.Review log files to find exact cause and contact your Kiuwan administrator. 
30Delivery analysis not permitted: baseline analysis not foundA delivery analysis is being executed but there's not any baseline analysis for that application.Before to run a delivery analysis, a baseline analysis must exist for that application. 
31No engine availableThe 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.

 
32Unexpected errorUnexpected errorContact Kiuwan Technical Support. 
33Out of MemoryThe analysis fails because the configured maximum memory is not enough to finish the analysis.Increase the max memory as described in Troubleshooting - Out of Memory 
34JVM ErrorError at JVM levelContact Kiuwan Technical Support.