Common Problems & Solutions ( AX 2009 )

Common Problems & Solutions

  • We have found that in a number of AOS crash cases they are resolved by installing the latest kernel hot-fix. Therefore it is recommended that you consider implementing the latest kernel roll-up 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.

Comments

Post a Comment

Popular posts from this blog

AOS machines application ( events )

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.
Read more

Critical Hot fixes ( AX 2009 )

Critical Hot fixes 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 w
Read more

This transaction has been marked for settlement by another user in AX 2009 / 2012

Image
“I need to settle a customer (or vendor) transaction but when I go to the ‘Settle open transactions’ form for the customer (or vendor), I cannot mark the transaction. There is a red icon in the ‘Is marked’ field and I receive an error if I try to mark. I’ve looked all over and I cannot find where to unmark it." Solution When this happens, the user has generally already done their due diligence and checked the likely places to find where the transaction may be marked – in other journals of the same type, in the Settle open transactions form, etc. and still cannot find where it is mysteriously marked. To find where the transaction is marked, take the following steps: 1. Go to Accounts receivable-> Common-> Customers-> All customers-> highlight customer-> Collect tab-> Settle open transactions (similar path for Vendor transactions). Normally you will see the transaction still has the red icon indicating the transaction is still marked elsewhere. 2. Highlight the rec
Read more