Posted on behalf of user:
User receives the following error messsage:-
FRM - 93652: runtime process has terminated abnormally
Amendment for completeness:
Product = TMA Manager
Forms = TMA1030 Query Works linking to TMA1000 Works
Hi,
So that we can try to replicate the issue, please provide a step by step list of what the user does from logging in to the application, to receiving the error message.
Please also advise if this error is only seen by one user, several or all user who try the same thing.
Lee Jackson | Product Manager
Steps taken
Query Works - Query on Street find correct notice, Links, Works - then get Runtime Error
I’ve tried to replicate this problem as the Atlas user, using High Street for the query and then using works ********************** to link with, but the works form opened and displayed the record without an error.
Please could you advise which street you searched for in the Query Works form and an example works reference that replicates the error message for you?
Please also advise if this error is only seen by yourself, several users, or all users who try the same thing for the same record?
Information received, investigating..............
this error appears to be only affecting one user.
As you cannot replicate the same problem from a different machine and other users dont experience this problem, I suspect this will be an issue with your version of Java (1.6.0_23).
Please could you ask your IT department to install Java Runtime Environment version 6 update 33 (1.6.0_33), which can be downloaded via the following page.
Please do not install Java version 7 as this will probably cause you more problems. For reference, you will be able to upgrade to the latest version of JRE when your system is upgraded to Exor version 4700 in the near future.
www.oracle.com/.../java-archive-downloads-javase6-419409.html
Response from user:
I’ll speak to our IT but I’m still puzzled. Every other exor user in the company is on the same JAVA version as me but they’re not having any problems.
That’s understandable but from experience Java is likely to be the cause, particularly as you didn’t see the error when you tried this on a different machine.
Previously I’ve seen 2 identical machines behave slightly differently and updating Java did fix the issues.
If the updated version doesn’t fix the problem initially, there are some options within Java that we can fine tune for you, but updating to a later version is the first step.