Consider a scenario where you are running AX 2012 and your Dynamics AX databases are part of a SQL Server AlwaysOn Availability Group (AG). I’ll discuss some concepts and points of interest below which are relevant when running AX 2012 RTM, R2 or R3.
We released a useful DIXF Application Hotfix in October 2015 which you may not be familiar with, and as I’ve recently been looking into this for a customer, I thought I would share some details on this topic.
Consider a scenario where you are importing data using DIXF, and you get an error when you try to “Preview source file”. 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.
Consider a scenario where you are using IDMF 2.0, and you want to work with InventTrans and LedgerTrans data, but you cannot find any archive templates for these tables.
Consider a scenario where you are using IDMF 2.0, but one or more of the jobs you are running error. How do you establish what went wrong, so that you can correct the problem? In the example below, I am working with IDMF 2.
Consider a scenario where you want to import data into AX 2012 R3 using DIXF, but you want a particular value to be auto-generated by the system rather than input from a text file.
Consider a scenario where you are importing a lot of data using DIXF, but one or more of the rows in the input file contain “bad data” that result in some rows not being imported OK into your staging table. How do you establish which rows are the problem, so that you can correct them?
The aim of this blog post is to provide you with some suggestions on what information and data to collect and provide when opening a Microsoft support case. You can of course use these suggestions in your own organization too, whether you are a Partner or End User of Microsoft Dynamics AX.
In the previous post in this series, I provided some T-SQL scripts that can check key settings and highlight possible issues you need to address. This post aims to provide some feedback and suggestions on the information the scripts collect.
It’s important to configure your SQL Server instance and your AX databases properly in order to achieve optimal performance on your Dynamics AX environment. This blog post aims to help you do that by providing some T-SQL scripts that can check key settings and highlight possible issues you need to address.
