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

Check your packaging process and make sure that the compatible source code files are included.

This is the list of supported extensions by language:

• Abap: .bsp .abap
• ActionScript: .as
• ASP.NET: .asax .ascx .ashx .master .asmx .aspx
• C: .pc .c .h
• Cobol: .cpy .pco .cbl .cob
• C++: .pc .cpp .h .hpp .hh .cc
• C#: .cs
• HTML: .html .htm .xhtml
• Informix: .sql .4gl
• Java: .java
• JavaScript: .js
• JCL: .jcl .prc
• JSP: .jspx .jsp .xhtml
• Natural: .nls .nlp .nsh .nss .nlm .nlh .nsp
• Objective-C: .h .m
• Oracle Forms: .oforms
• Perl: .perl .ph .pl .pm
• PHP: .php6 .php3 .phps .php4 .php5 .phtml .php
• PL-SQL: .sf .spb .prc .sp .trg .pkb .st .spp .sql .plsql .fnc .pks .pck .sps
• Powerscript: .srs .sra .srm .srw .srx .sru .srf
• Python: .python .py
• RPG IV: .rpg4 .dspf .mbr .rpg .rpgle
• Trabsact-SQL: .tsql .sql .sp
• VB6: .bas .frm .cls
• VB.net: .vb

AN-5 — 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 again.

AN-7 — Unable to parse any file.

This error is produced when Kiuwan could not analyze any source file in the application source code.

As Kiuwan (either by Kiuwan Local Analyzer or by uploading source files zip to the cloud) tries to parse the source files before to analyze them, all of them failed during the parsing phase.

This is quite an unsual 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: https://www.kiuwan.com/docs/display/K5/Code+analysis+using+the+downloaded+agent (Global Configuration section)
    • If you analyzing in the cloud (uploading a ZIP): https://www.kiuwan.com/docs/display/K5/Analysis+Management
• 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 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 v3.4, ILE Cobol 5, MicroFocus Cobol and Cobol Tandem. If the code belongs to another Cobol dialect, please let us know it 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 on Configure button and selecting Cobol block configuration option.
• If you are analyzing C/C++, a common reason of analysis errors is an incorrect resolution of header files and macros during 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 to read the posts about this subject in Kiuwan's blog :  
    • https://www.kiuwan.com/blog/analyzing-c-with-kiuwan/
    • https://www.kiuwan.com/blog/c-analysis-with-kiuwan-part-ii/

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

Kiuwan analysis engine is configured by default to analyze all the source code file, for each language, for 60 minutes. It should be more than enough for 99% of applications.

You can get this error if the number of source code file for a specific language is too big; or there is a specific file that is too big or too complex for the analyzer.

A possible solution is to split your application code in two different applications. If this workaround doesn't work for you you can configure the max analysis time parameter using the local Kiuwan Local Analyzer and analyze this application locally. Please visit Kiuwan Local Analyzer documentation page for information on installation and usage of Kiuwan Local Analyzer.

In the case you consider that the application should have been analyzed in less than 60 minutes, please contact Kiuwan Support Team (Troubleshooting#ContactKiuwanTechnicalSupport) to diagnose your particular application.

AN-13 — Analyzable number of lines are exceeded for the whole account.

LOC for all your applications exceed 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 analysis allowed to execute per day.

Please try to analyze your application tomorrow.

AN-18 — Limit for allowed number of analyses for your subscription has been achieved.

Your account has achieved the number of success analyses allowed to execute along 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 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 new subscription.