Aaron Ruckman's Web Log : 3.5

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.0 or 3.5 installation will fail if the Print Spooler is not running on Windows XP or Windows Server 2003

aaronru — Thu, 20 Dec 2007 03:32:00 GMT

One of the .NET Framework 3.0 or 3.5 prerequisite packages requires that the Print Spooler service is running in the "Started" State. If the Print Spooler Service is not running, the .NET Framework 3.0 or 3.5 installation will fail.

To resolve this issue

Start the Print Spooler service before you install the .NET Framework. To do this:

1.	Click Start, point to Settings, click Control Panel, and then double-click Administrative Tools.
2.	Double-click Services, click to select Services (Local), right-click Print Spooler, and then click Properties.
3.	Click Start, and then click OK.

.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.

What to do when you go to post a setup and deployment issue on the MSDN forums?

aaronru — Tue, 11 Dec 2007 08:33:00 GMT

Step 1. It would be super helpful if you could provide the following information at the beginning of your post:

Version of .NET Framework you are trying to install.
Where did you get it (web page, path, application that redistributed the framework)
Is this a pre-release, CTP or beta version? Which? (Beta#, CTP (Month Year), RC, etc)
What .NET Framework Patches do you currently have installed?

Step 1. Follow Aaron Stebner's blog: http://blogs.msdn.com/astebner/archive/2007/08/01/4172276.aspx

I use http://home.services.spaces.live.com/ to post my logs, applications, etc. It is free and easy to use.
I've seen others use: http://www.file-upload.net/

Step 2. If this is a .NET Framework 3.5 install on Vista then you should run the following tool and post the output of the command: http://blogs.msdn.com/aaronru/archive/2007/11/29/net-framework-3-5-installation-validation-tool.aspx

Step 3. If this is a .NET Framework 3.5 isntall on Vista RTM then you should additionally try the following:

Run the following from an elevated command prompt

1. Winmgmt /verifyrepository

2. If the repository is reported as INCONSISTENT, run “Winmgmt /resetrepository” (if it fails because of service dependency, run “net stop winmgmt” and try again). If the repository is consistent, skip this step.

3. Do “mofcomp C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet.mof” to compile the failed mof.

If you feel the need to completely remove the .NET Framework and Visual Studio from your machines then you should follow the blog: http://blogs.msdn.com/aaronru/archive/2007/12/10/uninstalling-the-visual-studio-2008-rtm-or-rc.aspx

Thanks for taking the time to enhance our product.

.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

.NET Framework Error: 6015 - EFS is disabled

aaronru — Tue, 14 Aug 2007 17:32:00 GMT

If you are installing the .NET Framework 3.5 Beta2 on Vista and you get an error message like:

Installer encountered an error: 0x8007177f. This machine is disabled for file encryption"

Then what has happened is that your Domain administrator has disabled per policy the ability to have file encryption.

The following site explains how to correct this issue.

http://support.microsoft.com/kb/933595

Possible issue using ASP.NET controls in VS 2008 beta 2

aaronru — Tue, 07 Aug 2007 19:51:00 GMT

Description of this issue

Since Visual Studio 2008 beta 2 and the .NET Framework 3.5 beta 2 were released, we have heard of a few issues related to using ASP.NET controls in the VS IDE after installing beta 2. The issues we have seen so far include the following:

ASP.NET controls do not show up in the Visual Studio 2008 beta 2 toolbox
ASP.NET tag IntelliSense and schema validation is broken in HTML source view in the VS IDE

In the cases we've seen so far, the systems are running Windows Vista, and the file version of %windir%\Microsoft.NET\Framework\v2.0.50727\system.web.dll is less than the official beta 2 version of 2.0.50727.1378.

How to workaround this issue

If you run into an issue like this, you can uninstall .NET Framework 2.0 hotfixes and then re-install the .NET Framework 3.5 as a workaround.

There are some detailed instructions that explain how to do this at this location, including a list of the exact hotfixes that need to be uninstalled to resolve this issue.

You do not need to re-install the previous hotfixes after working around this issue. The .NET Framework 2.0 SP1 and 3.0 SP1 hotfix packages that are installed as prerequisites for the .NET Framework 3.5 beta 2 already include all of the fixes that were previously released as separate Windows Vista hotfixes for the .NET Framework 2.0/3.0.

Root cause of this issue

We have found a problem with how some Windows Vista-specific hotfixes for the .NET Framework 2.0 have been packaged in the past that can cause an incorrect version of files like system.web.dll to appear on the system. This means that if you have some specific .NET Framework 2.0 hotfixes installed on your Windows Vista system, you might encounter this type of file version problem and therefore also run into some issues when trying to use VS 2008 beta 2. Windows Vista is built from components, and these components have their own version information that is used to determine which files will be present on the OS. The versions of the files contained in each of the components does not have to match the component version, and that can lead to newer versions of components having older versions of files in some cases such as this.