This page is intended to provide a consolidated list of published documentation, tools, as well as tips and tricks for the Application Object Server (AOS) in Microsoft Dynamics AX 2009.

The AOS is dependent on several hardware, software, and network resources for effective operation. Please be sure to include maintenance routines for these resources to ensure the stability of your AOS.

Important Note: Many of the links on this page go to CustomerSource. Learn more about CustomerSource and how to sign in

On this page:


 

Top Downloads

Top

 

Critical Hotfixes

The Dynamics AX kernel hotfixes are cumulative fixes that address issues in the executable and dll files for Dynamics AX. These hotfixes do not modify any X++ code, therefore they do not require full X++ code review when deploying to your environment. The kernel fixes are designed to address stability, performance, and compatibility with other software applications. When you apply a kernel hotfix you do want to do testing and the key areas to focus on are printing, pdf functionality, and integration points. When you apply a kernel hotfix you want to be sure that it is applied on all machines that have a Dynamics AX component, such as the client, AOS, or .Net business connector. If you do run into any issues with the Kernel hotfix you can safely remove the hotfix from the Programs and Features area of the Control Panel.

It is recommended that you consider regular installation of Kernel rollups in your Microsoft Dynamics AX environments. We find that many times when a customer is experiencing issues with the AOS that installing the latest Kernel hotfix resolves the issue. Therefore to assist our customers and partners with applying the Kernel hotfixes we have started to release the Kernel portion of the Rollup hotfixes for Dynamics AX 2009 as a separate download. This download will have "_BinaryOnly" in the file name. The one without "_BinaryOnly" contains both the Application and Kernel. This way customers can install just the Kernel portion of the Rollup hotfixes that we provide. Due to Rollup hotfixes receiving, more testing than a regular hotfix we recommend that you apply the latest kernel Rollup hotfix unless your issue has been resolved in a kernel hotfix since then. Here are the links to the latest kernel hotfix - To find the latest kernel Rollup see the Hotfix Rollups released for Microsoft Dynamics AX 2009 section of Hot Fixes Released for Microsoft Dynamics AX 2009


To determine which Kernel rollup is currently applied to your AOS you can go to
C:\Program Files\Microsoft Dynamics AX\{Version Number}\Server\{Instance Name}\Bin and find the ax32Serv.exe file.
Right click on this file and select properties. Go to the details tab (version tab on Windows 2003 Server) and find the number for Product version. You can then use the website listed below to determine the service pack and rollup that you are running.

Overview of Dynamics AX build numbers

** Note: The path could include Program Files(x86) if your AOS is on a 64 bit machine and you have Dynamics AX 4.0

Top

 

Featured Videos

 

Top

 

Related Resources

Top

 

Tools

How to gather a crash dump/what information to provide to support

Top

 

Common Problems & Solutions

  • We have found that in a number of AOS crash cases they are resolved by installing the latest kernel hotfix. Therefore it is recommended that you consider implementing the latest kernel rollup as part of your maintenance. This could mean applying the latest kernel rollup once a quarter. Since the kernel hotfixes are cumulative, easy to uninstall, and do not include X++ fixes they are typically able to be installed with a lot less effort than an application hotfix. We do recommend that you apply the kernel rollup in a non-production environment and do some testing before applying it in your production environment. Please see the information from the AX Kernel Patching section on how to update to the latest kernel hotfix rollup.
  • If you implement code when users are in the system you could have cache or data access issues that result in an AOS crash. Therefore, when implementing code in your production environment it is recommended that you do so when users are not in the system. If you are going to import an xpo make sure that you shut down all but one AOS during the process. You may also want to consider then shutting down that last AOS, deleting the axapd.aoi file, and restarting one AOS so that the axapd.aoi file gets rebuilt.
  • Verify that all of your Microsoft Dynamics AX components are on the same build. We have found that if there are rpc call changes in a kernel build and a machine is inadvertently missed during the Kernel hotfix install that it can result in AOS crashes.
  • If possible separate each AOS by process/component. So for example if you use Dynamics AX clients, Enterprise Portal, and you heavily utilize batch processing you could have each of these connect to its own AOS.

Top

 

Troubleshooting Tips

  • KB 953375 - How to find a user ID that is associated with a session ID of a "RPC error: RPC exception 1726 occurred in session [SessionID]" error message in the Application log on the AOS server in Microsoft Dynamics AX
  • KB 953374 - You receive a warning message in the Application log on the AOS server in Microsoft Dynamics AX: "SPID [SPID_number] for Session Id [SessionID], is still present in the database. Please delete the SPID from the database"
  • KB 950802 - Error message in the Application log on a computer that is running Microsoft Dynamics AX Application Object Server: "RPC error: Client provided an invalid session ID [X]"
  • Setting to change after restoring the database.

Here are some events from the AOS machines application event that can be useful when managing an AOS:

Event Log Entries

How to Troubleshoot

Event ID 149. Object Server 01: Ready for operation

Use this to verify the AOS build/version information from the kernel build section.

Event ID 172.

Use this to verify the .Net Business Connector build. This is helpful if you think the issue is related to components not being on the same build.

Event ID 1000

Use this information along with any Event Id’s of 1001 to confirm the times when the AOS crashes.

Event ID 1001

This indicates that they have the option marked to send mini memory dumps to the Watson site. Pass the contents of this event on to your Escalation Engineer so they can review it to see if there is information that points to the issue.

Object Server 01: RPC error: RPC exception 1726 occurred in session X

This means that the AOS had data to send back to the client but the client was no longer available. You can see this if users are ending task on the client when they think processes are hung. If the user does this repeatedly in a short time it can cause an AOS crash or it could point to a process that has a problem and causes an AOS crash. Follow the steps in blog on how to trace a session back to a user. This way you can try to determine the process the user was doing and possibly trace that process.

Object Server 01: No ping from XX. Terminating the session

This error message occurs when the AOS tries to ping the client and does not get a response. You can see this if users are ending task on the client when they think processes are hung. If the user does this repeatedly in a short time it can cause an AOS crash or it could point to a process that has a problem and causes an AOS crash. Follow the steps in blog on how to trace a session back to a user. This way you can try to determine the process the user was doing and possibly trace that process.

Object Server 01: SPID XX for session id XX is still present in the database. Please delete the SPID from the database.

 This means that the SQL Server is still processing data from a client session that was terminated. Especially if you see these right before a crash find out the user that this session belongs to using the steps from blog. This will help you determine the user who had a process running but was no longer in the Dynamics AX client. Find out the process they were running, if possible, and try to trace that process or see if you can reproduce an AOS crash.

Object Server 01: Internal version mismatch. Microsoft Dynamics AX Client from MACHINENAME (0.0.0.0) tried to attach with 5.0.1500.4622 revision of AOS kernel."

This indicates that the AOS and the client builds do not match and can cause problems. This message was added to kernel build 5.0.1500.4622 and higher. The amount of detail returned will depend if the client is also at that version or above. Check the sysuserlog table for the buildnum and computername of clients connecting from an earlier build than the AOS. Example: select distinct(BUILDNUM) from SYSUSERLOG where CREATEDDATETIME > '2011-01-01'

Top

 

Still having trouble...

If you are experiencing issues downloading the install file or documentation on CustomerSource/PartnerSource, please contact ITMBSSUP@microsoft.com

  1. Ask the community of users like yourself through the Microsoft Dynamics AX Community here.
  2. For Technical support questions, contact your partner, or if enrolled in a support plan directly with Microsoft, you can enter a new support request to Microsoft Dynamics Technical Support from CustomerSource or PartnerSource under Support >> New Support Request
  3. You can also contact Microsoft Dynamics Technical Support by phone using these links for country specific phone numbers:
    Partners – Global Support Contacts (requires PartnerSource login)
    Customers – Global Support Contacts (requires CustomerSource login)

Top

 

Acronyms used in this article

  • WSS – Windows SharePoint Services

Top