Below I have included Microsoft's own positioning of the Dynamics ERP products. Generally, it's difficult to gain an unbiased answer from a Dynamics Partners as they are expressing their own interests based on their line of Dynamics Business.
Microsoft Dynamics AX 2012 Trace Parser is a wonderful tool which can help you in identifying fairly good amount of performance problems within your installations. I would say if you have customizations you should know how to use this tool J.
So what is Microsoft Dynamics AX 2012 Trace Parser??
Trace Parser provides user interfaces to import, process and render ETW tracing events that produced by Microsoft Dynamics AX. User can then analyze tracing events to identify performance bottlenecks such as long-running X++ methods, slow SQL queries and frequently called RPCs. Features in Trace Parser help users determine the root causes of performance problems.
Today I was doing some AX 2012 performance R&D to see how big is the contirbution of SQL to AX 2012 performance issues.
From my experience and following Microsoft guidelines, we would strongly recommend not to virtualize your Microsoft SQL server. For larger Microsoft Dynamics AX 2012 installations a Microsoft SQL Server installation on physical hardware is recommended. However, Microsoft supports Microsoft Dynamics AX 2012 installations with virtualized hardware for a number of virtualization solutions.
Take an example, for 10 items shipped in a Transfer Order you have received only 8. You can do the following to close the transfer order.
In the Setup tab, of the transfer order, you can place a % for Under delivery, in order to consider the order as completed.
I was playing around with AX 2012 in one of my labs and I started getting following error.
To be frank with you, I had made couple of KB updates and few cuddling with my system registry for checking some components. But believe me I landed up in a mess and started getting the following error, was clueless on what was leading to this issue.