Unfortunately I can't seem to recall what the ultimate resolution was. This however appears to be the last communication we had with the client so it's possible this helped in resolving it:
As discussed, here's the next things we'd like you to perform for troubleshooting the "user switching boot-out issue".
During our conference call this afternoon you mentioned another User got booted out of MAS 200 upon switching to a different company code. Therefore it doesn't quite sound like Karen's User ID (016) is bad/corrupt. However it couldn't hurt to remove 016 and create a new one for Karen.
Then the next time Karen or another User is booted out, please take a look and see if anything was recorded in the MAS 200 System Activity Log (Library Master > Reports). And we'd be very interested to know if you can replicate it. For example, if Karen switches to User 035, and then tries to access Customer Maintenance and gets booted out, what happens it she repeats those exact steps? I think this would help to isolate it.
Ideally we need to figure out what's different when the User gets booted out vs. not getting booted out - because that too should help in uncovering the cause. Therefore we'd like for you to determine for sure if the User only gets booted out when switching to a User ID who's already in MAS 200. Or does it in fact also happen when the User ID isn't already in? And for User ID's already in, are they accessing MAS 200 via Terminal Server?
Actually it now looks like the logging out of the network thing was related to a different issue. Sorry.
Pretty sure it was related to not logging out of the network overnight. A KB entry mentioned the need to log out due to some Windows configuration issues. Symptom was that suddenly the user appeared to drop connection to the network with some type of "cannot find xxxx.M4t" where the M4t was some type of user or console file.