CMS Snapshot Analysis - Run Analyzer - Missing objects - Shell with extension - Missing Shell program artifacts

 This page handle the case when there are missing Shell program artifacts.

Step by Step scenario

1. Run analysis for SHELL application

1. Check if the pre-processor log file was created (refer the following file for the log file location: CAST Management Studio - Information - How to find logs)
2. If the pre-processor log file was created then Check if the pre-processor has crashed, then re-mediate, else go to the next step

   1. In order to check if the pre-processor has crashed,open the SHELL pre-processor log file "shell_pp_report_MM-DD-YYY_HHMMSS.txt" (refer to the following file for the log file location: CAST Management Studio - Information - How to find logs):
      The SHELL pre-processor log file should be as follows:

      Pre-processor for Shell
      Beginning of process...
      - Processing file 'path\file 1'
      
      ....
      
      - Processing file 'path\file n'
      
      End of process.

      If the log file stops before the message "End of process" then the pre-processor has crashed. The pre-processor crashes because of the file indicated in the latest row from the log file (As a consequence the file will be analyzed from the deployment folder instead of the LISA folder).

   2.  As a workaround remove the file that caused the crash of the pre-processor
   3. Then analyse your source code.
3.  If you are using CAST AIP < 8.2.1, then the issue is due to the JAVA_HOME environment variable, as a workaround perform the following steps:
   1. The JAVA_HOME should be set to the JRE of CAST installation directory, you can find it on < CAST installation dir >\jre
      
      
   2. if CAST-MS is already opened, then close it and open again
   3. Run analysis
      
   Starting from CAST AIP 8.2.1 the JAVA_HOME environment variable will be set by the UA on the current JRE from CAST AIP.
   
4. If you are using Shell extension < Shell 1.0.6, then the issue is due to a bug in the launch.bat, as a workaround  perform the following steps:
   
   1. Edit the launch.bat file, you will find it on <CAST installation dir>\CustomPlugins\com.castsoftware.shell\Configuration\Languages\SHELL\prepro
      
   2. Replace the following code line:
      
      By this line of code:
      "%JAVA_HOME%\bin\java.exe" -jar "%local_path%com.castsoftware.shell.prepro.jar" %1 %target_path% Info, you should have a file as follow:
      
      
      
   3.  If CAST-MS is already opened, then close it and open again
   4. Run analysis
5. If the checks above don't resolve your issue then contact CAST Technical Support with the following Relevant input 

Relevant input

1. The name of the object that you are expecting to get.
2. Sherlock export with the following options: Export Logs (feature checked by default), Export Configuration files (feature checked by default), Export Computer Environment (feature checked by default),Export CAST Bases, source code

Ticket # 8515, 8203, 7417, 7342