Purpose (problem description)

This page addresses an issue where Enlighten will crash when trying to open a saved view.

You may not also be able to view the model picture preview in Enlighten or in the Discovery Portal on the dashboard. This is related to the issue with saving the view in Enlighten as Enlighten saves the model picture with the view. 

A sample screenshot of Enlighten not showing the model picture preview is shown below: 

Another side-effect of this issue is that in the dashboard's Discovery Portal, you will not be able to view model pictures for saved views.

Observed in CAST AIP
Release
Yes/No
8.3.x (tick) 
Observed on RDBMS
RDBMS
Yes/No
CSS (tick)
Step by Step scenario
  1. Analyze code
  2. Start Enlighten
  3. Add objects to Enlighten's Graphical View
  4. Try to save the Graphical View
  5. Enlighten crashes
Action Plan
  1. Check the postgresql.conf file's bytea_output parameter and set it to correct value
    1. Check the value set for the parameter by using the page - RDBMS Information - PostgreSQL - How to get PostgreSQL settings, If the parameter value of bytea_output is set to escape.then this can affect the display of the view in Enlighten.

      1. To resolve the issue, do the following:
      2. Save a copy of your postgresql.conf file for your postgres instance.The postgresql.conf file can be found in your database data area for your postgres server. This location is defined during installation of postgres or CAST Storage Service. For a default Windows CSS implementation, this can be found in the CAST Storage Service area, which by default would be located in C:\Program Files\CAST\CASTStorageService2\db_data.
        Alternatively you can use the below query to identify the location of your postgresql.conf file

        SHOW config_file;
      3. Stop all CAST processes using your postgres instance
      4. Stop your postgres instance
      5. Modify the postgresql.conf file by setting bytea_output to the value 'escape' for the postgres server. 
      6. It needs to be uncommented in the postgresql.conf file for the server to take the value for the parameter into effect;  the comment character in the file is the '#'. 
        Therefore, change the value from: 

        #bytea_output = 'escape' 
        OR
        #bytea_output = 'hex' 
        OR
        bytea_output = 'hex' 
        To the below correct value:
        bytea_output = 'escape' 


      7. Save the changes to your postgresql.conf file
      8. Restart your postgres instance
      9. Bring up Enlighten and you should now be able to open up a saved view
  2. Check if the objects that were present in the previous run are also present in the current run. In such cases the view will not be able to show non-existing objects and might behave incorrectly.
  3. If the above steps do not solve your issue contact CAST Technical Support. with the following Relevant Input

Relevant input

  • Sherlock with option Export Databases (KB only)
  • postgresql.conf file
  • Detailed description of the problem
  • Screenshots of the problem
Notes/comments

 Ticket # 2719

Related Pages