Created by user-4b453 on Feb 11, 2022
Purpose (problem description)

This page provides the approach to troubleshoot problems you may face during the step Run Reference Finder Analyzer.

Observed in CAST AIP
Release
Yes/No
8.3.x(tick)
8.2.x (tick) 
8.1.x (tick) 
Observed on RDBMS
RDBMS
Yes/No
Oracle Server(tick)
Microsoft SQL Server(tick)
CSS3(tick)
CSS2(tick)
CSS1(error)
Action Plan

  1. Open the CAST-MS log file.

  2. Search for the entry starting Task Run Reference Finder Analyzers.

    INF: 2018-03-09 18:25:38: starting Task Run Reference Finder Analyzers "RP_DATABASE_64978"
INF: 2018-03-09 18:25:38: Q:\8.1.4_Build1506_flat_for_customer/anarun.exe -CONNECT_PROFILE('supcssux1:2280 on CastStorageService.l814_11050_mts_1') -RUN_RP(100155801,100306251,'C:\Users\MTS\AppData\Local\Temp\CAST\CAST\8.1\LISA\3cba398a440c414297c6affac3b40137\Scr64978\JobSettings.xml') -MANAGED(100155801) -SESSION_ID(100306251) -LOG('C:\Users\MTS\AppData\Local\Temp\CAST\CAST\8.1\3cba398a440c414297c6affac3b40137\RP_DATABASE_64978-20180309182533.castlog',TRUNCATE) -LARGESTORAGE('C:\Users\MTS\AppData\Local\Temp\CAST\CAST\8.1','C:\Users\MTS\AppData\Local\Temp\CAST\CAST\8.1','3cba398a440c414297c6affac3b40137/Scr64978') -LOGIN(,CASTCORP\MTS,) -APP(-NOGUI) -FINAL_UPDATE -NOPROGRESS -EXIT
INF: 2018-03-09 18:25:43: Loading ini file: C:\Users\MTS\AppData\Local\Temp\CAST\CAST\8.1\AMRunResult100306251.INI
WRN: 2018-03-09 18:25:43: Ini file not found: C:\Users\MTS\AppData\Local\Temp\CAST\CAST\8.1\AMRunResult100306251.INI
ERR: 2018-03-09 18:25:43: The analysis failed to connect to database (Error code 1).
 Please see the analysis log for further details
 Execution log C:\Users\MTS\AppData\Local\Temp\CAST\CAST\8.1\3cba398a440c414297c6affac3b40137\RP_DATABASE_64978-20180309182533.castlog
 com.castsoftware.java.ExternalException:The analysis failed to connect to database (Error code 1).

     In the above example, the Error message is: ERR: 2018-03-09 18:25:43: The analysis failed to connect to database (Error code 1).

  3. If in CAST MS, in the dependencies tab, there is only one Reference pattern dependency, you will run a command line to execute the Reference Pattern dependency. This should solve the issue: 

    1. Copy the command line, that is just under starting Task Run Reference Finder Analyzers where anarun.exe is executed. In the above example this is:

      Q:\8.1.4_Build1506_flat_for_customer/anarun.exe -CONNECT_PROFILE('supcssux1:2280 on CastStorageService.l814_11050_mts_1') -RUN_RP(100155801,100306251,'C:\Users\MTS\AppData\Local\Temp\CAST\CAST\8.1\LISA\3cba398a440c414297c6affac3b40137\Scr64978\JobSettings.xml') -MANAGED(100155801) -SESSION_ID(100306251) -LOG('C:\Users\MTS\AppData\Local\Temp\CAST\CAST\8.1\3cba398a440c414297c6affac3b40137\RP_DATABASE_64978-20180309182533.castlog',TRUNCATE) -LARGESTORAGE('C:\Users\MTS\AppData\Local\Temp\CAST\CAST\8.1','C:\Users\MTS\AppData\Local\Temp\CAST\CAST\8.1','3cba398a440c414297c6affac3b40137/Scr64978') -LOGIN(,CASTCORP\MTS,) -APP(-NOGUI) -FINAL_UPDATE -NOPROGRESS -EXIT
