Page tree
Skip to end of metadata
Go to start of metadata
Purpose (problem description)

This page will help you to investigate the error after login "Application failed to start" 

           


Dashboard Package version


Release

Yes/No

13.x(tick)
12.x(tick)
11.x

(tick)

10.x(tick)
Observed in RDBMS

RDBMS

Yes/No

Oracle Server(error)
Microsoft SQL Server(tick)
CSS3(tick)
CSS2(tick)
Step by Step scenario
  1. Deploy AAD war and configure
  2. Access AAD
  3. Observe error
Action Plan

Perform the below actions

  1. If you observe the above mentioned error after login then please ensure war configuration is correct by following - Installation and deployment process
  2. If configuration is correct then please check rest-api log to see the error/warning.
    1. If you see below error in log:
    2. Check idle connections in pgadmin and terminate them as shown below:
    3. Once done. Try to login to dashboard.
  3. If you observe below error in rest-api log :

      2021-03-23 07:23:12,607| ERROR | main | com.castsoftware.adg.webservice.dao.portfolio.TechnologyDao | Skip snapshot [name:'rct4-common', date:'Mon Mar 15 14:17:00 CDT 2021', id:'17220'], because of inconsistent technological object [id:'
     8799']
    2021-03-23 07:23:12,608| ERROR | main | com.castsoftware.adg.webservice.dao.portfolio.TechnologyDao | Skip snapshot [name:'rct4-common', date:'Mon Mar 15 14:17:00 CDT 2021', id:'17220'], because of inconsistent technological object [id:'
    1. Run the below query on central to check the corruption related to technological objects :

      SELECT DISTINCT doi.snapshot_id,
                      doi.object_id,
                      doi.object_type_id,
                      dot.object_type_name AS OBJECT_NAME,
                      'Technologic '
                      || dot.object_type_name
                      || ' object'        AS OBJECT_DESCRIPTION,
                      dot.object_type_name AS OBJECT_FULL_NAME
      FROM  dss_link_info dli
            JOIN dss_object_info doi
              ON doi.snapshot_id = dli.snapshot_id
                  AND doi.object_id = dli.next_object_id
            JOIN dss_object_types dot
              ON dot.object_type_id = doi.object_type_id
            LEFT JOIN dss_objects dos
                    ON dos.object_id = dli.next_object_id
      WHERE  dli.link_type_id = 2
            AND dos.object_id IS NULL
      
    2. ]If the query returns result then run the below query to fix the corruption in central :

      insert into DSS_OBJECTS (OBJECT_ID, OBJECT_TYPE_ID, OBJECT_NAME, OBJECT_DESCRIPTION, OBJECT_FULL_NAME)
      select distinct doi.OBJECT_ID, doi.OBJECT_TYPE_ID, dot.OBJECT_TYPE_NAME as OBJECT_NAME,
      'Technologic ' || dot.OBJECT_TYPE_NAME || ' object' as OBJECT_DESCRIPTION, dot.OBJECT_TYPE_NAME as OBJECT_FULL_NAME
      from DSS_LINK_INFO dli
      join DSS_OBJECT_INFO doi
      on doi.SNAPSHOT_ID = dli.SNAPSHOT_ID and doi.OBJECT_ID = dli.NEXT_OBJECT_ID
      join DSS_OBJECT_TYPES dot
      on dot.OBJECT_TYPE_ID = doi.OBJECT_TYPE_ID
      left join DSS_OBJECTS dos
      on dos.OBJECT_ID = dli.NEXT_OBJECT_ID
      where dli.LINK_TYPE_ID = 2 and dos.OBJECT_ID is null
    3. Once done, consolidate the central to measurement schema.
  4. If the above steps do not solve your issue contact CAST Technical Support. with the following relevant input

 

Notes/comments

Ticket # 20264

Related Pages


  • No labels