AOS Sessions being aborted
nep
Windows Server 2008 64Bit and the clients are primarily running from a
terminal server installed with Windows Server 2003 R2. Some clients are
running from Windows XP installed locally on their workstations.
The client went live with the system in the spring of 2009 and have been
running fine with Dynamics AX 2009. However the last 14 days we more and more
often experience clients that breaks down, apparently for no reason.
The AOS event log shows this pattern:
Object Server 01: RPC error: Client provided an invalid session ID yyy
Object Server 01: RPC error: Client provided an invalid session ID xxx
Object Server 01: No ping from yyy. Terminating the session.
Object Server 01: No ping from xxx. Terminating the session.
We have tried to trace this error - investigating whether or not this may be
caused by "bad code" etc. We have not been able to identify such issues and
we do not really know what to look for.
We have seen this error even when running a client on the AOS server itself,
which should rule out the error being caused by network failures(?)
The hosting vendor has measured the network and can't find any technical
problems.
The only thing that we suspect right now is that one or more Windows
Update's have introduced some new scenarios?
--
Regards
nep
SCGAN
nep
Our client found a problem with the time of the AOS server. It was
out-of-sync with the AD server by 4 minutes. After setting the time again,
they have had a normal production day without any problems!
The above article mentiones an interval of 210 sec. - don't know if this has
any meaning.
I have asked Microsoft to confirm the above and will post their reply.
--
Regards
nep
SCGAN
Good to hear that. Please update us the MS reply. ^^
so AOS sessions error no longer exists after time synch between AD and AOS
Server?
Thanks & Regards,
S.C.GAN
georgievg
Do you have a responce form microsoft?
I am experiencing the same issue here.
I have an AOS Ax4.0 running on a 64-bit windows 2008.
Getting the same errors:
Object Server 02: RPC error: Client provided an invalid session ID xx
Object Server 02: No ping from xx. Terminating the session.
Have checker the time sync and all the client PCs and servers are syncing with PDC (pdc is syncing with time.windows.com)
Have anyone resolved that issue?
Thanks
SCGAN wrote:
Hi Nep,Good to hear that. Please update us the MS reply.
27-Sep-09
Hi Nep,
Good to hear that. Please update us the MS reply. ^^
so AOS sessions error no longer exists after time synch between AD and AOS
Server?
Thanks & Regards,
S.C.GAN
"nep" wrote:
Previous Posts In This Thread:
On Thursday, September 24, 2009 8:17 AM
nep wrote:
AOS Sessions being aborted
At a client we are running DAX 2009 SP1 on SQL2008. The AOS is installed on a
Windows Server 2008 64Bit and the clients are primarily running from a
terminal server installed with Windows Server 2003 R2. Some clients are
running from Windows XP installed locally on their workstations.
The client went live with the system in the spring of 2009 and have been
running fine with Dynamics AX 2009. However the last 14 days we more and more
often experience clients that breaks down, apparently for no reason.
The AOS event log shows this pattern:
Object Server 01: RPC error: Client provided an invalid session ID yyy
Object Server 01: RPC error: Client provided an invalid session ID xxx
Object Server 01: No ping from yyy. Terminating the session.
Object Server 01: No ping from xxx. Terminating the session.
We have tried to trace this error - investigating whether or not this may be
caused by "bad code" etc. We have not been able to identify such issues and
we do not really know what to look for.
We have seen this error even when running a client on the AOS server itself,
which should rule out the error being caused by network failures(?)
The hosting vendor has measured the network and cannot find any technical
problems.
The only thing that we suspect right now is that one or more Windows
Update's have introduced some new scenarios?
--
Regards
nep
On Friday, September 25, 2009 2:27 AM
SCGAN wrote:
RE: AOS Sessions being aborted
http://blogs.msdn.com/emeadaxsupport/archive/2009/04/24/how-does-the-session-validation-work-in-dynamics-ax-4-0.aspx
Regards,
S.C.GAN
"nep" wrote:
On Friday, September 25, 2009 10:36 AM
nep wrote:
Problem solved!
Problem solved!
Our client found a problem with the time of the AOS server. It was
out-of-sync with the AD server by 4 minutes. After setting the time again,
they have had a normal production day without any problems!
The above article mentiones an interval of 210 sec. - do not know if this has
any meaning.
I have asked Microsoft to confirm the above and will post their reply.
--
Regards
nep
"SCGAN" wrote:
On Sunday, September 27, 2009 10:52 PM
SCGAN wrote:
Hi Nep,Good to hear that. Please update us the MS reply.
Hi Nep,
Good to hear that. Please update us the MS reply. ^^
so AOS sessions error no longer exists after time synch between AD and AOS
Server?
Thanks & Regards,
S.C.GAN
"nep" wrote:
Submitted via EggHeadCafe - Software Developer Portal of Choice
Book Review: ASP.NET 2.0 Web Programming with VB 2005 [Murach]
http://www.eggheadcafe.com/tutorials/aspnet/5ce13132-519c-486e-908d-b006d6c94b35/book-review-aspnet-20.aspx
Amar Nalla [MSFT]
This error basically happens when the server does not request a ping request
from the client within a specified time interval. In Ax 4.0 and Ax 2009 the
client sends a ping request to the server periodically. You can see the
details of these error messages in this blog post:
http://blogs.msdn.com/daxis/archive/2009/03/19/troubleshooting-orphaned-sessions-and-spids-in-dynamics-ax.aspx
There is no specific cause for this error other than the fact that the
client did not send the pings. Do you see any crashes or client hangs when
these error happens? That might help in narrowind down the root cause of the
issue.
Thank you,
Amar Nalla [MS]
PS: This posting is provided "AS IS", and confers no rights or warranties.
<Georgiev G> wrote in message news:20101269743d...@natdist.com...