Analysis Error Codes Reference – Kiuwan

Please go here to see the return error codes in Kiuwan Local Analyzer.

Error Code	Error Name	Description
AN-1	Unexpected error	Internal unspecified analyzer error. A new support ticket is issued automatically to diagnose the problem. Please contact Kiuwan Technical Support.
AN-2	Error during CQM Indicator calculation	Internal error calculating your Kiuwan indicators based on the CQM quality model.A new support ticket is issued automatically to diagnose the problem. Please contact Kiuwan Technical Support.
AN-3	ZIP file is corrupted or empty	The ZIP file with the application code is empty or corrupted.Check your packaging process and analyze it again.
AN-4	There is no analyzable file in the received files	Kiuwan couldn't find any compatible source code file in your ZIP file or repository.Please visit Kiuwan Supported Technologies for the current list of supported technologies and extensions.
AN-5	The static analysis report file is missing.	Internal error generating the analysis results.A new support ticket is issued automatically to diagnose the problem. Please contact Kiuwan Technical Support.
AN-6	Could not extract the ZIP file.	Corrupt application source code ZIP file, Kiuwan was unable to open it.Check your packaging process and analyze it again.
AN-7	Unable to parse any file.	This error is produced when Kiuwan could not analyze any* source file.As Kiuwan tries to parse the source files before analyzing them, all of them failed during the parsing phase.This is quite an unusual situation.Below you can find some of the most common reasons: If the analysis contains only one file* (or very few files) the whole analysis fails, see the possible reasons below but try to analyze a bigger application. There are syntax errors in source files Source code might not be conformant to language grammar. Please review the source code and run the analysis again. The encoding used for the analysis is not correct Action: By default, UTF-8 is considered, but if your source files are better supported by any other encoding, you should change it, and the number of processed files will be higher. To do it, please take a look at the next URLs: If you are using Kiuwan Local Analyzer: Kiuwan Local Analyzer (Global Configuration section) In cases where files can be processed by different engines (for example, .sql files can be processed by several engines: PL-SQL, Informix, Transact-SQL), a wrong engine was selected. Action: please select the proper engine and run the analysis again If you are analyzing COBOL, please be sure that the COBOL files belong to one of the supported dialects. Currently, COBOL versions supported by Kiuwan are COBOL85, OS/VS COBOL II, Enterprise COBOL for z/OS v5, ILE COBOL 5, MicroFocus COBOL NetExpress 5, COBOL Tandem, AcuCOBOL-GT. If the code belongs to another COBOL dialect, please let us know so we contact our product department to check the roadmap for it. If your COBOL code belongs to supported COBOL dialects, please configure properly the COBOL analysis. You can modify processing options such as to allow free format COBOL or first columns comments. You can do it in Kiuwan Local Analyzer by clicking Configure and selecting the COBOL block configuration option. If you are analyzing C/C++, a common reason for analysis errors is an incorrect resolution of header files and macros during the preprocessing phase. A correct resolution is essential for a complete and correct C/C++ static code analysis. To properly configure the C/C++ analysis, you need to configure some options available in Kiuwan Local Analyzer. For specific information about how to configure these options, we suggest you read Configure an analysis with C or Cpp If none of these actions solves the problem, please contact Kiuwan Technical Support A new support ticket is issued automatically to diagnose the problem with those files.
AN-8	Unable to get access to the source file.	Internal error reading the unzipped source files.A new support ticket is issued automatically to diagnose the problem. Please contact Kiuwan Technical Support.
AN-9	Could not extract the rulesets.	Internal error accessing the quality model rules for the analysis.A new support ticket is issued automatically to diagnose the problem. Please contact Kiuwan Technical Support.
AN-10	Analysis timeout has been produced.	You can get this error in case this maximum time is reached. Common reasons are the number of source code files for a specific language is too big or there is a specific file that is too big or too complex for the analyzer.The recommended solution to this problem is to analyze locally using Kiuwan Local Analyzer (KLA) and configure the max analysis time parameter.Please visit the Kiuwan Local Analyzer documentation page for information on the installation and usage of Kiuwan Local Analyzer.
AN-13	The analyzable number of lines is exceeded for the whole account.	LOC for all your applications exceeds the quota assigned to your subscription.You can delete some application or big analysis to decrease the analyzed LOC count, and so, continue analyzing.
AN-16	Could not obtain the license for this analysis.	There is some problem generating your license to execute an analysis.A new support ticket is issued automatically to diagnose the problem. Please contact Kiuwan Technical Support.
AN-17	The daily limit of success analyses for this application has been exceeded.	Your application has achieved the number of success analyses allowed to execute per day.Please try to analyze your application tomorrow.
AN-18	The limit for the allowed number of analyses for your subscription has been achieved.	Your account has achieved the number of success analyses allowed to execute along with your subscription.
AN-19	Limit for analyzed LOC for your subscription has been achieved.	Your account has achieved the number of LOC that can be analyzed along with your subscription.This means that you cannot execute more analyses in your account.If you need to execute more analyses, please contact us to ask for a new subscription.
AN-20	Too many defects in memory	The analysis uploaded to the server or the promotion you are trying to perform is extremely big and has too many defects to be processed. Please verify the size of the code being analyzed - consider excluding folders that are not part of your development such as referenced open source libraries, splitting the analysis into parts, or reevaluate the rules included in the model you are using - maybe you are checking compliance with some methodology your code does not follow systematically.

Related to