Mike Frank
2009-04-28 13:30:03 UTC
Hi Amar Nalla,
glad to hear, that someone is taking care of this problem. Sorry, that
it took me a while to answer.
As to your questions:
1. We are using the new impersonated Batch framework, and BC.Net called
through a WebService but no EP.
2. There was no heavy login activity at the time of the crash (ca. 11:00
am). Most of our users logging in the morning. We have about 35 to 40
users (with the Windows client) online at a time.
3. No specific pattern was discernible yet. We had the AOS crashing
three times now (we upgraded to 2009 from 3.0 on 2008/12/27) and I'm
only the last time sure, that the crash was caused by a deadlock,
because I had this message in eventlog.
I could not run SQL profiler, because I had to have it running all the
time and this is our production environment.
Some remarks on system setup:
We run two AOS. All regular users log onto AOS1. AOS2 runs only batch
jobs (AOS1 is not activated as batch server).
The WebService and with it the BC runs on AOS2 but connects to AOS1.
Hope this is any help to you.
Mike
glad to hear, that someone is taking care of this problem. Sorry, that
it took me a while to answer.
As to your questions:
1. We are using the new impersonated Batch framework, and BC.Net called
through a WebService but no EP.
2. There was no heavy login activity at the time of the crash (ca. 11:00
am). Most of our users logging in the morning. We have about 35 to 40
users (with the Windows client) online at a time.
3. No specific pattern was discernible yet. We had the AOS crashing
three times now (we upgraded to 2009 from 3.0 on 2008/12/27) and I'm
only the last time sure, that the crash was caused by a deadlock,
because I had this message in eventlog.
I could not run SQL profiler, because I had to have it running all the
time and this is our production environment.
Some remarks on system setup:
We run two AOS. All regular users log onto AOS1. AOS2 runs only batch
jobs (AOS1 is not activated as batch server).
The WebService and with it the BC runs on AOS2 but connects to AOS1.
Hope this is any help to you.
Mike
Hi Steffen and Mike,
We made changes to avoid such crashes due to a deadlock, so I would like to
get more details on the cause of the crash.
Are you using BC.Net or EP or Batch? Are there lot of sessions logging in at
the same time? Is there a specific pattern that triggers the crash? Will you
be able to launch SQL Profier and trace the statements during the crash? I
can give more details on what to look for when this crash happens.
Thank you,
Amar Nalla [MSFT]
This posting is provided "AS IS" and confers no rights or warranties.
We made changes to avoid such crashes due to a deadlock, so I would like to
get more details on the cause of the crash.
Are you using BC.Net or EP or Batch? Are there lot of sessions logging in at
the same time? Is there a specific pattern that triggers the crash? Will you
be able to launch SQL Profier and trace the statements during the crash? I
can give more details on what to look for when this crash happens.
Thank you,
Amar Nalla [MSFT]
This posting is provided "AS IS" and confers no rights or warranties.
The problem lies definitely in the kernel. In my case the deadlock was in
SysClientSessions which is used for client session handling. But even if
the
deadlock was in a regular app table, this should never cause the AOS to
crash.
I thought also about reporting the problem to MS, but since my experience
with German AX Support is not so good (to be polite), I wanted to try the
newsgroup first. Since you have reported it, I can spare myself the
trouble.
Mike
SysClientSessions which is used for client session handling. But even if
the
deadlock was in a regular app table, this should never cause the AOS to
crash.
I thought also about reporting the problem to MS, but since my experience
with German AX Support is not so good (to be polite), I wanted to try the
newsgroup first. Since you have reported it, I can spare myself the
trouble.
Mike
I've dived into the issue each time my superiors hear about this problem,
and
each time I have to tell them that I can't really get to the heart of the
problem, as I supect that the problem lies in the kernel. I have already
requested support from MS but it is slow and cumbersome.
If you find a solution to the problem, pls let me know.
BTW. What is your setup? I have a appl. server, an aos on Server2008 and
a
sql 2005 on server 2008.
and
each time I have to tell them that I can't really get to the heart of the
problem, as I supect that the problem lies in the kernel. I have already
requested support from MS but it is slow and cumbersome.
If you find a solution to the problem, pls let me know.
BTW. What is your setup? I have a appl. server, an aos on Server2008 and
a
sql 2005 on server 2008.
Thank you, at least I know now, that I'm not alone :-(
AX 2009 is indeed very unstable (and slow). Client crashes are
frequent.
Though AOS crashes are worst for me, because that involves every user.
And, with this kind of stuff you are pretty much stuck. If there is a
bug in
the application (and there are lots of them) you can at least have a
look at
the code and possibly fix it.
AX 2009 is indeed very unstable (and slow). Client crashes are
frequent.
Though AOS crashes are worst for me, because that involves every user.
And, with this kind of stuff you are pretty much stuck. If there is a
bug in
the application (and there are lots of them) you can at least have a
look at
the code and possibly fix it.
I've had this crash for the first time today aswell - IMHO AX2009 is
too
unstable - I have users crashing and AOS deadlocks as this one at
least 5+ pr
month
too
unstable - I have users crashing and AOS deadlocks as this one at
least 5+ pr
month
Three consecutive messages in EventLog
Object Server 01: Dialog issued for client-less session 2: Cannot
select a
0, 0.
Deadlock, where one or more users have simultaneously locked the
whole table
or part of it.
Object Server 01: Unexpected situation
More Information: Session Allocation Failed: Session is already
allocated.
Faulting application ax32serv.exe, version 5.0.1000.52, stamp
490c41df,
faulting module kernel32.dll, version 5.2.3790.4062, stamp
462646d5, debug?
0, fault address 0x0000bee7.
This was in our production environment.
Anyone seen this? AX 2009 is very unstable. We had never any AOS
crashes in
3.0.
And, why should a deadlock cause the server to crash?
As for the client-less session. Batch processing is not enabled for
this
server, but only for the second AOS, which has no regular user
sessions.
This second server was shutdown about 10 to 20 minutes before the
crash, but
that should never cause the first AOS to crash!
Mike
Object Server 01: Dialog issued for client-less session 2: Cannot
select a
0, 0.
Deadlock, where one or more users have simultaneously locked the
whole table
or part of it.
Object Server 01: Unexpected situation
More Information: Session Allocation Failed: Session is already
allocated.
Faulting application ax32serv.exe, version 5.0.1000.52, stamp
490c41df,
faulting module kernel32.dll, version 5.2.3790.4062, stamp
462646d5, debug?
0, fault address 0x0000bee7.
This was in our production environment.
Anyone seen this? AX 2009 is very unstable. We had never any AOS
crashes in
3.0.
And, why should a deadlock cause the server to crash?
As for the client-less session. Batch processing is not enabled for
this
server, but only for the second AOS, which has no regular user
sessions.
This second server was shutdown about 10 to 20 minutes before the
crash, but
that should never cause the first AOS to crash!
Mike