web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Stranded users in GP
Microsoft Dynamics GP (Archived)

Stranded users in GP

(1) ShareShare
ReportReport
Posted on by Community Member

I've come across this issue in a couple of different environments and I'm still scratching my head.


Users close GP, but their login is not cleared out of the DYNAMICS..ACTIVITY table. I've seen it happen in an environment with users accessing GP via terminal services and RemoteApp and I've also seen it happen in an environment with client installs. I've physically stood there and watched the users log out, and they're definitely logging out correctly. I mostly see it in GP 2015 R2. Anyone ever experience something similar to this?


Seems like there's lots of blog posts and info on how to remove stranded logins, I'm interested in finding out how to prevent them from happening in the first place. I've seen SQL scripts out there that clean up GP logins that I know I could turn into an stored proc and run periodically, but I'd rather not be constantly running SQL update statements against the system db if I don't have to.

*This post is locked for comments

I have the same question (0)
  • RogerRogerATX Profile Picture
    RogerRogerATX 1,515 on at

    We're not on GP2015 so I don't know for certain BUT considering that I myself have found weird dexterity bugs in GP I'm curious too (we have the same problem but it's a remote desktop related more than likely)...

    Are they exiting GP by closing the app or by selecting Microsoft Dynamics GP-->Exit ?

  • Community Member Profile Picture
    Community Member on at

    I've seen them do it both ways. Initially I thought that they were closing GP and then quickly logging out of the TS, or they were closing the remote app GP and it was killing the SQL connection before GP could finish closing itself properly, but now I'm not so sure.

  • Verified answer
    Beat Bucher GP Geek GPUG All Star Profile Picture
    Beat Bucher GP Gee... 28,061 Moderator on at

    Hi Michael,

    Do you use the GP Web Client ? or is this happening in the full client ?

    I've been using GP for over 13 years now from V 7.x to 2015R2 and never really seen a case where the Activity table didn't cleared after the user logs out properly (except when he/she kills the apps from the task manager).

    Cases where the use is stranded in ACTIVITY is when accessing GP thru RDP / Citrix and the user 'disconnects' the session rather then doing a logoff. In some circumstances the TS / RDP server will kill the apps after a threshold of inactivity on the server side.. The entry though will remain in ACTIVITY. That's why I'm running a daily job every night to clear out the table.. But this only happens once in a while and I know of specific users to which it happens, because they tend to close their laptop and run away without closing their GP session first... :-)

    Are you able to narrow the issue within a range of users ? or any pattern that would be common within those users ?

  • Community Member Profile Picture
    Community Member on at

    There's really no pattern to it. Sometimes it happens, other times it doesn't. I'm beginning to think that the stranded logins are from times where they freeze GP or, as you say above, their connection to the TS is simply closed. I'll keep monitoring and update this thread with any new info.

    Part of the issue may be related to the other question I posted on the forum that you answered :). (for those reading: community.dynamics.com/.../532489)

  • Community Member Profile Picture
    Community Member on at

    Did you ever make any progress on this issue? We are running into a similar situation. Our Web Users seem to be the only ones stranded at this time

  • Suggested answer
    Beat Bucher GP Geek GPUG All Star Profile Picture
    Beat Bucher GP Gee... 28,061 Moderator on at

    Hi Matthew,

    The GP Web Client user is a particular one and cannot be compared to the full client..

    Mostly the problem relies on the Windows Authentication that once the GP user is authenticated, doesn't require you the re-enter your credentials for the next 30 days or so... Most of the time, users will just close their web browser instead of properly 'exiting' the session in GP :

    2017_2D00_01_2D00_04_5F00_081825.png

    You can check with the Web Client session manager who's sesion is still logged into GP (and their status), at which point you can kill the stranded sessions.

    2017_2D00_01_2D00_04_5F00_083927.png

  • Community Member Profile Picture
    Community Member on at

    I'm extremely curious to see if you ever made progress on this one.  I have a situation where the users will click 'x' to close the program from the top right and it will leave their logins stranded.  The organization I just started working with has actually trained each of the users to fully log out of GP through the file menu, but I've never seen this behavior before.  This is a 2013 GP setup.  

  • Beat Bucher GP Geek GPUG All Star Profile Picture
    Beat Bucher GP Gee... 28,061 Moderator on at

    Hi Matthew,

    Are you talking about the full client or the web client ?

    From where does the GP client run ? is it installed locally or published on a remote apps server (Citrix or RDS) ?

    I've been running on 2013R2 since almost 2 years now and 95% of our users access GP thru RDS, and very rarely do I have stranded users.. Occasionally I get calls from users that ask me to "kill" their RDP session, as they can't seem to log back into GP because there is already a session running and somehow it prevents them to restart another one

  • Community Member Profile Picture
    Community Member on at

    I just learned (one year later) how to reply and see responses. Anyway, This was for an install where they are dialing in to terminal servers and accessing the install directly from that local install on that specific terminal server. Yes there was some RDS, but I was having the same issue accessing directly. Very odd. I don't know that they ever got it resolved, but I know that this is not a normal piece. This was a full client install on a remote terminal server. My reply here is useless for helping someone, but perhaps if they see a pattern we can identify why this was happening.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Shravan Attelli Profile Picture

Shravan Attelli 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans