[SOLVED] Lansa login error (function LH@PURG)

[Stefano Foresi]

Hello,
I'm currentl experiencing this error, looks like a Lansa internal functions (LH@PURG) encouters some bad formatted data and trows that error (00000020 as Date).
I don't know how this happened, Lansa trows me that error at every environement opening.
Any ideas how to fix it? Does that functions clears some folder or maybe table where are store log files? (Maybe some LX_DTA.LX_something...)

2024-04-11 10 38 45.png (11.78 KiB) Viewed 27042 times

Thanks in advance,
Stefano

[René Houba]

Hi Stefano,

What is your LANSA version? And what EPC?

Kind regards,
René

[Gilamonster]

Hi Stefano,
We encountered a similar issue with LH@PURG, a long time ago, with version 11.3 after a check-in which ended in error.
Please find below the answer received by LANSA Support at that time.

This is occurring because there appears to be some corrupt data in your LX_FLG internal table. Typically, a Date with wrong format (ie : 20051412 in YYYYMMDD format).The safest way to fix this error is to clear the entire LX_FLG table, however you would end up losing all of your Host Monitor history. Alternatively you could open the table in a Database editor and look for the record where XLGDAT is '00000020', and delete that record only.

I hope this will help
Kind Regards
Christophe

[Stefano Foresi]

Thanks for your reply,

I've cheched LX_FLG but there are no entries having XLGDAT = 00000002.

In the meantime, to fix the issue my admin tried to uninstall my client setup of Lansa, to reinstall it again,
maybe the uninstall process cleared the LX_FLG having XLGWID = my pc hostname.

He wasn't able to install it again due to setup process not being able to recognize our Lansa server installation, but that's another story...

Thanks.
Stefano

[Stefano Foresi]

Hi Christophe,
I'm now running a new server installation of Lansa,
and while checking-in some programs to our AS400 I've encountered some error, resulting in the same error message in LG@PURG function.

As you suggested, I've searched and found that LX_DTA.LX_FLG contains records having XLGDAT = 20,
once deleted those record the error is gone!

So thank you very much for your help!!!

Best regards,
Stefano