In this instance there is a solution by implementing the latest Kernel hotfix on Dynamics Ax 4 SP2 to solve the issues. These integrations needs to be tested before a go-live on an upgraded kernel.įor example, a customer (using Dynamics Ax 4 SP2) want’s to upgrade their PC clients to Windows 7, there is no problem with the business logic functionality but with the GUI. NET Business Connector or the Dynamics Ax BizTalk adaptor, handle printer routines, accesses the SQL Server database etc. The kernel is used for example to generate the GUI, handle integrations with third party solutions by the use of. The kernel is the “engine” in a Dynamics Ax environment, that is present both in the Dynamics Ax Object Server (AOS) service and the Dynamics Ax client (the “fat” client). But, even if it is “just” a kernel change there can be pit holes. In most cases an upgrade to the latest kernel is a viable option for most Dynamics Ax installations. For example, if an implementation project used 1000 hours the application upgrade will use 1/10 of that time, i.e 100 hours. The most important for the customer is a stable and reliable Dynamics Ax environment and last but not least a fit of the business logic to their business.Ī rule of thumb is that an application upgrade is done in 1 tenth of the time the original implementation project was done. I am a pro upgrade guy but at the same time I do not expect my customers to be on the latest CU/RU release. Most companies using Dynamics Ax have customization done in the application that in many ways changes the business logic to better match that of the organization. In many situations it can be hard for a consultant to motivate an upgrade of a customer’s Dynamics Ax environment for small issues.
#MICROSOFT DYNAMICS AX ENTERPRISE PORTAL EVENT ID 1000 UPDATE#
The recommendation from Microsoft is that all Dynamics Ax installations should be on the latest Cumulative Update (CU) release level for Ax 2012 and Roll Up release level for Ax 2009.