i did remove bank services history and there hasn't been any real Difference.  I am now getting more feedback from the users.  It appears that they quite frequently get a UI error, they close it and just try again and everything works.  Today when running a day end we received errors indicating that there was a record lock with EFT and it couldn't continue and to try again later.  I went to current users to see who might be in EFT.  It turned out only 3 users were listed on the lanpak tab.  But we knew that there was more like 10 or 12 users in sage.  We isolated a single computer that was not listed on the lanpak users screen and that computer could move around open ar customers bring up customers – account activity etc.   I would click on open company check the userid, confirm it was the user I was tracking, attach again.  Still not in lanpak users.  I exited sage, exited my RDP connection to the server and re-established my remote connection and into sage and then that user was on the lanpak users list.  If I did open company and go out and attach to sage as a different user the user was removed from lanpak and listed as the new user everything was as expected.   Users continued to have ongoing record lock errors for approximately 2 or 3 hours.  We forced all users to go out completely back in so their names were all in the lanpak list.  While I was watching this list – right before my eyes. There was a blink of the screen, like the refresh when it looks for new users, and everyone was gone completely from the list and I was frozen.  I went to task manager forced a close, went back in and the only user in lanpak was me.  All users again had to go all the way out and back in they re-registered in the lanpak list and now have been working fairly successfully over the last 2 hours. 

Does anyone have any ideas what may be going on.  Is the list of lapak user not reliable and others have seen that this means nothing and I shouldn’t focus my attention on this.  Or is this an indicator that Sage has lost track of a user that could be locking files and is causing all these strange conflicts and record locks.

Does anyone know why users show up on the “other” tab.  This customer has many users on the Other tab and I have never seen that before.  I have only ever seen users listed on the lanpak tab.

I haven't seen the lanpak list do that before. It really sounds like some sort of network disconnect.  I don't think I saw it above - what version of Sage are you running?  Are the applications on the same server as the RDP server?  Is the configuration of the Path environment variable the same as how the registry is pointing to the Sage programs? (both UNC or both drive letter or ...).

Is any of this within a virtualized environment?

Is anti-virus running on this server?

Is the server used for anything else?

Do you have non-Sage applications accessing the Sage data (third party applications, for example)?

The LanPak.bin file in the shared data\SITE folder is where the list of users will be.  Semaphor.bin, also in SITE, governs locking of resources.  If you have something that is trying to update or gain control of these files, halt that process.  There's no point to backing up semaphor.bin - if it doesn't exist then the first user into Sage will cause it to be re-created.  I think it is the same for lanpak.bin, but I'm not certain.  But if there is an issue with different workstations not interacting with the files in the SITE folder properly then that will cause locking and concurrency issues.

sage 2016 SP3,  Apps are on same server as RDP, env path and reg are the same both drive letter, yes virtualized enviroment, no anti virus (have shut down still issues), Server does also provide MS office apps, no non-sage apps, 

you did put me on to something though with your explanation of the lanpak and semaphor file.  I was not aware of it as it was a bit disgused through the share but it turns out that the shared files (licenses site company and user) were on a different server from program files.  both local servers to each other so shouldn't matter.  But I made that change last night to place them on the same server, i did leave lanpak and semiaphore file behind (new ones created)   this morning everyone is in sage and they are correctly listed on lanpak tab and NOT on the other.  So I am hopeful.

Is it anything to do with the Signon Manager?  I am having weird locking issues and periodically it references Signon Manager so I don't know if that is something to look at.

Is it anything to do with the Signon Manager?  I am having weird locking issues and periodically it references Signon Manager so I don't know if that is something to look at.