Landmark - Rich Client access/icons disappear

Okay, I'm reaching out to this community as I've had a support ticket open since June... we just went live in May.

We have LTM on Landmark and our HR users access it via Rich Client (installed, not applet)

We have sporadic issue that has occurred for multiple users on multiple pcs and both in LTMTEST and PROD environments and in different buildings that are miles away from each other, so it can't be a network connection. And it can occur with one person and no one else has the issue at that same time.

-They are signed in and working fine and then go to perform an action/task and nothing works. Then when they go back to their 'canvas', all of their icons are gone

-Upon login, they have no icons

Their access is flat out disappearing and will not re-initiate in that session.

Close that session of Rich Client and open a new one and all is well.

This has occurred on landmark versions .37, 39 and 51 is our latest as of Tuesday night and it just occurred again.

Support had us update java on the server from 1.7.0.45 to .80 and it has again occurred in both test and prod.

We can't reproduce this.

Has anyone else had this issue or have any ideas?

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

cockrell

Hi Annette,

Yes, we have experienced the same problem. We are on application version 10.2 and landmark version .38. Our HR staff are our main users of the Rich Client application to access Landmark. Our users would randomly lose all of their icons but their security roles would still be in tact when reviewing the actor setup. As you stated, waiting for a bit, logging out and then logging back in the system restores the icons. Sometimes it took longer to get them back but there really wasn't anything that occurred except letting time go by before logging back in. It really didn't make any sense. We haven't experienced this in some time now (knock on wood). No one has ever been able to give us a reason or solution either. I would be very interested if someone has some insight into this issue.

unknown

Thank you. We are actually went live on 10.2.13 but have since updated to 10.2.17 and have experienced it in both versions and as mentioned, 3 different versions of Landmark.

We did go about a month with no one reporting it to me and finally just closed the ticket and then it occurred again this morning.

I will post back here if I find anything but at this point, we are just hanging in there.

Today they had me change a parameter in richclientadmin.lawspec file .. the Xmx line from 636 to 1024. I have no idea what it does and asked questions how that number gets put there to begin with but didn't receive replies to that.

It is definitely sporadic and not re-creatable which I know is difficult to triage but it is driving people crazy. .. .and I think it's occurring more but HR Staff don't want to take the time to call me so I can get support on a webex... they have work to do.

unknown

The Xms setting is the maximum memory that a Java process is allowed to use. Giving a Java process more room can allow it to work better, because it won't fill up its allocated memory so quickly. This can happen if there's a memory leak in a java process, or a failure to garbage-collect. Both are all-too-common problems with java applications.

Copyright © 2025 Infor. All rights reserved.