Aaron Ruckman's Web Log : sp1

When installing .NET Framework 3.5 on Vista what does the .NET Framework 2.0 SP1 on Vista error code 1058 mean and how do I work around it?

aaronru — Wed, 21 May 2008 07:41:00 GMT

If you see an error like:

[05/20/08,14:05:17] Microsoft .NET Framework 2.0SP1 (CBS): ***ERRORLOG EVENT*** : Error: Installation failed for component Microsoft .NET Framework 2.0SP1 (CBS). MSI returned error code 1058

[05/20/08,14:05:17] Setup.exe: GetGlobalCustomProperty - Property: {BBE1827C-F2FD-4FDA-A6D6-C83B62FFFDCA} - PropertyName: compfailed - Value: 0

Then that is a known issue with your machine having the IIS server turned off and it needs to be turned on. The reason is that some of the ASP.NET updates require the Server to be running during install.

After installing .NET Framework 3.5 (which applies the .NET Framework 2.0 SP1 and 3.0 SP1 Updates) then you can turn the IIS server service back off.

For a more detailed description of how to find this type of error see the following:

When analyzing .NET FX 1603 errors, start with the dd_dotnetfx35install.txt log file.

Search for “1603” in the log.

In your case:

[07/17/07,13:44:29] Microsoft .NET Framework 3.5 'package': ***ERRORLOG EVENT*** : Error: Installation failed for component Microsoft .NET Framework 3.5 'package'. MSI returned error code 1603

Scroll up a few lines and note the name of the MSI log:

[07/17/07,13:44:09] Microsoft .NET Framework 3.5 'package': Enabling MSI log file: C:\DOCUME~1\username\LOCALS~1\Temp\dd_NET_Framework35_MSI69C8.txt

Open that log file.

Search for “return value 3”. This is what typically results in a 1603 error.

Action ended 13:44:25: InstallExecute. Return value 3.

Scroll up a few lines to see the actual error:

07/17/07 13:44:24 DDSet_Error: The Commandline '"C:\WINDOWS\Microsoft.NET\Framework\v3.5\WFServicesReg.exe" /c /v /m /i' returned non-zero value: -2147023838.

In this case, there is more:

DDSet_Warning: CScriptMapsComponent::Initialize m_spAdminBase.CoCreateInstance failed. Error code: 0x80070422

DDSet_Warning: CFxInstaller::SetupScriptMapsIIS6 Failed to initialize IIS6 APIs. Error code: 0x80070422

DDSet_Status: CScriptMapsComponent::Close

DDSet_Error: CFxInstaller::SetupComponents SetupScriptMaps failed. Error code: 0x80070422

Find out what the error code means:

# as an HRESULT: Severity: FAILURE (1), FACILITY_WIN32 (0x7), Code 0x422

# for decimal 1058 / hex 0x422

ERROR_SERVICE_DISABLED winerror.h

# The service cannot be started, either because it is

# disabled or because it has no enabled devices associated

# with it.

# 1 matches found for "-2147023838"

The installation needs the IIS Service running on your machine.

.NET Framework 3.5, 3.0 SP1 & 2.0 SP1 Language packages

aaronru — Mon, 21 Apr 2008 20:26:00 GMT

Recently the .NET Framework 3.5 Language packages were released.

You can get them by going to the following Microsoft Download center details page.

2.0 x86 -- http://www.microsoft.com/downloads/details.aspx?FamilyId=5F7F4632-C9C0-4E79-B269-C2AEE9D1962E&displaylang=en

2.0 x64 – http://www.microsoft.com/downloads/details.aspx?FamilyId=1CC39FFE-A2AA-4548-91B3-855A2DE99304&displaylang=en

2.0 ia64 – http://www.microsoft.com/downloads/details.aspx?FamilyId=DE4DFCCD-E75F-4C2F-9991-565A69AF9015&displaylang=en

3.0 -- http://www.microsoft.com/downloads/details.aspx?FamilyId=B3E05715-4D28-4C18-9A60-E26C0E3FFE1E&displaylang=en

