Consider a scenario where you are using IDMF 2.0, and you find that after each IDMF Metadata sync the Master table list gets refreshed and you then have to manually sort out the list each time by unchecking/checking tables as Master tables. Well, there’s a simple way to change that default behaviour: 1. Update AXDataManagementSchedulerService.exe.
There are several ways to approach troubleshooting performance, and the aim of this blog post is to give Customers and Partners some guidance on what information and data to provide when you need help trying to establish why something is “slow”.
Consider a scenario where you are importing data using DIXF, and you get an error when you try to “Preview source file” and you are running SQL Server 2014 SP2 CU10 or CU11. 1. The error The error you see looks something like this: System.ServiceModel.CommunicationException: An error occurred while receiving the HTTP response to http://servernamehere:7000/DMFService/DMFServiceHelper.svc.
As I am sure you are already aware, you can now submit requests directly to the Dynamics Service Engineering (DSE) team by using Lifecycle Services (LCS). Submit a request to the Dynamics Service Engineering team https://docs.microsoft.
Consider a scenario where you are running AX 2012 and your Dynamics AX databases are hosted on a Clustered SQL Server instance. I’ll discuss some concepts and points of interest below which are relevant when running AX 2012 RTM, R2 or R3.
I’ve seen this error a couple of times in the past month or so, and I’ve also noted that some people have asked about it on the Internet, too. I’ve just finished working on a case with a customer where we were able to reproduce this issue on a VM.
We’ve recently released some kernel fixes that improve how Microsoft Dynamics AX 2012 R2 and R3 handle SQL Server AlwaysOn AG failovers. The R3 version of this fix is visible on LCS here: LCS | AX 2012 R3 Kernel Fix KB3159596 | Handle SQL Server AlwaysOn AG failovers more transparently and gracefully https://fix.lcs.dynamics.com/Issue/Resolved?
From time to time we see questions about the compatibility statements and what they mean. The most common question relates to whether they apply to the kernel or the application. A common misconception is that you only need to patch the kernel rather than the application. This is not the case.
Consider a scenario where you are running AX 2012 R3 and you want to import data from Excel files using ODBC. Having recently worked a case on this topic, I thought I’d share some of the details on how this can be set up. 1.
Consider a scenario where you are running AX 2012 R3 and you want to compare entities between AX companies using DIXF, but you get an error telling you that the SQL Server replication tool is not installed. 1.
Consider a scenario where you are running AX 2012 R3 and you want to archive or purge data from a custom table in AX using IDMF. The screenshots are from a VM TEST environment with CONTOSO DEMO DATA that is running AX 2012 R3 CU10 on SQL Server 2014 and the latest version of IDMF.
I recently worked on a case with a Partner that reported that the ‘Name’ field for the DMFASSETENTITY entity did not get imported as expected into their AX 2012 R3 CU9 environment, so I thought I would share how we resolved that by manually adding the mapping, and how we tested the solution. 1.
