Troubleshooting MVC 3 Installation Errors on ASP.NET: A Comprehensive Guide

Table of Contents

This article provides detailed guidance to assist you in resolving a critical issue that can arise during the installation of Microsoft ASP.NET MVC 3 or ASP.NET Web Pages. Specifically, it addresses a fatal error that can halt the installation process, preventing successful setup of these essential web development tools. Understanding the root causes and applying the appropriate solutions are crucial for developers aiming to utilize ASP.NET MVC 3 or ASP.NET Web Pages effectively. This guide aims to equip you with the knowledge and steps necessary to overcome these installation hurdles.

Symptoms¶

When attempting to install ASP.NET MVC 3 or ASP.NET Web Pages, you might encounter a fatal error message. This error typically manifests as a dialog box during the installation process, indicating a failure with a specific error code. The error message will be similar to the following:

Installation failed with error code (0x80070643)

To gain a deeper understanding of the underlying cause of this installation failure, it’s essential to examine the installation logs. On the final screen of the ASP.NET Web Pages or ASP.NET MVC 3 installation process, you will find a link to the log file. By clicking this link, you can access detailed logs that pinpoint the exact error that led to the installation failure. Within these logs, you will often find an error code that further directs you to the MSI log, located in the same folder as the primary installation log. The MSI log is particularly valuable as it often contains a more specific error message, such as the example below:

Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: WebConfigCA_Remove, location: C:\Program Files (x86)\Microsoft ASP.NET\ASP.NET Web Pages\v1.0\WebConfig\WebConfigCA.exe, command: -u

This Error 1721, specifically mentioning WebConfigCA_Remove, suggests an issue during the configuration of web settings, often pointing towards problems with accessing or modifying the web.config file. Recognizing these symptoms and understanding how to access the installation logs are the first critical steps in diagnosing and resolving ASP.NET MVC 3 or ASP.NET Web Pages installation errors.

Cause¶

Several underlying conditions can lead to the installation error described above. Identifying the precise cause is crucial for applying the correct resolution. Here are some of the most common reasons for this error:

• Pre-release Version Conflict: Having a pre-release version of ASP.NET Web Pages or ASP.NET MVC 3 installed prior to installing Visual Studio 2010 SP1 can create conflicts. When attempting to install the released versions of these components after installing the service pack, the system might encounter inconsistencies, leading to installation failures. The remnants of the pre-release version can interfere with the clean installation of the final release.

• Restricted Root Web.config Sections: The root web.config file, a critical configuration file for ASP.NET applications, can sometimes have sections marked with allowOverride="false". This setting restricts the installer’s ability to modify these sections during the installation process. If the ASP.NET MVC 3 or Web Pages installer needs to make changes to these protected sections, the installation will fail due to insufficient permissions to override the existing configuration. The root configuration file is typically located in the directory %system%\\Microsoft.NET\\Framework\\<version>\\Config.

• Web.config File Lock: If another process is actively using or has locked the root web.config file, the installer will be unable to write to it. This locking mechanism prevents simultaneous modifications to the configuration file, which can lead to data corruption or instability. Processes like IIS, other ASP.NET applications, or even background services could potentially lock the web.config file.

• Read-Only Root Web.config: If the root web.config file’s attributes are set to read-only, the installer will not be able to make the necessary modifications. The installer requires write access to update the configuration file with settings required for ASP.NET MVC 3 or Web Pages to function correctly. A read-only attribute effectively blocks the installer from completing its configuration steps, leading to installation failure.

Understanding these potential causes helps narrow down the troubleshooting process and allows for targeted solutions. By considering each of these scenarios, you can more effectively diagnose the specific reason behind your ASP.NET MVC 3 or ASP.NET Web Pages installation error.

Resolution¶

The appropriate solution to resolve the ASP.NET MVC 3 or ASP.NET Web Pages installation error depends heavily on identifying the root cause. Once you have determined the likely cause from the scenarios described above, you can apply the corresponding resolution steps.

If you suspect a conflict with a pre-release version of ASP.NET Web Pages or ASP.NET MVC, follow these steps:

1. Remove Trailing Backslashes from Registry Keys: Open the Registry Editor by typing regedit in the Run dialog (Windows Key + R) and navigating to the following registry keys. For each key listed below, locate the Path value and remove the trailing backslash (\) if present.

   • HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\ASP.NET\\4.0.30319.0\\Path
   • HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\ASP.NET\\4.0.30319.0\\Path

   Modifying these registry keys, specifically removing trailing backslashes from the path values, is a crucial step in resolving conflicts arising from pre-release versions. Incorrectly formatted paths in the registry can sometimes interfere with the proper detection and uninstallation of older software components.

2. Uninstall Old ASP.NET Web Pages Version: Go to the Control Panel, then “Programs and Features” (or “Add or Remove Programs” depending on your Windows version). Locate and uninstall any existing installations of ASP.NET Web Pages. Ensure you remove all pre-release or older versions that might be present on your system. A clean removal is essential to prevent conflicts with the new installation.

3. Restore Trailing Backslashes to Registry Keys: After uninstalling the old versions, revisit the same registry keys modified in step 1 and add back the trailing backslash (\) to the Path values. Restoring the backslashes ensures that the registry paths are correctly formatted for other system processes and applications that might rely on them.

4. Reinstall ASP.NET Web Pages or ASP.NET MVC 3: Attempt to install ASP.NET Web Pages or ASP.NET MVC 3 again. With the potential pre-release conflicts resolved and registry paths corrected, the installation process should now proceed without the fatal error.

If the issue is not related to pre-release versions, consider these general troubleshooting steps:

• Check Root Web.config Permissions: Verify the permissions of the root web.config file. Ensure that the user account performing the installation has write access to this file. You can check and modify permissions by right-clicking the web.config file, selecting “Properties,” and then navigating to the “Security” tab.

• Unlock Root Web.config: If you suspect that another process is locking the web.config file, try to identify and terminate any processes that might be accessing it. Restarting IIS (iisreset in Command Prompt as administrator) can often release locks held by web application processes. Additionally, check for any other applications that might be interacting with the configuration file.

• Remove Read-Only Attribute: Ensure that the root web.config file is not set to read-only. Right-click the file, select “Properties,” and in the “General” tab, uncheck the “Read-only” attribute if it is selected. Apply the changes and attempt the installation again.

• Temporarily Disable Antivirus/Security Software: In some cases, overly aggressive antivirus or security software might interfere with the installation process by blocking necessary file modifications or process executions. Temporarily disabling such software (while being mindful of security risks and re-enabling it immediately after installation) might resolve the issue.

By systematically working through these resolution steps, based on the possible causes, you should be able to overcome the ASP.NET MVC 3 or ASP.NET Web Pages installation error and successfully install these components. Remember to carefully examine the installation logs for specific error details, as they often provide valuable clues for pinpointing the exact cause and the most effective resolution.

---

We encourage you to share your experiences and questions in the comments below. Have you encountered similar installation errors? What solutions worked for you? Your insights can be valuable to other developers facing these challenges.