Troubleshoot general installation issues
Important
This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.
Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
This topic provides information that can help you troubleshoot issues that you may encounter when you run the Setup wizard for Microsoft Dynamics AX.
The Setup wizard does not start automatically
If the Setup wizard does not start automatically when you put the DVD in the drive, double-click the setup.exe file in the root directory of the DVD.
Cannot locate file <Drive>\setup.exe AutoRun=1
When you click Microsoft Dynamics AX components in the initial installation screen, you may receive the message, “Cannot locate file: \<Drive>\setup.exe AutoRun=1”. This message indicates that the file association has changed for the autorun.hta file that is used by Setup.
By default, HTML Application Host is the program that is associated with the .hta file type. However, if Microsoft Visual Studio is installed on Windows Server 2012, the .hta file type can be associated with Visual Studio instead.
To resolve this issue, you can use one of the following options:
Before you run Setup, use the Default Programs Control Panel to associate the .hta file type with the HTML Application Host program.
If you are prompted to choose a program with which to open setup.exe, choose HTML Application Host.
Right-click the file setup.exe and choose Run as administrator.
Right-click the file setup.exe and choose Properties. Click the Compatibility tab. Under Compatibility mode, select Windows 7.
Setup fails
If Setup fails, view the setup log that is created every time that Microsoft Dynamics AX is installed.
Open the setup log file. By default, the path of this file is \%AllUsersProfile%\Microsoft\Dynamics AX\Dynamics AX Setup Logs\Date Time\DynamicsSetupLog.txt.
Find the error message that was generated by the failure. For detailed information, review the information immediately after the error message in the log.
Exception: System.Runtime.InteropServices.COMException
During installation, Setup verifies the operating system version of the computer. If Setup is unable to verify the operating system version, Setup can fail. When this issue occurs, the log file displays the message “Setup encountered an unhandled exception and could not be completed” and the message “Exception: System.Runtime.InteropServices.COMException”. To work around this issue, restart the computer and run Setup again.
Exception from HRESULT: 0x8024402C
During installation, Setup tries to connect to the Microsoft Update website to install updates. Error code 0x8024402C indicates that the connection to the Windows Update servers failed. This error may occur if proxy or firewall settings are configured incorrectly. For more information, see Microsoft Knowledge Base article number 900936.
Buttons are not visible on Setup pages
If Windows runs with certain DPI and resolution settings, Setup pages are not displayed correctly, and you cannot continue.
The following table shows the supported and unsupported DPI and resolution settings for Windows 7 and Windows Server 2008 R2.
DPI |
Resolution |
Supported/Not supported |
|---|---|---|
100 |
800 x 600 |
Not supported |
125 |
800 x 600 |
Not supported |
150 |
800 x 600 |
Not supported |
100 |
1024 x 768 |
Supported Note This resolution is not supported on Chinese operating systems. |
125 |
1024 x 768 |
Not supported |
150 |
1024 x 768 |
Not supported |
100 |
1280 x 1024 |
Supported |
125 |
1280 x 1024 |
Supported |
150 |
1280 x 1024 |
Not supported |
100 |
1600 x 1200 |
Supported |
125 |
1600 x 1200 |
Supported |
150 |
1600 x 1200 |
Supported |
The following table shows the supported and unsupported DPI and resolution settings for Windows Vista and Windows Server 2008.
DPI |
Resolution |
Supported/Not supported |
|---|---|---|
96 |
800 x 600 |
Not supported |
120 |
800 x 600 |
Not supported |
96 |
1024 x 768 |
Supported Note This resolution is not supported on Chinese operating systems. |
120 |
1024 x 768 |
Supported Note This resolution is not supported on Chinese operating systems. |
96 |
1152 x 864 |
Supported |
120 |
1152 x 864 |
Supported |
96 |
1280 x 1024 |
Supported |
120 |
1280 x 1024 |
Supported |
96 |
1600 x 1200 |
Supported |
120 |
1600 x 1200 |
Supported |
You must set a value for the parameter ClientAosServer
When you install Microsoft Dynamics AX silently by using a parameter file, you may incorrectly receive the following error message in the setup log file: “Setup cannot continue. You must set a value for the parameter ClientAosServer.” Verify that the parameter file contains the required value. If Setup continues, and you do not receive any other errors, you can ignore this message.
Label IDs are displayed instead of label text
If label IDs are displayed instead of label text the first time that you start the client, this means that the labels for the selected language are not available. Use one of the following resolutions:
You may have selected a language that has not yet been released for Microsoft Dynamics AX. To resolve this issue, select a supported language.
You may have selected a supported language that has not been installed. To install supported languages other than U.S. English, you must install the Foundation Labels model. For information about which languages are available, and about how to install an additional model, see Install the Microsoft Dynamics AX databases.
Could not load type 'System.ServiceModel.Activation.HttpModule'
After installing a component that uses Internet Information Services (IIS), such as Help Server or web services on IIS, you may receive the following error: “Could not load type 'System.ServiceModel.Activation.HttpModule' from assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'”.
This error indicates that Microsoft .NET Framework 4.0 was installed, and then an earlier version of the .NET Framework was installed, or .NET 3.0 WCF HTTP Activation was enabled.
To resolve the problem, follow the instructions in Microsoft Knowledge Base article 2015129.