I hope this clarifies the answer

Lovemyi

I don’t believe either of the answers you’ve gotten are off-base at all. If you’d like to reply with some specific details to at least respond to the issues raised, then perhaps we could help you further.

To throw in my $0.02: I often see this error when users are in a program and close Client Access via the X in the top-right corner instead of signing out properly. When they attempt to reconnect, the system tries to join them back to the program, which by then may be dead already…hence, the crash.

Are you signing out (back to the sign on screen) as advised by your administrator when you close the Client Access program?

Generally, I tend to disconnect and reconnect rather than typre my profile/password into the Signon screen when I want to log back on. I have my sessions configured to “Bypass signon” in order to avoid the typing.

While trying to log back on, the system send this message “JOB ENDED ABNORNALLY”.

We will need to see the joblog for that job to know the reason given by the system.

I can log into many sessions, but only one profile.

I’m not clear on what that means. It seems to mean that you can start multiple sessions but can only logon using a single profile from that PC at during a given time. If you want to log off of one of those sessions in order to log on with a different profile, you see the “JOB ENDED ABNORNALLY” screen.

Is that close? If not, can you clarify?

Tom