Description

This page provides the solution for the following error, encountered while opening CMS.

Internal error occurred.
      The application is closing. Call CAST support now providing the log file at C:\ProgramData\CAST\CAST\Logs\CAST-MS-20181105-165044.log.txt

internal Exception : 
       Failed to create log root folder I:\Implementation\Logs

The error can be seen in the below screenshot.

Applicable in CAST Version
Release
Yes/No
8.3.x(tick)
8.2.x

(error)

Observed on RDBMS

RDBMS

Yes/No

Oracle Server (tick)
Microsoft SQL Server (tick)
CSS2 (tick)
Step by Step Scenario

Below is the step-by-step scenario leading to the problem:

  1. Create a new triplet using ServMan.
  2. From an analysis server, open CAST-MS on the newly created Management Base.
  3. In the Preferences, select some folder as Default Log Root Path.
  4. From another analysis server where the same folder does not exist, or either its parent folder, open CAST-MS.
Impact of the Problem

The impact of the problem on the analysis or the dashboard is:

Unable to start CAST-MS to do any analysis

Action Plan

Starting from 8.3, CAST AIP stores the default log root path in Management Base, in the table CMS_PREF_SOURCES. When the schema is new, this field is not set. But this field may have been configured on an analysis server where the folder exists. When the user opens CAST-MS, it tries to create this folder, if it does not already exist on the new analysis server. If the parent folder of the log root path does not exist, then you get this Fatal Error.

  1. Use pgadmin to connect to the Management Base and use the following query to reset the field, then retry to open Cast-MS :

    pgadmin on Management Base
    UPDATE cms_pref_sources 
    SET    logrootpath = NULL; 
  2. Alternatively, if you do not want to update the Management Base, you can create folder I:\Implementation\Logs on disk, and reopen Cast-MS

  3. If the problem you are facing does not match any case listed in this page, contact CAST Technical Support with the following relevant input, so that CAST Technical Support can reproduce the issue.
Notes / Comments


Related Pages