The fatal error can occur in every step of the Analysis. It is visible in the Log file. 

Observed in CAST AIP
Observed on RDBMS
Step by Step scenario
  1.  Package and Deliver an application.
  2.  Set the version as current Version.
  3.  Run the Analysis.
  4.  An Error / Fatal error is raised in the log file and the analysis stops.
Action Plan

Perform the following steps:

  1. If the error is related to network issue like The specified network name is no longer specified as seen below in the screen shot, establish a new connection by re-launching CAST-MS and run the analysis which should run fine.
  2. Check If the fatal error is due to lack of disk space on the database server as shown below

    Analysis log file
    ERROR:  could not extend file "base/12002/t8_1006387": No space left on device.
    HINT:  Check free disk space..
    CONTEXT:  SQL statement "create index IDX_TMP_WK_ID on TMP_WK_ID (SOURCE_ID, TARGET_ID)".
    PL/pgSQL function amt_p_diff_lnk(integer) line 333 at SQL statement.
    SQL statement "select AMT_P_DIFF_LNK (I_IDSESSION)".
    PL/pgSQL function amt_p_build(integer) line 96 at SQL statement.
    SQL statement "select AMT_P_BUILD (I_IDSESSION)".
    PL/pgSQL function cache_processid(integer,integer) line 21 at SQL statement (Severity 1, Msg No 1).
    1. Check that all the configuration/hardware requirements details mentioned in CAST AIP for Dashboards were fulfilled.

    2. If all requirements were fulfilled, then contact CAST Technical Support with the following Relevant input

  3. Check if the issue is due to connectivity timeout to the database server.  This occurs more often in larger analyses.

    1. Errors usually are:
      1. An input/output error occurred while sending to the server
      2. Database BCP operation dbbcp_init failed on table

      3. An existing connection was forcibly closed by the remote host
    2. To resolve:
      1. In the postgresql.conf file for the postgres server, set the following parameter:
        1. tcp_keepalives_idle = 600

      2. Restart the postgres server with this change
  4. Check if the error is related to lack of memory in the analysis machine as seen in the analysis log below

    Analysis log file

    MemMngrDLL_AllocBlock(): Cannot allocate a new user area of bytes.
    A memory allocation call failed while creating a node.
    MngTreeDLL_MkTreeElement() - Not enough memory for building a new 'NODE'.

    1. Add some memory to the analysis machine.
    2. Split the analysis unit 
  5. Check if the error is related to a lack of memory in the postgres database.  This can be more of an issue in machines in which the analysis is running on the same machine as the database.  Check the postgres database log for the following errors, if any are found then memory should be increased and the analysis rerun:
    1. could not reattach to shared memory
    2. CreateProcess call failed
    3. could not fork <process>
  6. Check if the error is due to corruption in the installation of CAST AIP
    Looking at the screenshot above we can see that the issue is coming due to missing dll / error executing the dll present in the CAST binaries folder which is due to corruption in the installation. So the solution is to re-install CAST AIP
  7. Check if the error is due to a corrupted connection profile in the CWProfileConnection.ini file.  For more details please refer CMS Snapshot Analysis - Run Analyzer - Fatal Error - Failed to connect on local database - connection profile may be badly configured 
    1. Verifying the local database name in the analysis may assist with this - see the analysis message 'Using Knowledge Base on Schema xxx' and verify that xxx is the correct local schema
    2. If not, edit the CWProfileConnection.ini file to remove any duplicated corrupted items, re-sync in CAST-MS, and then verify that the analysis properly runs.
  8. If the fatal error is an SQL Error, navigate to the page for SQL Error
  9. If the Fatal Error occurs during the Parsing Step, try to remove the last file parsed before the Fatal Error. If this does not solve the issue, you may iterate this approach 2 or 3 times. If removing the 3 files does not solve the issue, then give up this approach and proceed to the next step.
  10. If the Fatal Error occurs during the saving Step with error : Error executing actions. Error message: Analysis saving could not be finalized,  follow this page: CMS Snapshot Analysis - Run Analyzer - Fatal Error - Error executing actions Error message Analysis saving could not be finalized 

  11. Else, check CMS Snapshot Analysis - Run Analyzer - Fatal Error - Analyzer is running out of memory - This may occur under disk full condition
  12. Else, remove all the empty files (file size 0) and files fully commented (there is no line of codes, or all code lines are commented out). Run the analysis again.
  13. If the issue still occurs, navigate to the below pages
  14. If you do not find the information you are looking for or solution for your problem, in this page, contact CAST Technical Support with the following Relevant input

Relevant input

  • Enable the memory traces and provide the log file containing the traces.
  • The AMT IN Tables if the fatal error occurs during the saving step.
  • CAST Support Tool (CST) - alias Sherlock. Option to select : Export Logs, Export CAST Database for Management Base only (also Knowledge Base if the fatal error occurs during the saving step), Export Configuration files, Export source code.
  • Screenshot showing the Fatal Error in CAST MS.

Related Pages