Views:

Applies to Product - Dynamics 365 Lifecycle Services


What’s happening?
Customers are unable to perform data migration from one environment to another, specifically facing issues with the Data Migration Tool (DMT) where the installer does not appear, preventing migration from AX 2009 to Finance.
 

Reason:
The underlying cause of this may relate to missing prerequisites for the DMT installation, such as the required SQL Server version, .NET Framework, and the necessary services not being installed or running. Additionally, issues may arise from the specific version of the environment not meeting the requirements outlined in the official documentation.
 

Resolution:

  1. Verify Prerequisites: Ensure that the following prerequisites are met:
  2. Microsoft SQL Server 2012 Native Client is installed.
  3. Microsoft .NET Framework version 4.5 or later is installed.
  4. The Microsoft SQL Server Integration Services (SSIS) service is installed and running on the machine where the DMT service will be installed.
  5. SQL Server authentication must support both SQL authentication and Microsoft Windows authentication.
  6. Ensure that the Microsoft Access database engines follow the version guidance provided in the documentation.
  7. Check Documentation: Refer to the official Microsoft documentation for installing the Data Migration Tool and ensure that all steps are followed correctly. The relevant links include:
  8. Install the Data Migration Tool
  9. DMT Installation Guide
  10. Screen Sharing Session: If issues persist, schedule a screen-sharing session to review the setup and installation process in real-time.
  11. Upload Error Logs: If applicable, request the customer to upload any error logs encountered during the installation or migration process for further analysis.
  12. Follow Up: Maintain communication with the customer to ensure that they have received the necessary support and to confirm if the issue has been resolved. If the issue remains unresolved, continue to provide assistance as needed.
If the above steps do not resolve the issue, further investigation may be required based on the specific error messages encountered.