.Net Framework Cleanup Tool, Решение проблем с установкой Опции

[Decker]

Иногда бывают варианты, когда .NET Framework установился некорректно, или невозможно установить / удалить его из-за ошибок в реестре, службе Windows Installer и еще не бог весть по каким причинам. Для решения этой проблемы незаменима утилита CleanUp Tool:

 dotnetfx_cleanup_tool.zip ( 222,38 килобайт ) Кол-во скачиваний: 1060

 dotnetfx_cleanup_tool_2_.zip ( 250,68 килобайт ) Кол-во скачиваний: 1288


p.s. Одна из выложенных версий поддерживает .NET Framework до 2.0, вторая до 3.5 SP1.

[Decker]

© http://blogs.msdn.com/astebner/archive/200...-2-0-setup.aspx

How to fix error code 25015 with access denied message during .NET Framework 2.0 setup

Recently, I saw a post on the MSDN .NET Framework Setup Forum indicating that a customer was having trouble getting the .NET Framework 3.0 to install on his system.

How to diagnose this error

The error log for the .NET Framework 3.0 setup (%temp%\dd_dotnetfx3error.txt) showed the following information:

[11/10/06,11:30:12] Microsoft .NET Framework 2.0: [2] Error: Installation failed for component Microsoft .NET Framework 2.0. MSI returned error code 1603
[11/10/06,11:30:36] WapUI: [2] DepCheck indicates Microsoft .NET Framework 2.0 is not installed.
[11/10/06,11:30:37] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0 was not attempted to be installed.

Based on this information, I determined that the .NET Framework 2.0 setup was failing. Then, I used the list of .NET Framework 3.0 setup log files to request additional information from the customer - specifically, the log file named %temp%\dd_netfx_retMSI*.txt.

When the customer sent me this log file, I found the following error that was causing the .NET Framework 2.0 setup to fail:

Error 25015.Failed to install assembly 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.VisualBasic.Vsa.dll' because of system error: The process cannot access the file because it is being used by another process.

In addition, the customer sent me a log file created by Filemon that indicated that setup failed when attempting to open this file with an access denied error.

How to workaround this error

Based on the above information, I made an educated guess that there was something wrong with the folder and file permissions on the customer's system. Fortunately, he was able to use the following steps to resolve this issue and successfully install the .NET Framework 3.0:
Use the SubInAcl tool described at http://blogs.msdn.com/astebner/archive/200.../04/739820.aspx to make sure that the Administrators group and the SYSTEM account both have permissions to folders under %windir% and registry hives under HKLM
Run the cleanup tool described at http://blogs.msdn.com/astebner/archive/200.../30/611355.aspx to make sure any remnants of the .NET Framework 2.0 have been removed from the system
Try again to install the .NET Framework 2.0 (or in this case, try again to install the .NET Framework 3.0, which will try to install the .NET Framework 2.0 behind the scenes)

Important caveats about error code 25015

Please note - error code 25015 during .NET Framework 2.0 setup is a catch-all for many types of errors. Therefore, the solution described in this post will likely only work if you see error code 25015 and the system error message states that the file is being used by another process and/or access is denied. Not all instances of the 25015 error code will be resolvable with these steps.

In coding terms, error code 25015 is the else block at the end of a big if statement. As a result, it ends up being the error code displayed after .NET Framework 2.0 setup verifies that the error is not caused by any other known fusion return code (which are defined in the file corerror.h that ships in the .NET Framework 2.0 SDK).

The customer who encountered this problem also posted this item on his blog describing this troubleshooting experience in case you are interested in reading that as well. Hopefully this will be useful if you run into this type of error while installing the .NET Framework 2.0 on your system.
Published Wednesday, November 15, 2006 5:34 PM by astebner
Filed under: Setup Issues, Visual Studio and .NET Framework

[Decker]

© http://blogs.msdn.com/astebner/archive/200.../04/739820.aspx

Solving setup errors by using the SubInACL tool to repair file and registry permissions

A while back, I wrote a blog post about a .NET Framework 2.0 beta 2 installation problem that was caused by incorrect access control list (ACL) permissions on some registry hives. In that post, I described how to use a tool in the Windows Resource Kit named SubInACL to reset file and registry ACLs to help solve this problem.

Ever since I wrote that post, I have run into installation errors for several other products that have been solved by using the SubInACL tool. Therefore, I wanted to write a standalone set of instructions for how and when to use the SubInACL tool because the previous blog post is specific to the .NET Framework 2.0 setup and does not always appear in search results when people run into this kind of a problem and search the Internet for assistance.

How to download and run SubInACL

Here are some steps that can be used to download and run the SubInACL tool to repair file and registry permissions that are often needed to successfully install programs on Windows, particularly for MSI-based (Windows Installer) setups:
Download the SubInACL tool and install it. By default it will install to c:\Program Files\Windows Resource Kits\Tools
If you are running Windows Vista, click on the Start menu, choose All Programs, then Accessories, then right-click on the item named Command Prompt and choose Run as administrator
If you are running an OS other than Windows Vista, go to the Start menu, choose Run, type cmd and click OK
In the cmd prompt, type notepad reset.cmd and click yes to open Notepad.exe and create a new text file named reset.cmd
Copy and paste the following contents into reset.cmd (or download it from this location on my file server and rename it from reset.cmd.txt to reset.cmd):

Код

cd /d "%programfiles%\Windows Resource Kits\Tools"

subinacl /subkeyreg HKEY_CURRENT_USER /grant=administrators=f /grant=system=f /grant=restricted=r /grant=YOURUSERNAME=f /setowner=administrators > %temp%\subinacl_output.txt
subinacl /keyreg HKEY_CURRENT_USER /grant=administrators=f /grant=system=f /grant=restricted=r /grant=YOURUSERNAME=f /setowner=administrators >> %temp%\subinacl_output.txt

subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=administrators=f /grant=system=f /grant=users=r /grant=everyone=r /grant=restricted=r /setowner=administrators >> %temp%\subinacl_output.txt
subinacl /keyreg HKEY_LOCAL_MACHINE /grant=administrators=f /grant=system=f /grant=users=r /grant=everyone=r /grant=restricted=r /setowner=administrators >> %temp%\subinacl_output.txt

subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=administrators=f /grant=system=f /grant=users=r /setowner=administrators >> %temp%\subinacl_output.txt
subinacl /keyreg HKEY_CLASSES_ROOT /grant=administrators=f /grant=system=f /grant=users=r /setowner=administrators >> %temp%\subinacl_output.txt


subinacl /subdirectories %programfiles%\ /grant=administrators=f /grant=system=f /grant=users=e >> %temp%\subinacl_output.txt

subinacl /subdirectories %windir%\ /grant=administrators=f /grant=system=f /grant=users=e >> %temp%\subinacl_output.txt

Change the values named YOURUSERNAME to be the Windows user account that you are logged in with.

Note: The YOURUSERNAME value should match the name of your user folder at c:\Documents and Settings (or c:\users on Windows Vista and higher). You can also find the value to use for YOURUSERNAME by launching Task Manager and looking at the user name listed in the User Name column of the Processes tab.

Save and close reset.cmd.
In the cmd prompt, type reset.cmd and press enter to run the SubInACL tool. This tool will take several minutes to run, and it requires that the user account you are using has administrator privileges on the system. This is why it is necessary to run it from an elevated cmd prompt on Windows Vista. Step 2 above can be used to start an elevated cmd prompt on Windows Vista.
After reset.cmd completes, try to install the product that previously failed to install correctly on your system.

Note: There are a couple of scenarios where installing or running SubInAcl can fail. For example, some non-English versions of Windows have the name of the Administrators group translated to another language, and the command lines listed above will fail in that case. I have posted workarounds for the issues that I know of in this separate blog post.

Also note: Running the above command lines will cause SubInAcl to create a log file named %temp%\subinacl_output.txt. If you see any errors reported in the cmd prompt after running SubInAcl, you can look in this log file for more detailed information about what file(s), folder(s) or registry value(s) are causing the errors. To open this log file, you can click on the Start menu, choose Run, type notepad %temp%\subinacl_output.txt and click OK.

When looking at this log file, you may see some errors reported with error code 5. That error code means Access Denied, and it is typically caused by Windows or some other program running on your system that is holding files, folders or registry values in use so that SubInAcl is unable to update the permissions for them. Most of the time, that type of error in the SubInAcl output can be safely ignored, but you may need to try to reboot and then manually fix the permissions for these files, folders or registry keys as a workaround.

When is SubInACL useful

I have found that the SubInACL tool is most useful when a setup package fails with error code 5 or 0x5 or 0x80070005. All of these error codes mean Access Denied, and this type of error code is often caused by missing ACLs for the Administrators group or the built-in System account. The Windows Installer service runs with System account permissions in most cases. If the System account does not have sufficient permissions to access the file system or parts of the registry, an MSI-based setup package will fail with an Access Denied error.

SubInACL can also help resolve Internet Explorer script errors caused by incorrect access control permissions for specific user accounts on the system.

Example of a setup failure that was fixed by SubInACL

A customer contacted me with a problem installing Visual Studio 2005. I looked at the main Visual Studio log file located at %temp%\dd_vsinstall80.txt, and I found that Windows Installer 3.1 setup was failing. Then, I looked at the Windows Installer 3.1 setup log file located at %windir%\KB893803v2.log. It showed the following error:

30.844: DoRegistryUpdates:UpdSpInstallFromInfSection Failed for MSI.Reg.Install: 0x5
30.844: DoInstallation:DoRegistryUpdates failed
30.875: Access is denied.

I had the customer run the above steps to use the SubInACL tool to update the file and registry ACLs on their system, and then they were able to install Windows Installer 3.1 and Visual Studio 2005 with no further problems.

[Decker]

 subinacl.7z ( 129,53 килобайт ) Кол-во скачиваний: 192


Ну и собственно "история" в тему:

Разговор на работе на кухне (о .NET):
- Первый фреймворк, потом второй. Третий, четвертый, пятый... А там, глядишь, и пенсия...

[Ramzes]

 subinacl.7z ( 129,53 килобайт ) Кол-во скачиваний: 192

А это для чего?

[Decker]

А это для чего?

Для установки разрешений / прав доступа на файлы и ветки реестра.