Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Dynamics AX 2009 SP1 AOS Service

529 views
Skip to first unread message

Amer

unread,
May 30, 2010, 9:27:01 AM5/30/10
to
I have a problem related to the service of the AOS, it keeps stoping from
time to time, i checked the event viewer it shows the following errors:
1- The Microsoft Dynamics AX Application Object Server is running on an
operating system that is not supported. The supported operating system is
Microsoft Windows Server 2003 with Service Pack 1.
2- Object Server 02: The database reported (session 1 (-AOS-)):
[Microsoft][SQL Native Client]Communication link failure. The SQL statement
was: "SELECT
A.ENABLEBATCH,A.SERVERID,A.MAXSESSIONS,A.TIMEALIVE,A.LOADBALANCINGENABLED,A.CLUSTERREFRECID,A.SERVERGUID,A.RECVERSION,A.RECID
FROM SYSSERVERCONFIG A WHERE (SERVERID=?)"
3- Object Server 02: Dialog issued for client-less session 1: Cannot select
a record in @SYS103513 (SysServerConfig). @SYS115443: , @sys2048.
Error accessing database connection.
I am running dynamics ax 2009 on two servers (application and database),
Application server:
- Windows server 2008.
- Dynamics AX 2009 with SP1 AOS
Database server:
- Windows server 2008
- sql server 2008
Please help !!

Jonas

unread,
May 30, 2010, 10:42:00 AM5/30/10
to
The first error can be ignored. It is not an error. If you install the
latest kernel it will go away

/Jonas

"Amer" <Am...@discussions.microsoft.com> skrev i meddelandet
news:D3B3CEC1-9CD4-4113...@microsoft.com...

Amer

unread,
Jun 6, 2010, 3:09:22 AM6/6/10
to
Hi Jonas,
If i installed the last kernal, well it solve the restart issue ??

Jonas

unread,
Jun 7, 2010, 8:46:15 AM6/7/10
to
Well, I do not know. We made some other changes too.

For example, we got a few errors on insufficient memory. We discovered just
the other day that this error comes hand in hand with memory leaks on the
server.
So when Ax throws this error on client or server side, the memory never gets
allocated and the memory gets corrupt (not a previously known bug).

We made the changes in the article below at about the same time as we
installed all updates, so we really do not know what gave us the positive
effect.
http://blogs.msdn.com/b/emeadaxsupport/archive/2009/06/15/error-executing-code-insufficient-memory-to-run-script.aspx

/Jonas


"Amer" <Am...@discussions.microsoft.com> skrev i meddelandet

news:F676E831-76D0-4F73...@microsoft.com...

0 new messages