42P01

[clenox]

I had a problem doing a parametric run where my computer did a manual update and shut down in the middle of the runs.  When I was able to get back in, I saw that about 30 of my runs had completed.  I went to the results module and no results were there.  I go the message "42P01: relation "files_master" does not exist."  It wiped out all of my previously imported runs.  I ended up deleting my VEDA 2.0 version 1.231.1.1 and re-installing it.  I synced the model and then went to the results module.  I imported a previously completed run that was not part of the parametric series and it loaded fine.  Then I tried to import the parametric files that completed and again got the error message above.  It again wiped out the run that I had just imported.  when I tried again to re-import the run that had worked and was not part of the parametric series of runs, I got this message: "22004 null values cannot be formatted as an SSQL identifier."  Can you please help me to resolve this issue?  It is not allowing me to attach the log file.

[Ravinder]

Dear Clenox,

Please rename the log file to ".txt" file and attached into your post with the screenshot of the issue.

[clenox]

Unfortunately I had to move forward with deleting the model and re-installing it, and I didn't think to save the log file. Since you have had this problem before, can you give me any insight as to how to deal with it if it continues to occur?

[Ravinder]

Dear Clenox,

We already requested another user to share the log file, but he has not yet responded!

According to your scenario, your model is interrupted in the middle of run and the machine shuts down.

In this case you may try to start from scratch approach to re-sync your model and then solve it!

[Ravinder]

Unfortunately I had to move forward with deleting the model and re-installing it, and I didn't think to save the log file.  Since you have had this problem before, can you give me any insight as to how to deal with it if it continues to occur?

Dear Clenox,

Note:-
If you ever encounter this issue, please post the log file first, so that we can find out the real cause of the problem.

Problem:-
If you did not get any results due to any reason after solving the model.
   

Workaround:-
Follow the below steps-
1. Go to Tools menu and select Import VD files option. Browse your GAMS_WrkTIMES folder where your recently solved VD files exist and click to import.
   

2. Go to Tools menu under the Results tab and click Refresh Data
   

[mb537]

I had the same error when I had to force quit a number of runs when they stalled. I've attached the log file below with the error.

[Ravinder]

Kindly share the latest log file.

[mb537]

Kindly share the latest log file.

The log file is attached in the previous post. The forum did not allow uploading of a .log file so I saved it as a .txt file. If you're not able to see the file I can try to upload it another way.

[Ravinder]

Dear Morgan,

You have shared an old log file dated 24 April 2021(2021-04-27.txt).

When did you face the issue, we need a log file of that day.

Please rename the .log file to .txt and upload it.

[Antti-L]

Sorry to intervene Ravinder, but at least I am feeling confused now:

> When did you face the issue, we need a log file of that day.

I can clearly see the error 42P01 being logged towards the end of that log file, and so Morgan did indeed face the issue on that day (2021-04-27 17:01:21), and the log file is of that day, correct?  So, wondering why that is not good enough?

Code:

 Exception data:
   Severity: ERROR
   SqlState: 42P01
   MessageText: relation "scenario_master" does not exist
   InternalPosition: 239
   InternalQuery: SELECT
        t1."name" AS cases_in_back_end,
        t2.case_name AS new_case,
        COALESCE(t1.study, t2.study_name) AS study_name,
        COALESCE(t1.model, t2.model_name) AS model_name,
        COALESCE(t1.user_name, t2.user_name) AS user_name
    FROM
        scenario_master t1 FULL
    JOIN(
[...]

[Ravinder]

Dear Antti,

Morgan posted his issue on 21 May 2021, so I just wanted to see his current log file. Although he had also faced the same issue on 27 April 2021.

Also, I wanted to check if he had faced this issue once or multiple times with same reasons or multiple reasons.