This page will help you solve problems related to CAST AIP Console.

CAST AIP Console is a front end web application which provides a means to configure, run, and manage CAST AIP analyses on multiple analysis machines.

CAST AIP Console gives an Application Overview showing the application state regarding versions, analysis and snapshots, Technologies and framework identification and Matching technology between Tech Survey and source code delivered

For more information, refer to:

Applicable Platform

AIP Platform


CAST AIP 8.3(tick) 
AIP Console VersionYes/No
AIP Console 1.8.x  or greater(tick)
Action Plan
  1. If you are starting AIP Console or AIP Node and receiving an windows error code 1, then make sure that the Java version you installed matches your architecture (if you have a 64-bit OS, then you should have a 64-bit Java).  See the screenshot below for an example of the error in this case:


    • You can check the event viewer logs for the below error as well - 

    • When you observe the above error, you need to check the Java used by the service. for this you can navigate to the aip-node-servicew.exe file in the installation folder and check the Java path - 

    • Make sure the Java path exists and is supported by AIP Console as per our deployment requirements - Deployment requirements
  1. If the node has become out of sync with the console or if there is some corruption in the setup, then:
    1. If you have AIP Console version < 1.15.x, you can do a delete with the KeepData option followed by an import to attempt to clear this up.
      1. The delete CLI is shown in the documentation here (again make sure you use the KeepData option):  Delete an Application via CLI
      2.  The import is shown in the documentation here in step 3:  Import an Application managed with CAST Management Studio into AIP Console
    2. If you have AIP console verison => 1.15.x, then there is a resync option to resync any changes done in CAST-MS with the AIP console
      1. Related documentation: 

        Resync Option

  2. If using the CLI in automation, make sure that the CLI tools extension is compatible with the AIP Console version you are running to avoid compatibility issues.  This is available on the Extend website:

    CLI Tools

  3. If using the CLI and you receive an error indicating a 404 response, make sure that your syntax of the CLI is correct and that you might not be missing a '-' for a flag (such as using the flag app-guid and making sure it is --app-guid "XXX" and not -app-guid "XXX").
    1. The specific error may look like the following:
      1. com.castsoftware.aip.console.tools.core.exceptions.ApiCallException: Response code from API was unexpected : 404
  4. If you have postgres hosted on a linux machine, AIP Console processes for example,  install extension/ run analysis can fail when it crosses a 2 hour time frame.
    This is because there is a timeout set on the linux environment by default (7200 seconds) as mentioned in the documentation here -  How to find the connection time-out value in linux? 
  5. Proxy details in AIP Console should be set as below - 
    1. If there is proxy set on the Windows machine, you need to select the System Proxy option in AIP Console
    2. If you are using a proxy script, you need to select the Manual Proxy option in AIP Console and provide the host and port details of proxy. 
    3. If you are using Extend Proxy instead of CAST Online Extend Server, you do not need to add another proxy. You need to select the No proxy option.
  6. If you come across the red ribbon error on the AIP Console GUI, like below -   
    2. Check cmsapi/webi logs. You may come across issues such as - "Unable to find com.castsoftware.aip.management.entities.cms.analysis.AnalysisUnit with id <AU id>"
      1. You need to check whether there is an analysis unit that is missing - CAST-MS validation view can provide this information.
      2. You need to check whether there is a dependency that is missing its target - CAST-MS validation view can provide this information. 
      3. You need to check whether any module is missing a filter - CAST-MS validation view can provide this information.
  7. If the logs have too many warnings or errors, it can result in the analysis crashing with no further update in the logs of AIP Console but CAST-MS shows analysis is complete and the status in CAST-MS is accurate. To limit the number of log messages, you can change the parameter logging:summary:limit to 1000 in the application.yml file of the Node data folder.    
  8. When you are importing an application to AIP Console, and after clicking on PROCEED the screen does not go further. The aip-node log will throw the below message - 

    Error Stack
    Caused by: java.nio.file.InvalidPathException: Illegal char <
    > at index 76: C:\ProgramData\CAST\AIP-Node\delivery\{c1373121-e992-42cf-b48c-c1fdb7949828}
    at java.base/sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182) ~[na:na]
    at java.base/sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153) ~[na:na]
    at java.base/sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77) ~[na:na]
    at java.base/sun.nio.fs.WindowsPath.parse(WindowsPath.java:92) ~[na:na]
    at java.base/sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:232) ~[na:na]
    at java.base/java.nio.file.Path.of(Path.java:147) ~[na:na]
    at java.base/java.nio.file.Paths.get(Paths.java:69) ~[na:na]
    at com.castsoftware.aip.management.entities.local.hibernate.types.PathConverter.convertToEntityAttribute(PathConverter.java:26) ~[aip-management-services-2.7.1.jar!/:2.7.1]
    at com.castsoftware.aip.management.entities.local.hibernate.types.PathConverter.convertToEntityAttribute(PathConverter.java:10) ~[aip-management-services-2.7.1.jar!/:2.7.1]
    at org.hibernate.metamodel.model.convert.internal.JpaAttributeConverterImpl.toDomainValue(JpaAttributeConverterImpl.java:45) ~[hibernate-core-5.4.33.jar!/:5.4.33]
    at org.hibernate.type.descriptor.converter.AttributeConverterSqlTypeDescriptorAdapter$2.doConversion(AttributeConverterSqlTypeDescriptorAdapter.java:140) ~[hibernate-core-5.4.33.jar!/:5.4.33]
    ... 58 common frames omitted

    The above error means there is an illegal character found when trying to access the delivery folder. Specific to this case, we observed that the table cms_pref_sources was updated wrongly to contain a newline character in the column - server path. To solve the issue we need to make sure the delivery folder is set correctly in the table and is accessible.

  9. Otherwise, select the section you are interested in.
  10. If the problem you are facing does not match any case listed in this page, report your problem to CAST Technical Support and provide the below Relevant input for CAST Technical Support to reproduce the issue.  

Relevant input

  • CAST Support Tool (CST) - alias Sherlock export with the following options CAST Bases Checker, Export Logs, Export Configuration files, Export Computer Environment, Export CAST Bases with Management Base, Knowledge Base, Central base, Measurement Base  Export source code and CAST AAD/AED Folder. 
  • Screenshot of issue with detailed explanation of the problem
  • Version of the AIP Console used as well as CAST AIP
  • CMSAPI logs located here:  <AIP_console_installation>\AipNode\data\logs\cmsapi\
  • WEBI logs located here:  <AIP_console_installation>\AIPConsole\data\logs\
  • For Offline extend issues, include the offline extend logs - <offline line extend install directory>\ExtendService\logs (This is deprecated)
  • Extend proxy issues - Extend proxy logs C:\Program Files\Cast\Extend\logs and Extend Proxy db. %ProgramData%\Cast\Extend\extend-proxy-db.sqlite
  • The external logs in the directory:  <AIP_console_installation>\AipNode\data\logs\external_logs

Related Pages