Does AX have a limit somewhere for the number of concurrent users, or perhaps
if the user uses the 'x' to close down AX it leaves an active session hanging
(you'd see this in the online users) and there are many of these.
Alternatively, does the machine that is running the AOS have enough
processor/memory etc?
Alternatively, could there be any issues ogged against the sql database at the
back end that could provide some clues?
Just my two penny worth, hope it helps
----- Original Message ----
From: sudhavalett <[EMAIL PROTECTED]>
To: Axapta-Knowledge-Village@yahoogroups.com
Sent: Thursday, 29 May, 2008 2:48:34 PM
Subject: [Axapta-Knowledge-Village] AX client crashes!
Hi all,
Did any one of you come across this situation?
Sometimes the AX client closes with the following message.
"The server needs to free resources. Your session has been
terminated" and then it bumps off from the client and does not let us
reconnecting to it even though the server is up and running. It will
be normal only after restarting the AOS. It does not leave any
messages in the event log. These days it is happening very
frequently. Please let me know if any one of you have the solution.
Thanks,
Sudha
__________________________________________________________
Sent from Yahoo! Mail.
A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html