Open a windows command line, paste the command and execute it:

    2. You can monitor the command execution by locating 'Analysis Runner' process in windows task manager:

      and by observing the log created by the above command line in:

      C:\Users\MTS\AppData\Local\Temp\CAST\CAST\8.1\3cba398a440c414297c6affac3b40137\RP_DATABASE_64978-20180309182533.castlog

      Once 'Analysis Runner' process has finished running (no longer visible in windows task manager), open the above log

    3. If you can see at the end of the reference pattern log, entries confirming that the execution has finished successfully like below example, the issue is resolved.

      2018-03-12 10:45:47.133670 Information; Job execution Execution result=success
2018-03-12 10:45:47.133670 Information ; Job execution Analysis completed 
2018-03-12 10:45:49.320937 Information ; Job execution 0 fatal error(s); 0 error(s); 0 warning(s); 41 information message(s).

    4. If you cannot see at the end of the reference pattern log entries confirming that the execution has finished successfully, then the issue is reproduced. For this visit the page CMS Application - Dependencies - Reference Pattern Dependencies

  4. If there are multiple Reference Pattern dependencies configured for your application:

     

    1. Check what is the Reference pattern dependencies that has failed:
      1. Open the CAST-MS log file
      2. In the CAST-MS log file, check for the line ending Task Run Reference Finder Analyzers <Name of the Reference Pattern> preceded by the error message: Task message: The analysis has not ended correctly

      3. For the below example, the name of the Reference Pattern is RP_Symbolic Resolution_14053

        INF: 2017-11-13 04:04:33:  starting Task Run Reference Finder Analyzers "RP_Symbolic Resolution_14053"