3.5 -- http://www.microsoft.com/downloads/details.aspx?FamilyID=c78987b9-97f4-455f-bee7-f6bfa4ad774e&DisplayLang=en

After you browse to the page then you will need to choose a language. When you choose that language click download to attempt to download and install that language package.

.NET Framework 3.0 SP1 & 2.0 SP1 on Vista RTM?

aaronru — Mon, 21 Jan 2008 06:14:00 GMT

I've received the following type of question a few times and would like to give the answer with some background:

Q. Where is the .NET Framework 3.0 SP1 & 2.0 SP1 for Vista RTM?

A. .NET Framework 3.0 & 2.0 released with Vista as OS Windows Components, which means that they are serviced as any other windows Component. Therefore, the .NET Framework 3.0 & 2.0 Service packages will be officially released as part of the Vista Service packages. When Vista SPX is shipped then .NET Framework 2.0 & 3.0 might also include updates in that service package.

In this case the .NET Framework 3.0 & 2.0 have a service package that will be shipped with Vista SP1. Vista SP1 RC is available now (http://technet.microsoft.com/en-us/windowsvista/bb738089.aspx)

NOTE: The same logic stated for Vista and .NET Framework will also be true for Windows2008 & .NET Framework 2.0 & 3.0, only Windows Server2008 will release with .NET Framework 2.0 SP1 & 3.0 SP1 in the OS.

Recent .NET Framework KBs enumerated

aaronru — Thu, 03 Jan 2008 02:21:00 GMT

With .NET Framework 3.5 on Vista or LHS you might get one of the following KBs installed. The following table helps to identify which KB matches what Framework version and which language.

LCID = Language Code ID.

NetFx2.0 SP1 & NetFx3.0 SP1 = These KBs are the representation for the Language enabling packages.

The English + CORE packages must be present prior to installing an additional language package.
The non-English KBs are included in the appropriate 3.5 language package.

2.0 & 3.0 RTM Stand Alone Language Pack = These KBs enable Users to install a .NET Framework Language on Vista or LHS when the OS Language package, which contains the 2.0 & 3.0 RTM, is not installed.

These are included in the 3.5 Language packages and installed as appropriate.
Note that the 936704 & 936705 are not necessary, as 110806 and 929300 contain all of the relevant files anyway.

LCID	Language	NetFx2.0 SP1	2.0 RTM STAND ALONE LANG Pack	NetFx3.0 SP1	3.0 RTM STAND ALONE LANG Pack
1033	English+CORE	110806	936704	929300	936705
1041	Japanese	935953	936382	935952	936428
1031	German	936360	936383	936406	936429
1036	French	936361	936384	936407	936430
1028	Chinese (Traditional)	936362	936385	936408	936431
2052	Chinese (Simplified)	936363	936386	936409	936432
1042	Korean	936364	936387	936410	936433
3082	Spanish	936365	936388	936411	936434
1040	Italian	936366	936389	936412	936435
1025	Arabic	936367	936390	936413	936436
1046	Brazilian Portuguese	936368	936391	936414	936437
2070	Portuguese	936369	936392	936415	936438
1029	Czech	936370	936393	936416	936439
1030	Danish	936371	936394	936417	936440
1043	Dutch	936372	936395	936418	936441
1035	Finnish	936373	936396	936419	936442
1032	Greek	936374	936398	936420	936443
1037	Hebrew	936375	936399	936421	936444
1038	Hungarian	936376	936400	936422	936445
1044	Norwegian	936377	936401	936423	936446
1045	Polish	936378	936402	936424	936447
1049	Russian	936379	936403	936425	936448
1053	Swedish	936380	936404	936426	936449
1055	Turkish	936381	936405	936427	936450

Creating .NET Framework 3.0 SP1 redist

aaronru — Thu, 13 Dec 2007 19:11:00 GMT

Please follow the official guidelines at

http://msdn.microsoft.com/en-us/library/cc160716.aspx

.NET framework 3.0 SP1 & 3.5 download managers

aaronru — Thu, 13 Dec 2007 18:03:00 GMT

.NET Framework 3.0 SP1 & 3.5 released with a small webdownload, which then manages the installation of .NET Framework across all supported OS and architectures. This Blog will explain what they are and how to use them in your role as an end-user, Administrator and ISV.

For End Users, we expect that you will get the .NET Framework 3.0 SP1 and .NET Framework 3.5 in one of the following ways:

Downloading it from the links above
via Windows Update as they become available
Preinstalled on your box by an OEM like Dell, HP, Gateway, etc.
Your network administrator might install it for you
An ISV (application like ATI Catalyst) will install it as a prerequisite for an application that you might want to install.

If you download it yourself, then just go ahead and follow the instructions at the above links.

For ISVs and administrators, you should understand the process of what happens during the download steps. This is what is happening under the covers:

It looks to see what you need to install on your machine and makes a list, which generates the total download size, this is displayed in the UI.
Then it beings the download process

It first looks for each file in the list locally in a known and predetermined location verifying that it has the right package locally, if it exists then it moves to the next one.
If it does not exist locally, or if the validation fails on the local package, then it will attempt to download one for you from the internet, securely from Microsoft.

After it has a full set of files that match what it thinks it needs then the download manager installs them.

This is very powerful in that now an ISV does not need to carry additional binaries for supported by non-mainline scenarios. For example, an ISV might want to support both x86 & x64 but they know that they will have 80% of their customers on x86. Therefore, they can optimize their redistributable experience in that they carry only the x86 packages, and let the bootstrapper download the x64 packages for the additional 20%. Also, if a package becomes corrupted, then it provides a way to self heal the installation via a download.

For Administrators & ISVs, I've been getting the question frequently lately regarding what happened to the redist packages that we are used to?

In the past we were also asked why do I have to carry everything in the Redist, when I don't need everything for my particular scenario?

We addressed both of these issues of why do I have to carry everything and what happened to the redist packages in this implementation of the download manager.

(Full Admin guides for 3.5 & 3.0 SP1 are in the publishing pipeline, the following is just to whet your appetite)

For 3.0 SP1 see the following blog: http://blogs.msdn.com/aaronru/archive/2007/12/13/creating-net-framework-3-0-sp1-redist.aspx

For 3.5, please wait for the admin guide, which will be published soon.

.NET Framework 3.5 Installation validation tool

aaronru — Fri, 30 Nov 2007 07:41:00 GMT

If you want to detect if your .NET Framework 3.5 installation was successful, you can use this tool to verify that the right versions are installed.

Instructions:

1. Download the following file to your computer: http://cid-e7f319723234fb5c.skydrive.live.com/self.aspx/Public/netfx35tools/NetFx35_detect_issues.bat

2. Open a command prompt by doing start -> run and type cmd.

3. enter the full path to where the script runs.

What is happening:

This script will check the registry for the right versions of the .NET Framework 3.5, .NET Framework 3.0 SP1 & .NET Framework 2.0 SP1. they are not there then it will return what it did find and let you know that an error happened.

Further on Vista, it will tell you if you have appropriately installed .NET Framework 2.0 SP1 & 3.0 SP1.

Return codes:

0 == Success

>0 == Failure

.NET Framework 3.5 RTM Detection Logic.

aaronru — Mon, 26 Nov 2007 18:44:00 GMT

When you install .NET Framework 3.5, it installs .NET Framework 3.0 SP1 & .NET Framework 2.0 SP1, or equivelent cumulative update on Vista.

For 3.5 RTM we look for the following:

Registry Key Name

Value

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\

NET Framework Setup\NDP\v3.5

Name: Install

Type: DWORD

Data: 1

For 3.0 RTM see the following:

http://msdn2.microsoft.com/en-us/library/aa964978.aspx#DetectingTheMicrosoftDotNETFramework3_0

For 3.0 SP1 we look for the following:

Registry Key Name

Value

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\

NET Framework Setup\NDP\v3.0

Name: SP

Type: DWORD

Data: 1

For 2.0 SP1 we look for the following:

Registry Key Name

Value

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\

NET Framework Setup\NDP\v2.0.50727

Name: SP

Type: DWORD

Data: 1