Exception Error while installating AX 2012

I'm installing Ax 2012 remotely on the Clients Server. All the pre-requisites for Ax 2012 Installation have been installed and verified. During the Installation when I've select the components to be installed, it gives the following error -

"An unexpected error occured during the setup. See the logfile C:\Program files\ Microsoft dynamics AX\60\Setup Logs\...  for details."

This error comes for both Custom Installation and Single Computer Installation.

When I see the Setup Logs in the 60 folder of MSD AX , I find the following error-

"2011-10-07 06:52:55Z Exception: System.Reflection.ReflectionTypeLoadException

2011-10-07 06:52:55Z Message: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.

2011-10-07 06:52:55Z FullText: System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
2011-10-07 06:52:55Z   at System.Reflection.Module._GetTypesInternal(StackCrawlMark& stackMark)
2011-10-07 06:52:55Z   at System.Reflection.Assembly.GetTypes()
2011-10-07 06:52:55Z   at Microsoft.Dynamics.Setup.Components.ComponentHandler.GetComponents()
2011-10-07 06:52:55Z   at Microsoft.Dynamics.Setup.Components.ComponentHandler.GetComponentsByCompID(CompID cid)
2011-10-07 06:52:55Z   at Microsoft.Dynamics.Setup.Components.ComponentHandler.SetInstallValue(CompID cid)
2011-10-07 06:52:55Z   at Microsoft.Dynamics.Setup.S080FeatureOption.Exec_AXComponentsTreeView_BeforeCheck(AxTreeNode node)
2011-10-07 06:52:55Z   at Microsoft.Dynamics.Setup.AxWizardPageComponentSelection.axComponentsTreeView_BeforeCheck(Object sender, TreeViewCancelEventArgs e)
2011-10-07 06:52:55Z   at System.Windows.Forms.TreeViewCancelEventHandler.Invoke(Object sender, TreeViewCancelEventArgs e)
2011-10-07 06:52:55Z   at System.Windows.Forms.TreeView.TreeViewBeforeCheck(TreeNode node, TreeViewAction actionTaken)
2011-10-07 06:52:55Z   at System.Windows.Forms.TreeView.WndProc(Message& m)
2011-10-07 06:52:55Z   at Microsoft.Dynamics.Setup.PrereqAssembly.AXComponentsTreeView.WndProc(Message& m)
2011-10-07 06:52:55Z   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
2011-10-07 06:52:55Z   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

2011-10-07 06:52:55Z ==== Setup encountered an unhandled exception and could not be completed. For details see the previous messages in the log. === "

