Problem with .Net 2.0 SP2 on Windows 2008

[kaepteniglo]

Do you know, that Windows Server 2008 R2 is only available in 64Bit?

That means you have to install the x64-Version of .NET Framework

[IFoutz]

I am aware of that, yes, but this is SP2 of 2008, not 2008 R2.

[Aaron Young]

We have run into this with our customers also, but have been unable to replicate it in-house using Virtual or Physical machines and all available Editions of Windows 2008 Server (not R2) with all available Windows Updates/Service Packs applied.

Our short-term solution was to introduce a command-line to bypass the .NET prerequisite in this situation, (which so far seems very rare), but we're hoping that upgrading to IA 9 R2 will fix it with the new OS variable for WS2008, but we haven't gotten to a point where we can do this yet.

Regards,

- Aaron.

[Roostar2004]

I was wondering if this has been addressed in a newer version of Installaware. It seems that the thread just died. The reason why I am asking is that one of our users ran into this same problem. The only way that we could resolve the issue was to change the registry value so that it would not try and install .NET 2 SP2.

The question that I have which is the same as other posts in this thread is what is the "expected" behavior of the following code when running server 2008 (non r2).

Code: Select all

~InstallAware Clipboard Data~
~Get System Settings~
~{E5AF7FD7-9D49-4413-8D03-3F04FA4BDB7C}~
~NET2SP2_ISVISTA~
~69~

If it is suposed to return true than it seems to be failing, if it is suposed to return false because we need an additional check then I am okay with that. Would I need to specificly use the following code to check for server 2008?

Code: Select all

~InstallAware Clipboard Data~
~Get System Settings~
~{E5AF7FD7-9D49-4413-8D03-3F04FA4BDB7C}~
~NET2SP2_ISVISTA~
~76~

[mills]

I can't paste the code you posted... "Invalid clipboard data". Could you copy as text and post it?

[Roostar2004]

This is the current code:

Code: Select all

Get System Setting Windows Vista into NET2SP2_ISVISTA
if Variable NET2SP2_ISVISTA Equals TRUE
 Comment: On Vista, read a file version to determine the .NET 2 SP2 installation state
 Get Folder Location System->Windows Directory into NET2SP2_WINDIR
 Check File Version $NET2SP2_WINDIR$\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll into Variable NET2SP2_FILE
 if Variable NET2SP2_FILE Equals TRUE
   Set Variable NET2SP2 to TRUE
   else
   Set Variable NET2SP2 to FALSE
 end
 else

I was wondering for Server 2008 should this check return true or do I need to put in specific checks for server 2008 such as:

Code: Select all

Get System Setting Windows Vista into NET2SP2_ISVISTA
if Variable NET2SP2_ISVISTA not Equals TRUE
 Get System Setting Windows 7 into NET2SP2_ISVISTA
 if Variable NET2SP2_ISVISTA not Equals TRUE
   Get System Setting Windows 2008 R2 into NET2SP2_ISVISTA
   if Variable NET2SP2_ISVISTA not Equals TRUE
     Get System Setting Windows 2008 into NET2SP2_ISVISTA
   end
 end
end
if Variable NET2SP2_ISVISTA Equals TRUE
 Comment: On Vista, read a file version to determine the .NET 2 SP2 installation state
 Get Folder Location System->Windows Directory into NET2SP2_WINDIR
 Check File Version $NET2SP2_WINDIR$\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll into Variable NET2SP2_FILE
 if Variable NET2SP2_FILE Equals TRUE
   Set Variable NET2SP2 to TRUE
   else
   Set Variable NET2SP2 to FALSE
 end
 else

[mills]

In the virtualized Windows 2008 (and R2), both return TRUE for:

Code: Select all

Get System Setting Windows Vista into NET2SP2_ISVISTA

I added a messagebox to check the value.

My advise for those that are experiencing this issue on an isolated user's machine, I would add messageboxes to the script (or write to a file, which would be easier for the user) to track the progress that's made and why it's trying to install it if it's already there...

[roecki]

This problem still exists with IA 10 (Windows 2008 Server Standard 64 bit, not tested with R2).

When will this be fixed?

Anton

[roecki]

Hi,

when using Windows Server 2008 R2 Standard x64 the variables are having this values:
NET2SP2 is TRUE
NET2SP2_ISVISTA is TRUE

when using Windows Server 2008 Standard x64 the variables are having this values:
NET2SP2 is FALSE
NET2SP2_ISVISTA is TRUE

Shouldn't NET2SP2 always be TRUE if NET2SP2_ISVISTA is TRUE?

Anton

[J. M.van der Kolk]

Has this issue been resolved in InstallAware 10?

[giaviv]

Dear InstallAware users,

We are now looking into this issue. Please provide us with as much information as possible such as:
1) What the problem is exactly
2) What OS does it happen on
3) How to reproduce this issue

Thanks!

[J. M.van der Kolk]

Thank you for looking into this.

I am building up a battery of test machines to validate when we see the issue. So far I have issues installing .Net Framework 2.0 on:
- Windows Vista SP1
- Windows Vista SP2
- Windows 2008 Server R2

I build a new installer that has all .Net versions as of .Net Framework 2.0 included in the prerequisites. I did this using InstallAware 10. I get this error message on each of the platforms above:

Microsoft .NET Framework 2.0 Client with Service Pack 2 cannot be installed alongside Microsoft .NET Framework Full Edition.

[Bar_BQ]

Hi,

The problem is that IA forces .Net2sp2 installation on Windows Server 2008 no matter wether it is already installed or not. This essentially means that user cannot perform installation at all. I omitted the problem by changing error message box to allow continuing installation. Hard to believe this problem exists over a year, many times reported and still unsolved...

Regards,
BarBQ

[ramil.domingo]

I would like to report that this problem still exists even in the current IA version 2012 (Build 9.26.11). When can this be resolved?

[FrancescoT]

Dear Ian,

For what I see the only two conditions checked are exactly those you told.

So the dialog box comes up as warning ... if one of those condition are not met.

I would like to suggest you, could you place some dialogs for debug purpose in the checknet2sp2 script and then run it at your customer site, in order to exactly verify who is triggering the issue?

Maybe you've already done it ... but it is the only possible suggestion that comes to my mind.

Let me know.