dotNET 1.1 SP1 install error on 2003 Server 64-bit Datacenter SP2

Discussion in 'Windows 64bit' started by Jason Gurtz, Jan 22, 2008.

  1. Jason Gurtz

    Jason Gurtz Guest

    SQL 2005 64-bit and IIS also installed on the machine with latest SP and

    Here's the error when you run the installer:

    This setup is not supported on 64-bit versions of Windows XP

    So I extracted it and ran it like this:

    D:\tmp\dotNET1.1\dotnetfx>msiexec /i netfx.msi /lvx* d:\tmp\dotNET11.log

    I got a little bit more output but still nothing any more useful to my
    eye. We need to install this due to a third party application from UAI

    Here's some of the output of the log surrounding the error:

    MSI (c) (E8:F8) [16:17:49:824]: PROPERTY CHANGE: Adding
    SystemFolder.3643236F_FC70_11D3_A536_0090278A1BB8 property. Its value is
    Action ended 16:17:49:
    SystemFolder.3643236F_FC70_11D3_A536_0090278A1BB8. Return value 1.
    MSI (c) (E8:F8) [16:17:49:824]: Doing action: LaunchConditions
    Action 16:17:49: LaunchConditions. Evaluating launch conditions
    Action start 16:17:49: LaunchConditions.
    Info 2898.Tahoma08, MS Sans Serif, 1
    DEBUG: Error 2835: The control ErrorIcon was not found on dialog
    Internal Error 2835. ErrorIcon, ErrorDialog
    This setup is not supported on 64-bit versions of Windows XP
    MSI (c) (E8:F8) [16:17:52:918]: Product: Microsoft .NET Framework 1.1 --
    This setup is not supported on 64-bit versions of Windows XP

    Action ended 16:17:52: LaunchConditions. Return value 3.
    MSI (c) (E8:F8) [16:17:52:918]: Doing action: FatalError
    Action 16:17:52: FatalError.
    Action start 16:17:52: FatalError.
    Action 16:17:52: FatalError. Dialog created
    MSI (c) (E8:94) [16:17:52:980]: Note: 1: 2731 2: 0
    Action ended 16:17:55: FatalError. Return value 2.
    Action ended 16:17:55: INSTALL. Return value 3.

    Anyone have any clue? I have this same error on our other 64-bit server
    also, but don't need 1.1 on that machine. Anything I can forward to the
    UAI/Trimble developers would possibly be helpful too.



    Jason Gurtz, Jan 22, 2008
    1. Advertisements

  2. Jason Gurtz

    Jane C Guest

    Jane C, Jan 22, 2008
    1. Advertisements

  3. Jason Gurtz

    Jason Gurtz Guest

    I think the above is just the service pack 1 for .NET 1.1. When I run
    NDP1.1sp1-KB867460-X86.exe it says this:

    The upgrade patch cannot be installed by the Windows Installer service
    because the program to be upgraded may be missing, or the upgrade patch
    may update a different version of the program. Verify that the program
    to be upgraded exists on your computer and that you have the correct
    upgrade patch.

    I need to reinstall the whole of .NET 1.1 with the redistributable.
    Redistributable is dotnetfx file version 1.1.4322.573 and is available at

    This is what gives me the error message I posted first.


    Jason Gurtz, Jan 23, 2008
  4. Jason Gurtz

    Carlos Guest

    Do you comply with the "Server Installation Requirements" mentioned in the
    "Additional Information" portion of "Microsoft .NET Framework Version 1.1
    Redistributable Package" web page (the one you posted as reference)?
    Just a hunch.
    Carlos, Jan 23, 2008
  5. Jason Gurtz

    Jason Gurtz Guest

    Well all those pre-requisites are met just by virtue of being the Server
    2003 platform. MDAC 2.8 SP2 comes standard and IIS6 comes standard (IIS
    is installed a running). Don't see how that section has anything to do
    with my issue.


    Jason Gurtz, Jan 23, 2008
  6. Jason Gurtz

    Jason Gurtz Guest

    OK, I'm not done with this and now something is really starting to smell
    fishy. So, I've dug in to the msi... See:

    Unfortunately for me and just a few others, the broken scenario is not
    quite as is described in that posting (There is a
    %windir%\Microsoft.NET\Framework\v1.1.4322\ but it is empty). This
    could potentially be the case with others since often with a broken .NET
    it is recommended to uninstall .NET completely using Arron's tool! So,
    running a repair install with msiexec /f.... results in failure (with
    the same "Setup not supported on 64-bit versions of Windows XP").

    Strangely, on the other (production) 64-bit box, that directory seems to
    have the full of .NET in that dir but repair fails there with the same
    "Setup not supported on 64-bit versions of Windows XP."

    So that "shim" that the blog mentions must be missing in the OS? I
    would love to find out how to re-create it. Alternatively, I have been
    playing with orcas and some other msi dumping tools and feel confident I
    could comment out the LaunchCondition table and rebuild the msi to
    install on any 64-bit OS. Note VersionNT64 is true on 64-bit versions
    of XP and 2003 server so the Description field is misleading.

    NOT (VersionNT64),This setup is not supported on 64-bit versions of
    Windows XP

    Is it worth going to this trouble or will it result in a broken .NET 1.1?

    It seems like either IIS or SQL 2005 installation has something to do
    with this issue, though it will be tough at this point to recreate it.

    Any help/suggestion appreciated!



    So after running .NET 1.1 setup like this:
    Jason Gurtz, Jan 25, 2008
  7. Jason Gurtz

    Carlos Guest

    This article referrs to a "similar" issue on Vista x64 and dotNET 1.1 SP1.
    Maybe you can learn something from there.

    Carlos, Jan 26, 2008
  8. Jason Gurtz

    Jason Gurtz Guest

    Special thanks to Aaron Stebner and Heath Stewart both of MS. W/O you
    two I'd be very stuck!

    Here are the steps taken:


    Installing .NET 1.1 on 64-bit Windows Server 2003 R2 SP2

    I. Workaround non-working Application Compatability Database

    This works around the "Setup is not supported on 64-bit versions
    of Windows XP" Error message. Details are at:

    Visit <> and
    download the sdb2xml utility, placing it in a temporary working

    Copy %windir%\AppPatch\msimain.sdb to the same working directory

    Open a cmd prompt windows and navigate to the temp dir.

    Run this: sdb2xml msimain.sdb -out msimain.xml -extract

    Keep the file netfx64.mst. All the other files may be deleted.

    II. Replace Missing Registry Entries

    Found via:

    Be careful! 64-bit slightly different. Copy the following to a
    .reg file and import it.

    <copy below>
    Windows Registry Editor Version 5.00





    <copy above>

    III. Replace Missing SysWoW64 DLL File (mscoree.dll 32-bit)

    This works around a 1935 error with HRESULT 0x8002802F appearing in
    the application event log and verbose installer log. Deduced via
    Process Monitor and

    Copy %windir%\System32\mscoree.dll from a 32-bit, fully up to date
    Server 2k3 SP2 or XP SP2 machine and paste in %windir%\SysWOW64\

    As of 29Jan 2008 mscoree.dll should be version:
    2.0.50727.1433 (REDBITS.050727-1400)

    IV. Temporarily Disable DEP Security Feature.

    The version of RegSvcs.exe included and used during .NET 1.1
    installation is not compatibile with Data Execution Prevention.
    Found via:

    Edit your boot.ini file and make sure /NoExecute=AlwaysOff is part
    of the boot options. Save and reboot to apply. After installing
    the .NET 1.1 framework you should change that option back to
    /noexecute=optout for enhanced security.

    V. Running Installation While Applying Transform File

    Extract the contents of dotnetfx.exe to your temp dir from way back
    in step I using WinRAR or similar. The contents of the temp dir
    should be this:


    From a cmd prompt in the dir run setup like this:

    msiexec /i netfx.msi /lvx* Log.txt TRANSFORMS=netfx64.mst

    Accept the license agreement and you should be sorted. :)

    If you have other problems (hopefully not!) you can refer to the
    generated log file.
    Jason Gurtz, Jan 29, 2008
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.