Re: dotNET 1.1 SP1 install error on 2003 Server 64-bit DatacenterSP2

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.

LaunchCondition:
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!

~JasonG

--

So after running .NET 1.1 setup like this:

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

[...]

> MSI (c) (E8:F8) [16:17:49:824]: PROPERTY CHANGE: Adding
> SystemFolder.3643236F_FC70_11D3_A536_0090278A1BB8 property. Its value is
> 'C:\WINDOWS\SysWOW64\'.
> 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
> ErrorDialog
> 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.

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

Jason,
This article referrs to a "similar" issue on Vista x64 and dotNET 1.1 SP1.
http://www.mydigitallife.info/2007/12/27/install-microsoft-n et-framework-11-on-windows-vista-fix-regsvcsexe-fails-error/
Maybe you can learn something from there.
Carlos

"Jason Gurtz" wrote:

> 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.
>
> LaunchCondition:
> 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!
>
> ~JasonG
>
> --
>
> So after running .NET 1.1 setup like this:
>
> > D:\tmp\dotNET1.1\dotnetfx>msiexec /i netfx.msi /lvx* d:\tmp\dotNET11.log
>
> [...]
>
> > MSI (c) (E8:F8) [16:17:49:824]: PROPERTY CHANGE: Adding
> > SystemFolder.3643236F_FC70_11D3_A536_0090278A1BB8 property. Its value is
> > 'C:\WINDOWS\SysWOW64\'.
> > 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
> > ErrorDialog
> > 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.
>