Requesting your assistance at the earliest.

  • I am getting the same error.  Did you ever find a solution?

     === Setup logging started: 2/17/2012 3:03:32 PM ===
    Running file: "C:\Program Files\Microsoft Dynamics AX\60\SetupSupport\AxSetup.exe" RelatedFilesDir="E:" AutoRun=1 LogDir="C:\Program Files\Microsoft Dynamics AX\60\Setup Logs\2012-02-17 15-03-30"
    AxSetup version number: 6.0.947.61
    Microsoft Windows NT 6.1.7601 Service Pack 1 (64 bit)
    AX2012AOS-DEV
    CORP\AXqainstaller
    Interactive: True

    2012-02-17 15:03:32Z RelatedFilesDir=E:
    2012-02-17 15:03:32Z LogDir=C:\Program Files\Microsoft Dynamics AX\60\Setup Logs\2012-02-17 15-03-30
    2012-02-17 15:03:32Z Property RelatedFilesDir set to: 'E:\'
    2012-02-17 15:03:32Z Property LogDir set to: 'C:\Program Files\Microsoft Dynamics AX\60\Setup Logs\2012-02-17 15-03-30'
    2012-02-17 15:03:32Z Common Property Install Path set to 'C:\Program Files\Microsoft Dynamics AX\60'.
    2012-02-17 15:03:32Z Installation Path retrieved from registry. Value: 'C:\Program Files\Microsoft Dynamics AX\60'
    2012-02-17 15:03:32Z Initializing log file: C:\Program Files\Microsoft Dynamics AX\60\Setup Logs\2012-02-17 15-03-30\DynamicsSetupLog.txt

    2012-02-17 15:03:32Z  === Starting evaluation of existing installation state ===
    2012-02-17 15:03:32Z Application Object Server instance 01 has been installed with the name 01-MicrosoftDynamicsAX.
    2012-02-17 15:03:32Z MSI file: Components64.msi  Installed: True
    2012-02-17 15:03:32Z MSI file: HelpServer64.msi  Installed: False
    2012-02-17 15:03:32Z MSI file: ClientOba64.msi  Installed: True
    2012-02-17 15:03:32Z MSI file: TraceParser.msi  Installed: False
    2012-02-17 15:03:33Z Previously Installed Component:   Application Object Server (AOS) (01-MicrosoftDynamicsAX)

    2012-02-17 15:03:33Z Previously Installed Component:   Web services on IIS
    2012-02-17 15:03:33Z Previously Installed Component:   .NET Business Connector
    2012-02-17 15:03:33Z Previously Installed Component:   Debugger

    2012-02-17 15:03:33Z Property RunMode set to: 'AddRemoveFeatures'

    2012-02-17 15:03:33Z  === Starting UI phase ===
    2012-02-17 15:03:33Z S030WelcomeInfo
    2012-02-17 15:03:35Z S040MaintenanceMode
    2012-02-17 15:03:37Z Property RemoveComponents set to: '0'
    2012-02-17 15:03:37Z S080FeatureOption
    2012-02-17 15:03:40Z Property BypassWarnings set to: '0'
    2012-02-17 15:03:43Z Property InstallManagementUtilities set to: '1'
    2012-02-17 15:03:47Z Exception: Microsoft.Dynamics.Setup.AxSetupException

    2012-02-17 15:03:47Z  Message: The port number must be a number between 1 and 65535

    2012-02-17 15:03:47Z  FullText: Microsoft.Dynamics.Setup.AxSetupException: The port number must be a number between 1 and 65535
    2012-02-17 15:03:47Z    at Microsoft.Dynamics.Setup.Components.Aos.ValidatePort(String port)
    2012-02-17 15:03:47Z    at Microsoft.Dynamics.Setup.Components.ClientUI.GetClientAosServerAndPortFromRegistry()
    2012-02-17 15:03:47Z    at Microsoft.Dynamics.Setup.S220ClientAosServerEntry.IsPageApplicable()
    2012-02-17 15:03:47Z    at Microsoft.Dynamics.Setup.MainForm.FindNextPage(PageID oldPageID)
    2012-02-17 15:03:47Z    at Microsoft.Dynamics.Setup.S640InitialPrerequisites.IsPageApplicable()
    2012-02-17 15:03:47Z    at Microsoft.Dynamics.Setup.MainForm.FindNextPage(PageID oldPageID)
    2012-02-17 15:03:47Z    at Microsoft.Dynamics.Setup.MainForm.mainFormButtonNext_Click(Object sender, EventArgs e)
    2012-02-17 15:03:47Z    at System.Windows.Forms.Control.OnClick(EventArgs e)
    2012-02-17 15:03:47Z    at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
    2012-02-17 15:03:47Z    at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
    2012-02-17 15:03:47Z    at System.Windows.Forms.Control.WndProc(Message& m)
    2012-02-17 15:03:47Z    at System.Windows.Forms.ButtonBase.WndProc(Message& m)
    2012-02-17 15:03:47Z    at System.Windows.Forms.Button.WndProc(Message& m)
    2012-02-17 15:03:47Z    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    2012-02-17 15:03:47Z    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

    2012-02-17 15:03:47Z  ==== Setup encountered an unhandled exception and could not be completed. For details see the previous messages in the log. ===

  • In reply to Robert:

    Hi,

    Reading through your error log, I found following message -

    Robert
    2012-02-17 15:03:47Z  Message: The port number must be a number between 1 and 65535

    What port number did you provide?

  • In reply to Harish Mohanbabu:

    mohan is correct.

     

    after going through your message carefully, that is the first Exception looking for port number.

    let us know .

  • In reply to eswar:

    I was not prompted for a port # since I was adding a component to my AOS.  We cannot install the management tool.  I installed the orignial AOS with the default setting 2712 and 8101.

    Were you referring to a different port?

  • Hi Guys,

    Such error occurs when missing msi file in C:\Windows\Installer. This is a windows issue.

    Missing file May have been caused by manual intervention or third party software, but not traceable.


    I would suggest you to ask your infrastructure team to rebuild the machine as explained in the following link:

    Please see: support.microsoft.com/.../2667628

    The Windows Installer Cache, located in c:\windows\installer folder, is used to store important files for applications installed using the Windows Installer technology and should not be deleted. If the installer cache has been compromised, you may not immediately see problems until you perform an action such as uninstall, repair, or update on a product.

    When a product is installed using Windows Installer critical files are stored in the Windows Installer Cache (default is C:\Windows\Installer). These files are required for uninstalling and updating applications. Missing files cannot be copied between machines since they are unique.

    If files are missing from the Windows Installer Cache, you will have to rebuild the operating system and reinstall applications.
Related
Recommended