INF: 2017-11-13 04:04:33:  D:\Program Files\CAST\8.2/anarun.exe -CONNECT_PROFILE('CSSSUPPORT:2280 on CastStorageService.tkb_support_local') -RUN_RP(301,307,'Y:\LISA\LISA\5590f09a425645c98023b2a205ed82a7\Scr14053\JobSettings.xml') -MANAGED(301) -SESSION_ID(307) -LOG('Y:\Logs\5590f09a425645c98023b2a205ed82a7\RP_Symbolic Resolution_14053-20171113040425.castlog',TRUNCATE) -LARGESTORAGE('Y:\LISA\','Y:\LTSA\','5590f09a425645c98023b2a205ed82a7/Scr14053') -LOGIN(,SUPPORT\tkbuser,) -APP(-NOGUI) -FINAL_UPDATE -NOPROGRESS -EXIT
INF: 2017-11-13 04:04:38:  About to run JOB_REFERENCE_FINDER_ANALYZER job 'RP_Symbolic Resolution_14053'.
INF: 2017-11-13 04:05:42:  Loading ini file: C:\Users\tkbuser\AppData\Local\Temp\2\CAST\CAST\8.2\AMRunResult307.INI
WRN: 2017-11-13 04:05:42:  Ini file not found: C:\Users\tkbuser\AppData\Local\Temp\2\CAST\CAST\8.2\AMRunResult307.INI
ERR: 2017-11-13 04:05:42: The analysis has not ended correctly (Error code -1073740791).
                            Please see the analysis log for further details
                            Execution log Y:\Logs\5590f09a425645c98023b2a205ed82a7\RP_Symbolic Resolution_14053-20171113040425.castlog
                            com.castsoftware.java.ExternalException:The analysis has not ended correctly (Error code -1073740791).
Please see the analysis log for further details
    Execution log Y:\Logs\5590f09a425645c98023b2a205ed82a7\RP_Symbolic Resolution_14053-20171113040425.castlog
                              com.castsoftware.pmc.features.RunProfiledProcess.handleReturnCode(RunProfiledProcess.java:206)
                              com.castsoftware.pmc.features.RunProcess.executeProcess(RunProcess.java:335)
                              com.castsoftware.pmc.features.RunProcess.documentExecute(RunProcess.java:312)
                              com.castsoftware.mda.impl.MemoryTask.execute(MemoryTask.java:86)
                              com.castsoftware.java.treatment.Task.run(Task.java:377)
                              com.castsoftware.java.treatment.Task.runChildren(Task.java:582)
                              com.castsoftware.pmc.features.RunRFOnDependency.documentExecute(RunRFOnDependency.java:66)
                              com.castsoftware.mda.impl.MemoryTask.execute(MemoryTask.java:86)
                              com.castsoftware.java.treatment.Task.run(Task.java:377)
                              com.castsoftware.java.treatment.Task.runChildren(Task.java:582)
                              com.castsoftware.pmc.features.AbstractRunExecution.documentExecute(AbstractRunExecution.java:70)
                              com.castsoftware.mda.impl.MemoryTask.execute(MemoryTask.java:86)
                              com.castsoftware.java.treatment.Task.run(Task.java:377)
                              com.castsoftware.java.treatment.Task.runChildren(Task.java:582)
                              com.castsoftware.mda.impl.DocumentTask.execute(DocumentTask.java:44)
                              com.castsoftware.java.treatment.Task.run(Task.java:377)
                              com.castsoftware.java.treatment.Task.runChildren(Task.java:582)
                              com.castsoftware.mda.impl.MemoryAction.execute(MemoryAction.java:272)
                              com.castsoftware.pmc.actions.application.RunAnalysis.execute(RunAnalysis.java:493)
                              com.castsoftware.mda.impl.MemoryAction.topExecute(MemoryAction.java:265)
                              com.castsoftware.mda.impl.MemoryAction$MemoryActionTask.documentExecute(MemoryAction.java:383)
                              com.castsoftware.mda.impl.MemoryTask.execute(MemoryTask.java:86)
                              com.castsoftware.java.treatment.Task.run(Task.java:377)
                              com.castsoftware.java.treatment.execution.TaskExecutor$TaskMainThread.run(TaskExecutor.java:103)
                              java.lang.Thread.run(Thread.java:744)
INF: 2017-11-13 04:05:42:  Task message: The analysis has not ended correctly (Error code -1073740791).
Please see the analysis log for further details
    Execution log Y:\Logs\5590f09a425645c98023b2a205ed82a7\RP_Symbolic Resolution_14053-20171113040425.castlog
INF: 2017-11-13 04:05:42:  Log file: Y:\Logs\5590f09a425645c98023b2a205ed82a7\RP_Symbolic Resolution_14053-20171113040425.castlog
INF: 2017-11-13 04:05:42:  ending Task Run Reference Finder Analyzers "RP_Symbolic Resolution_14053" 
      4. Copy and execute the command line that is just under  the line starting Task Run Reference Finder Analyzers where anarun.exe is executed.

      5. If you can see at the end of the reference pattern log file, entries confirming that the execution has finished successfully like:

        2018-03-12 10:45:47.133670 Information; Job execution Execution result=success
2018-03-12 10:45:47.133670 Information ; Job execution Analysis completed 
2018-03-12 10:45:49.320937 Information ; Job execution 0 fatal error(s); 0 error(s); 0 warning(s); 41 information message(s).

       

    2. In CAST MS, in the Dependencies tab select all the Reference Pattern dependencies that did not run yet and execute them:
      1. Check what are the Reference pattern dependencies that have run successfully:
        1. Open the CAST-MS log file
        2. Search for the lines ending Task Run Reference Finder Analyzers <Name of the Reference Pattern> not preceded by Error messages.
        3. The name of the Reference Pattern you have found will not be executed again.
        4. Select all the other Reference Pattern dependencies except the one that has previously been executed by command line.
        5. Right click and select Run reference pattern on dependency.
  5. If the above point does not help you to solve the issue, contact CAST Technical Support with the Relevant Input for CAST Technical Support to reproduce the issue.
Notes/comments

 

Related Pages