Dynamics Doctor

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.

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 wh

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

The Microsoft Dynamics AX 7 release date is scheduled for later in 2015, and from what has been revealed so far, it’s going to be all about the cloud. Dynamics AX 7 is expected to be loaded with  following key features: 1)  I mproved cloud access and mobility As mobile devices begin to take the place of the traditional office tools, employees are increasingly using them to access data, offer sales quotes, check inventory and financial data and more. Dynamics AX 7 will include the enhancements to improve cloud access and mobility. 2)  New browser-based interface A browser-based interface will replace the current Windows Client making Dynamics AX capabilities available via new “work spaces,” promoting remote access across a variety of device platforms for enhanced collaboration. 3 )  Next generation user experience Superior user experience will be delivered via the context-sensitive Windows 8 framework, based on the HTML5 technology. 4) Life-cycle management Excelle