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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

The server has terminated the session, the client will now close

(0) ShareShare
ReportReport
Posted on by

Has anyone seen this issue?  Our users have been experiencing the following - they would be logged into the terminal server and after roughly 10 - 15 minutes the our AOS01 would kill their session and they get the error message that reads "The server has terminated the session, the client will now close."


Our VAR has completed a kernel update but that has not fixed it.  Recently I posted a question regarding corrupted AUC files and a user recently pointed me to this post:

http://blogs.msdn.com/b/emeadaxsupport/archive/2010/01/25/identical-ax-2009-auc-file-created-for-multiple-ax-installations.aspx

Could the fact that our users have been clearing their cache (deleting the cache and auc files) have anything to do with the server killing client sessions?


Running AX2012 R2; two AOSs; load balance on our two terminal servers - it seems that anyone connected to AOS01 is having the issue.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Umesh Pandit Profile Picture
    9,315 User Group Leader on at

    Hi Rumberger

    Check these useful post:

    community.dynamics.com/.../107339.aspx

    blogs.msdn.com/.../739382.aspx

    dynamicsuser.net/.../124330.aspx

  • Verified answer
    Community Member Profile Picture
    on at

    We touched base with our VAR as well as MS, the following is the issue and solution:

    A few weeks prior to this issue our SAN's controller bombed out and we needed to get some virtual machines off of that SAN and move them over to the virtual host which is hosting our AX cluster.  One of those VMs just so happen to be a domain controller.  

    After about a week or two of SQL (which is a VM) getting it's time from a VM on the same host the time was roughly 4 minutes off.

    Users logging into the client via the terminal server would submit a request and sql would think it's timeout has exceeded and the AOS would terminate the server session.

    The solution was to have the DC get it's time from a physical server due to the way the VMS handle time.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans