Cannot read properties of undefined (reading 'ENG')

[adale]

Working in VL Web (v15), I have a VL web page, view, and dialog, that had worked fine, and not touched for a while.
Now when running the application, when the dialog is attempted to open, I get an fatal error:
Cannot read properties of undefined (reading 'ENG')

This is not from any parm that I can tell from the dialog, but something in the underlying lansa code?

I do not find any more details to the error in the Master or Web runtime error logs?

Can someone point me to where more details would or should be listed for this type of fatal error?

Notes:
I have checked out and reviewed all the cross referenced objects for the dialog, and all show multilingual detail as 'English'. I recompiled, and checked in without any errors? Not sure why or where the run time fatal error is coming from?

[kno_dk]

Hi

I get the same.

My application have a session (COM_OWNER.StartSession Timeout(28800)) but I don't think it is timed out. No other errors.

I have reported it to LANSA Support but it did not solve my problem.

In my error it says: lansa_15_0_7_0/lansa_prim.js71 - do you get the same js and line number?

/klaus

[adale]

Klaus,
Not this time. This time, the fatal error screen listed the line numbers for the sequence of click(s) in the vl source, first the click icon (line 556), then the MTHROUTINE line (1157) that is calling the dialog, then nothing further.
In the past, I have had times where the fatal error screen will list the .js line numbers, in which case I have to dig a bit deeper into looking at the compiled objects and find the corresponding line number there.

Usually when these fatal errors occur, there is a log in the master runtime error log which points me to the root of the issue. But this time, nothing in any of the logs I can find???

I too have reported this to support without any answer.
I copied the dialog to a new one, same error.
I created a new blank dialog, and copied in the source, same error.
So I just ended up creating a brand new dialog, and built it from scratch again, and this new one works.
So it was certainly something in the old dialog source, but something the compile does not catch as an error, so further "under the covers"?