Page tree
Skip to end of metadata
Go to start of metadata
*Purpose

This page will help you to solve problems related to the Package feature.

For more information, refer to:

Official documentation:

*Observed in CAST AIP
Release
Yes/No
8.3.x(tick)
8.2.x(tick)
8.1.x(tick)
8.0.x(tick)
7.3.x(tick)
*Observed on RDBMS
RDBMS
Yes/No
Oracle Server(tick)
Microsoft SQL Server(tick)
CSS2(tick)
Action Plan
  1. Identify the type of issue and the Package step where the issue occurs. To do so, you have two possibilities:
    1. Either use the Package window.
      1. See if there are error messages or warnings in the Results column
      2. For performances issues, check the longest durations in the Duration column
      3. The Package step where the issue occurs is given in the Task column. In the below example, the step is the Extraction.

      4. Open the log file corresponding to the step where the issue occurs (See Delivery Manager Tool logs to find out where the logs are located):
        1. Extraction Log file if the step is Extraction 
        2. Scan Log file if the step is Scan 
        3. Discovery Log file if the step is Discovery 
        4. Selection Log file if the step is Selection 
        5. Validation Log file if the step is Validation 
        6. Remediation Log file if the step is Remediation 
    2. Or check in the log files generated by the DMT when Packaging a version.
      1. Open the Extraction Log, Scan Log, Discovery Log, Selection Log, Validation Log, Remediation Log located at Delivery Manager Tool logs. To open them, use the CASTLOG2 viewer located in <CAST INSTALLATION FOLDER>\DeliveryManagerTool\CastLog2Viewer.exe
      2. Check if there are ERROR, WARNING messages or performances issues in each of these logs. For example, the WARNING message Missing translation for id prevents some objects to be packaged
        Figure 3
        The message An error has occurred during command processing ... which prevents the package to be successful
    3. For Projects not found and alerts (Package Content tab), the Package step is Validation

  2. For System can not find the specified file message, an Antivirus program running on the machine hosting the DMT may cause the issue. These can be intermittent and can be seen during the Extraction, Discovery or Scan step. To resolve this issue, exclude the following files from the antivirus program:
    1. DeliveryManagerTool.exe
    2. DeliveryManagerTool-CLI.exe
    3. DeliveryManagerTool-Help.exe
    4. CastLog2Viewer.exe
    5. CAST-DeliveryEngine.jar
    6. CAST-DeliveryEngineCLI.jar
  3. When adding a new version from AIP Console which uses the JEE File Discoverer since the source code does not contain a .project/.pom file, you will come across the below messages in the selection.castlog2 file

    This message means the analysis unit associated to the project is incomplete as explained here

    This message will not let create an analysis unit with respect to the incomplete package as well. 

    When you have this message, you need to manually open Delivery Manager Tool and uncheck the selection rule - 


    After which you can run packaging and Delivery from Delivery Manager Tool.

    Do a set as current version and re-sync the application in AIP Console to continue with analysis and snapshot

  4. Navigate to the step showing the issue 
  5. If you do not find the information you are looking for or solution for your problem, contact CAST Technical Support with Relevant Input.

Relevant Input

If the issue occurs during the Packaging - Extraction Step 

Figure 6

  • The source code is required :
    • If you are packaging a local file system source code, provide it manually.
    • If you are packaging a source that requires an online connection, connection details and detail about the source to be package are required.
  • Sherlock Output. The option to select : Export Configuration files. If you launch DMT via AIC Portal and your delivery has not been successful, don't run Sherlock and retrieve the DELIVERY folder manually instead, at the following location on the machine you have launched DMT: C:\Users\<USER>\AppData\Local\CAST\CAST\DMT.
  • The Plugins folder that is in the delivery folder
  • Screenshot showing the issue.

If the issue occurs during the Packaging - Scan Step

 Figure 7

  • Sherlock Output. The option to select : Export Configuration files and Export Source code. If you launch DMT via AIC Portal and your delivery has not been successful, don't run Sherlock and retrieve the DELIVERY folder manually instead, at the following location on the machine you have launched DMT: C:\Users\<USER>\AppData\Local\CAST\CAST\DMT.
  • The Plugins folder that is in the delivery folder
  • Screenshot showing the issue.

For other issues (Packaging - Discovery / Selection / Validation / Remediation steps)

  1. If you launch DMT via AIC Portal and your delivery has not been successful :
    • Don't run Sherlock and retrieve the DELIVERY folder manually instead, at the following location on the machine you have launched DMT: C:\Users\<USER>\AppData\Local\CAST\CAST\DMT.
    • If you are using the Java file discover plugins or C++ file discoverer plugins, the source code is requested.
    • Screenshot showing the issue.
  2. If you launch DMT via CAST MS :
    • Sherlock Output. The option to select : Export Configuration files. 
    • For the Java file discover and C++ file discoverer Plugins, the source code is requested.
    • Screenshot showing the issue.
Notes/Comments


Related Pages

  • No labels