Hi Hans-Jürgen,
I agree to Carsten Schmitz: Wrong LNR probably means "wrong line number".
If you want to analyze the error by yourself and to provide more informations to the support you can try to debug the JWP which probably throws the error. Michael Kutswa has written a manual for this and published it on GitHub:
https://github.com/Automic-Community/How-to-remote-debug-a-JWP-with-Eclipse-Framework In your case, you can certainly get the object ID faster with an SQL statement directly from the DB, but maybe you can determine the incorrect line number...
@Michael Kutswa: Thank you for your very detailed manual! When we have migrated to version 12.3, I will certainly be able to use it.
Best regards,
Tim
------------------------------
Automation Evangelist
Fiducia & GAD IT AG
---
Mitglied des deutschsprachigen Automic-Anwendervereins FOKUS e.V.
Member of the German speaking Automic user association FOKUS e.V.
------------------------------
Original Message:
Sent: 01-13-2020 09:33 AM
From: Hans-Juergen Zintl
Subject: Version Management Object - Java Exception - Wrong LNR
If I open the two last versions of an automic object I get following Error. If I openn the third version of the object it works.
Stacktrace: