2. Known Issues
2.1 Installing
2.1.1 .NET Framework 2.0 SP2 installation may fail to upgrade .NET Framework 2.0 or 2.0 SP1
.NET Framework 2.0 SP2 installation may fail on a computer that has the .NET Framework 2.0 or 2.0 SP1 installed and is running Windows XP, Windows Server 2003, or Windows 2000.
The .NET Framework 2.0 SP2 Setup uninstalls earlier versions of the .NET Framework 2.0 and 2.0 SP1. When Windows Installer uninstalls previous versions, it uses the cached installation database. During the uninstall operation, if Windows Installer cannot find the installation packages for the earlier updates in its cache, or the original source location, the installation fails. If an incomplete rollback occurs, this failure to install may also cause applications that use the .NET Framework to fail.
This problem may occur for either of these reasons:
The Windows Installer cache is missing required files.
The Windows Installer cache has been changed. The cache is critical for repairing, for updating, and for uninstalling products. Therefore, do not remove or modify the contents of the cache. If you change the contents of the cache, you may be prompted for a source when you try to update or to repair Windows Installer-based products.
Sometimes a Windows Installer Patch (.msp) file that Windows Installer expects to find in the cache may not exist. The following are two common reasons why the .msp file may be missing:
- A tool that finds and deletes large files or rarely used files on the hard disk has been run.
- The owner of the %windir%\Installer directory is changed from SYSTEM or from Administrators.
If this issue occurs, the Windows Installer log for the failing installation will show something that resembles the following:
MSI (s) (D0:B0) [19:05:57:843]: Couldn't find local patch 'C:\WINDOWS\Installer\a4784a.msp'. Looking for it at its source.
MSI (s) (D0:B0) [19:05:57:843]: Resolving Patch source.
You can use the Microsoft .NET Framework Registration Correction Tool to resolve this issue when it occurs. The tool fixes this issue by deleting all hotfix or update registrations that are specific to this update so that maintenance installations do not try to load the specific .msp file.
You can also try to fix this issue by rebuilding the installer cache. You can typically find the Knowledge Base number for the hotfix or for the update in the lines that follow "Resolving Patch source," as shown in the following example:
MSI (s) (D0:B0) [19:05:57:859]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (D0:B0) [19:05:57:859]: Note: 1: 1706 2: -2147483647 3: NDP20-KB917283-X86.msp
To fix the Windows Installer Cache for this example, follow these steps:
1. Visit the following Microsoft Web site:
http://support.microsoft.com/kb/917283 (
http://support.microsoft.com/kb/917283). Note: You can replace the Knowledge Base article number in the URL with the Knowledge Base article number of the hotfix or the update for which you want to fix the Windows Installer cache.
2. Download the update.
3. Extract the .msp file in the hotfix or the update by using the /x command-line switch or the /extract command-line switch.
4. opy the extracted .msp file to the location for the missing file. In this example, the location is %windir%\Installer\a4784a.msp.
The hotfix registration or the update registration may be corrupted.
After a hotfix or an update is installed on a Windows Installer-based product, the hotfix registration or the update registration may become corrupted. This problem can occur because of third-party registry cleaner utilities that remove certain registry keys. These keys include the keys that are meant for internal use by Windows Installer. In this case, the "Resolving Patch source" message in the log reads as follows:
MSI (s) (CC:5C) [03:02:56:181]: Couldn't find local patch ''. Looking for it at its source.
MSI (s) (CC:5C) [03:02:56:181]: Resolving Patch source.
Note: The location of the hotfix or the update is missing in the log message because of the missing hotfix or upate registration information. In this case, a hotfix or an update is still registered to a product. However, location information for the hotfix or update is missing. Although the file may exist, Windows Installer does not know the path of the file that Windows Installer requires to load.
You can use the Microsoft .NET Framework Registration Correction Tool to resolve this issue when it occurs. The tool fixes this issue by deleting all hotfix or update registration that is specific to this service pack so that maintenance installations do not try to load the hotfix or the update package.
To resolve this issue:
If you cannot successfully install .NET Framework 2.0 SP2 and find the "Resolving Patch source" text in the installation log file as described in the "Cause" section, you can download the Microsoft .NET Framework Registration Correction Tool to resolve this issue.
Microsoft .NET Framework 2.0 Registration Correction Tool
The Microsoft .NET Framework Registration Correction Tool resolves both of the issues that the "Cause" section describes.
The following file is available for download on the Microsoft Download Center:
Download the Microsoft .NET Framework 2.0 Registration Correction Tool package now.
http://www.microsoft.com/downloads/d...9-96A323701260
The Microsoft Download Center has one version of the tool for each processor architecture that the .NET Framework 2.0 supports (x86, x64, and IA-64). Most customers run a 32-bit version of the operating system. Therefore, these customers should download and install the x86 version of the tool.
Administrators may also use this utility in scripts by passing either the /q command-line switch or the /quiet command-line switch. In this way, you can run the application in silent mode without using a user interface and without using block scripts.
The tool writes a running log under the %TEMP%\dd_clwireg.txt folder. You can view this log for more information about what the tool is doing.
Notes
- The Microsoft .NET Framework Registration Correction Tool is designed to be used with any current version of the .NET Framework.
- You must be an administrator to run this utility.
Първоначално написано от SoAfraid
Правила за публикуване
2001 - 2025 Всички права запазени.
Реклама |
Портфолио |
Контакти |
Условия за ползване |
Поверителност |
Карта на сайта
