Description
 The page provides you with the information about the warning "classpath entry can not be resolved" and the procedure to counter the warnings.
Observed in CAST Extension

Release

Yes/No

JEE 1.1.x(coche)
JEE 1.0.x(coche)
Observed on RDBMS
RDBMS
Yes/No
Oracle Server(tick)
Microsoft SQL Server(tick)
CSS3(coche)
CSS2(tick)
CSS1(error)
Step by Step Scenario
  1. Discover the source.
  2. Accept delivery and run the analysis.
  3. Open logs and observe that you have following warnings in the logs.

Action Plan
  1. This error message means that a wrong source path has been defined. Double-click on the warning message to find out the wrong source path as seen in the above screenshot.
  2. Find out why the analyzer is looking for source in this path. There can be several reasons
    1. Check if the wrong path is defined in variable CAST_PROGRAM_FILES_COMMON_PATH in configuration file <INSTALL_FOLDER>\CastGlobalSettings.ini.
      If it is the case, then change the value to an existing folder. The standard path for the EnvProf folder is in the CommonFiles folder of your operating system \Program Files (x86)\Common Files\CAST\CAST\EnvProf\
      You can change the place analyzer should look for these files in the CastGlobalSettings.ini by changing the value for the variable CAST_PROGRAM_FILES_COMMON_PATH = <New Path> but make sure all the files from the default folder are available here.
      See Appendix - Modifying default CAST data storage locations for understanding different variables in CastGlobalSettings.ini

    2. Check in Cast-Ms if the path is defined in the Classpath section of Analysis tab, at the Application level or at the Analysis Unit level.
      If the wrong path is one of the entries, then remove it or replace it by an existing folder.
      See CMS - J2EE Technology options
    3. Check the custom Environment Profiles. In the Services View, right-click on your Knowledge Base and select Environment Profile → Manage
      In the custom Environment Profiles, you may have "Archive Folder" or "Archive Files" entries. If the wrong path is one of them, then remove it or replace it by an existing foler
      See CMS - J2EE Environment Profiles



  3. If this does not help, then contact CAST Technical Support with the Relevant Input to reproduce issue
Impact on Analysis Results and Dashboard

Java Files will not be analyzed so there will not be any objects created..

Notes/comments

Related Pages