CAST HIGHLIGHT - CLI - Error code 6 - Command Line source dir or output dir validation error

User is getting (6) Command Line source validation error .

 

Action Plan

  1. Check the command to find out if all the parameters passed are correct
  2. Modify the command to point to the proper source directory if in the logs the error "Source directory does not exists" is also seen.  Source directory must exist and should point to the source code.  It should be separate from the working directory.
  3. If an error "Directory containing perl script for analyzer should exist" is thrown 
        1. Then check if this happened when HighlightAutomation.jar is run from outside the directory which has the jar. Please refer CAST HIGHLIGHT - CLI - Running the HighlightAutomation.jar not from the directory the jar is located results in error "Directory containing perl script for analyzer should exist 
        2. Check the command whether the Directory of Perl installation ie 
          perlInstallDir should be mentioned correctly. The default is:  C:\Program Files\Cast\HighlightAgent\perl. Please refer CAST HIGHLIGHT - CLI - Scan can't find the perl executable
        3. Check if the intended paths for --perlInstallDir and --analyzerDir  are set correctly.
          --perlInstallDir
          is the location of the perl installation
          --analyzerDir
          is for the location of the CLI perl analyzers
          The code reader installs perl in the strawberry perl directory and the CLI directory holds the CLI perl analyzers. Please refer Highlight Automated Code Scan (Command Line)

  4. --workingDir is the directory where the scan results and analysis log files are stored in a Highlight created  temporary folder ("HLTemporary").  This should be a unique directory for each analysis to store the analysis results
  5. If the command returns either "syntax of the command is incorrect " or "argument cannot be parsed", then please re-verify your command syntax and check whether the arguments passed are correct.
  6. Use the latest version of the CLI. As the platform evolves (new features, new API endpoints, etc.) are added, the command line also uses some of these functionalities. 

 

Ticket

43479, 49185

Related Pages

CAST HIGHLIGHT - CLI - Error Codes

CAST HIGHLIGHT - CLI - Error code 2 - Command Line options parse error

CAST HIGHLIGHT - CLI - Error code 3 - Command Line techno discovery error

CAST HIGHLIGHT - CLI - Error code 4 - Command Line analysis error

CAST HIGHLIGHT - CLI - Error code 5 - Command Line result upload error

CAST HIGHLIGHT - CLI - Error code 9 - Command Line unziping jars or zip error

CAST HIGHLIGHT - CLI - Docker - Results Upload - Upload failed with code 5 when using Docker

CAST HIGHLIGHT - CLI - ERROR: Failed to fetch company with id when using  --basicAuth

CAST HIGHLIGHT - CLI - Scan fails for an application with an error Failed to fetch company with id XXXSTDERR

CAST HIGHLIGHT - CLI - ERROR Failed to upload submission for application result id='XXXXXX' with company [name='XXX',id='XXXX'] and application [name='XXX',id=XXXXX] message: 400 highlight.server.client.campaignApplication.update.NoAnalysis

CAST HIGHLIGHT - Results Upload - CLI - UTF-8 "\xE7" does not map to Unicode at perl/FileList.pm line xx

Highlight Automated Code Scan (Command Line)

 

Have more questions? Submit a request

Comments

Powered by Zendesk