Welcome to MSDN Blogs Sign in | Join | Help

Unified .NET Framework Troubleshooting Guide

Details about the .NET Framework 2.0 setup packaging

Error codes that can appear during .NET Framework setup

How to repair a broken version of the .NET Framework that ships with the OS

How to resolve some specific types of .NET Framework setup failure

How to remove broken .NET Framework builds

.NET Framework service pack install issues

Where to find log files

Useful tools

Other references

 

Published Monday, August 22, 2005 10:40 PM by astebner

Comments

Thursday, March 02, 2006 7:55 AM by gody

# re: Unified .NET Framework Troubleshooting Guide

how come there is no solution to the error messages esp the failure to register assemblies.25015 error code .
i need help please
Thursday, March 02, 2006 6:49 PM by astebner

# re: Unified .NET Framework Troubleshooting Guide

Hi Gody - I have not posted a blog item about error code 25015 yet because we have not narrowed down any definitive root causes of that error yet.

Can you please try to use the manual removal steps for the .NET Framework 2.0 that are listed at http://blogs.msdn.com/astebner/archive/2005/04/16/408856.aspx and then try to re-install the .NET Framework 2.0 and see if that resolves this issue?  If that doesn't help, I would suggest contacting Microsoft technical support (you are entitled to a free support call for .NET Framework setup issues).  I'm sorry I'm not able to be more helpful here.
Tuesday, May 23, 2006 1:05 PM by megawatt

# re: Unified .NET Framework Troubleshooting Guide

Hi Aaron!

I work at Intuit where I support Quicken Medical Expense Manager, which installs on top of .NET Framework 1.1. I have been working with your .NET Framework team in Bangalor, specifically with Arun Ramalingam and Aditya Hari (mostly) and they have been UNBELIEVABLY helpful in helping me to get my customers fixed when we discover that their .NET Framework is broken. They shared your cleanup tool with me and it has cut my support call time from 2 hrs to 20 min. Many KUDOS to you for developing it! Everyone that I have spoken with at Microsoft has been so kind and helpful and I intend to write a note to Bill Gates to let him know what a great team of folks that he has!

I have one last question for you, can you explain to me, in laymen's terms, how and why the .NET Framework can break? I just want to understand a bit more so that I can attempt to explain it to my customers when they ask.

Thanks so much!
Meg A. Watt
Quicken Medical Expense Manager
Intuit, Inc.
Thursday, May 25, 2006 10:08 PM by astebner

# re: Unified .NET Framework Troubleshooting Guide

Hi Megawatt - Thank you very much for this feedback on Arun and Aditya as well as the .NET Framework cleanup tools.  I have passed this feedback on to the technical support managers that oversee the .NET Framework products as well.

Your question about how/why the .NET Framework can break is not a simple one to answer.  Like any reasonably complex piece of software, there are a lot of possible points of failure.  The .NET Framework relies upon the presence of many files and registry keys, so if any of them are missing, have bad data, have incorrect versions or are corrupt, it can lead to unpredictable results.

Since the .NET Framework is a runtime that other applications use, when it is broken, it can lead to unpredictable results and crashes in those applications.

The most common cause of fragility in the .NET Framework that I've seen in my past experience is related to the file %windir%\system32\mscoree.dll.  That file is a shim that is shared by all versions of the .NET Framework, and it enables side-by-side functionality by determining which version of the .NET Framework to use when running any given .NET application.  If that file is corrupt or somehow gets downgraded, it can cause applications to fail to load.  As a general rule of thumb, that file should be versioned the same as the highest version of the .NET Framework you have installed.  For example, if you have version 1.0 and 1.1 of the .NET Framework on your system, that file should be versioned 1.1.4322.

Hope this helps.  If you have any more specific questions that I can help you answer for your customers, or if you run into any further problems, please don't hesitate to contact me.
Friday, July 28, 2006 10:09 PM by geek4jesus.com » Fixing problems with .NET

# geek4jesus.com » Fixing problems with .NET

PingBack from http://geek4jesus.com/wp/?p=4
Wednesday, August 30, 2006 9:04 PM by gormboy

# re: Unified .NET Framework Troubleshooting Guide

Hello, Aaron;

First, thanks for the wealth of information you've poured out here.  However, I've spent the better part of a day trying to reinstall .NET Framework 2.0, and I'm just stumped!  First, I tried it through Windows Update, but that gave an error code (0x643).  Then, poking around here, I learned about dotnetfx.exe, downloaded it, and attempted to install it.  However, each attempt ended with the message:

Error 25015.Failed to install assembly
'C:\WINNT\Microsoft.NET\Framework\v2.0.50727\System.dll' because of system
error:
The system cannot find the file specified

Where is system.dll that the system can't find it?  Should it be placed in the v2.0.50727 folder as part of installation?  A search of my system shows there is no system.dll.

I've already used the clean-tool and performed the manual clean up.

I realize this may not be the appropriate forum, but I'm desperate!  Any help would be appreciated.

Thanks!

Dennis
Saturday, September 02, 2006 4:10 PM by astebner

# re: Unified .NET Framework Troubleshooting Guide

Hi Gormboy - Just to confirm, you've already tried to run the tool described at http://blogs.msdn.com/astebner/archive/2006/05/30/611355.aspx and that didn't help, correct?  If not can you please try that.  If so, can you please try to us the SubInAcl tool described at http://blogs.msdn.com/astebner/archive/2005/08/09/449720.aspx to try to fix any permission issues that might exist on your system?

If neither of those help, your best bet is to contact Microsoft technical support for further troubleshooting assistance.  There is contact information at http://support.microsoft.com/?LN=en-us&scid=gp%3Ben-us%3Bofferprophone&x=15&y=12.  That site says that you have to pay, but for setup-related problems such as this, there is not a support charge.
Saturday, June 16, 2007 10:29 AM by Aaron Stebner's WebLog : What to do if other .NET Framework setup troubleshooting steps do not help

# Aaron Stebner's WebLog : What to do if other .NET Framework setup troubleshooting steps do not help

PingBack from http://blogs.msdn.com/astebner/archive/2005/10/11/479928.aspx

Tuesday, June 19, 2007 6:28 PM by soniavdas

# .NET 1.1 Install issues on Vista

I am getting "1603:error installing .Net framework" on installing .NET 1.1 on Vista. Can you please help?

Wednesday, June 20, 2007 4:41 PM by astebner

# re: Unified .NET Framework Troubleshooting Guide

Hi Soniavdas - Error code 1603 is a generic failure code for an installer.  You will need to gather a verbose log file from the failing setup to be able to narrow this down further.  You can use instructions like the ones at http://blogs.msdn.com/astebner/archive/2005/03/29/help-me-help-you-if-you-have-setup-bugs.aspx to do this.  If you can gather this log, zip and send it to me at Aaron.Stebner (at) microsoft (dot) com, I will try to take a look and see if I can figure out any possible causes of this issue on your system.

Friday, August 31, 2007 7:35 AM by jwraith

# re: Unified .NET Framework Troubleshooting Guide

Hey Aaron,

I'm trying to run the Setup Verification tool in silent mode and pipe it to text file, however all it seems to do is create a blank text document then do nothing.

A little help would be appreciated :)

Tuesday, September 04, 2007 8:09 PM by astebner

# re: Unified .NET Framework Troubleshooting Guide

Hi Jwraith - The verification tool is not a console application, so you cannot pipe output to a text file because there is no output available to pipe.  However, it creates a log file with the actions it performs and the results of the verification in the %temp% directory on the systems that it is run on.

Also, the tool supports a few command line switches that will allow you to run it in silent mode and control the exact location of the log file that gets created.  You can run the file vsverify.exe inside the self-extracting EXE for the setup verification tool with a /? switch to see the usage options.

When running in silent mode, the verification tool will also return exit codes indicating the results of the verification.  A return code of 0 means success, and a non-zero return code means that some phase of the verification failed.

Hopefully this will help in your scenario.  Please contact me directly using http://blogs.msdn.com/astebner/contact.aspx if you have more detailed questions about how to get this scenario working on your system.

Thursday, September 27, 2007 4:00 PM by Takuboku

# re: Unified .NET Framework Troubleshooting Guide

Hi,

I tried to install .Net 2.0 and SQL express. However, The install failed at checking the configuration."Setup has detected a problem with Microsoft .Net farmewrok installation & cannot proceed.  Microsoft .Net framewrok 2.0 is either not installed on this systems or is corrupt"

I installed .Net 2.0 successfully, "The message Ms .Net farmework 2.0 has been successfully installed."

I checked the installed the status of .Net 2.0 with verification tool. I got the below message.

Is it completed to install the .Net?

09/27/07 15:44:00 *********** Log info from SetupVerifier.exe ***********

09/27/07 15:44:00  

09/27/07 15:44:00 #################  SUMMARY  ##########################

09/27/07 15:44:00 Number of files with correct attributes = 496

09/27/07 15:44:00 Number of files installed but not supposed = 0

09/27/07 15:44:00 Number of files with incorrect version = 0

09/27/07 15:44:00 Number of files with incorrect language = 1

09/27/07 15:44:00 Number of files missing = 0

09/27/07 15:44:00 Number of file warnings = 2

09/27/07 15:44:00

09/27/07 15:44:00 Total files = 497

09/27/07 15:44:00 ######################################################

09/27/07 15:44:00  

09/27/07 15:44:00 ##################  ERRORS  ##########################

09/27/07 15:44:00 Contents of FileLangProb.txt

09/27/07 15:44:00 CompID File Version Language Shared Permanent CRC Excluded

09/27/07 15:44:00

09/27/07 15:44:00 *** File with different language stamp (expected/actual) ***

09/27/07 15:44:00 {77B2DBF7-665A-432C-B1B4-ADD82744DE15} C:\Program Files\Internet Explorer\MUI\0409\mscorier.dll 2.0.50727.42 ENU true false - false

09/27/07 15:44:00 {77B2DBF7-665A-432C-B1B4-ADD82744DE15} C:\Program Files\Internet Explorer\MUI\0409\mscorier.dll 2.0.50727.42 JPN true false 0x18b18a53 false

09/27/07 15:44:00

09/27/07 15:44:00  

09/27/07 15:44:00 Contents of FileMissing.txt

09/27/07 15:44:00 CompID File Version Language Shared Permanent CRC Excluded

09/27/07 15:44:00

09/27/07 15:44:00  

09/27/07 15:44:00 Contents of FileVerProb.txt

09/27/07 15:44:00 CompID File Version Language Shared Permanent CRC Excluded

09/27/07 15:44:00

09/27/07 15:44:00 ######################################################

09/27/07 15:44:00  

09/27/07 15:44:00 #################  WARNINGS  #########################

09/27/07 15:44:00 CompID File Version Language Shared Permanent CRC Excluded

09/27/07 15:44:00

09/27/07 15:44:00 *** File with greater version (expected/actual) ***

09/27/07 15:44:00 {0E69362B-643A-4B36-A50E-55E1888B307E} C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.EnterpriseServices.tlb 2.0.50727.42 ENU true true - false

09/27/07 15:44:00 {0E69362B-643A-4B36-A50E-55E1888B307E} C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.EnterpriseServices.tlb 2.0.50727.832 ENU true true 0x9341ec8b false

09/27/07 15:44:00

09/27/07 15:44:00 *** File with greater version (expected/actual) ***

09/27/07 15:44:00 {1A6D8713-9116-44AE-BA60-4CF0E8C1D58B} C:\Program Files\Common Files\Microsoft Shared\DW\DW20.EXE 11.0.6555.0 - false false - false

09/27/07 15:44:00 {1A6D8713-9116-44AE-BA60-4CF0E8C1D58B} C:\Program Files\Common Files\Microsoft Shared\DW\DW20.EXE 11.0.6560.0 - false false 0x5b5a178d false

09/27/07 15:44:00

09/27/07 15:44:00 ######################################################

09/27/07 15:44:00  

09/27/07 15:44:00 ******** End of log info from SetupVerifier.exe *******

09/27/07 15:44:00  

09/27/07 15:44:00 ****ERROR**** VerifySetup returned false for parameters v20_urt_std_x86_ixp.sem and E_FILES

09/27/07 15:44:00 Verification thread is returning 100

Thursday, September 27, 2007 5:44 PM by astebner

# re: Unified .NET Framework Troubleshooting Guide

Hi Takuboku - From what I can tell in the verification results, the .NET Framework 2.0 should be correctly installed on your system.  The language mismatch for that one file and the higher versions for those other 2 files are OK to ignore in this case.

If you are still getting a .NET Framework 2.0 installation error from SQL Server setup, there may be something strange in the logic that SQL is using to detect the .NET Framework.  If that is the case, I'd suggest posting a question on the SQL setup forum at http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=95&SiteID=1 and hopefully someone there will be able to suggest a fix for you.

Thursday, November 29, 2007 9:27 AM by Fabien G.

# Visual Studio 2005 and .NET

Hi,

I have installed Visual Studio 2005, with the update available from the microsoft web site. And I have always the same issue (with the C++ IDE):

when I try to get the property dialog box of a project, I always have approximatively the message:

"Impossible to create the PropertyGrid component. Check that the CLR and the .NET framework are correctly installed."

I have installed-uninstalled several time the software (Visual Studio, .NET), and nothing changes. I have use the cleanup software dotnetfx_cleanup_tool.zip, before the last install.

In the registry, I have the key associated with the .Net framework 2.0.

When I launch netfx_setupverifier.exe, I have the same log file as above.

I have spend a lot of time on this issue, and I don't see what I can check now.

Is the issue due to the .Net framework or is it due to Visual Studio?

What can I check or do to solve that?

Thanks a lot for your help.

Thursday, November 29, 2007 1:06 PM by astebner

# re: Unified .NET Framework Troubleshooting Guide

Hi Fabien G - The only instances of this issue that I have heard of in the past were caused by having leftover pieces of an old VS 2005 beta somewhere on the system.  In some of those cases, running the VS 2005 beta cleanup tool at http://astebner.sts.winisp.net/Tools/vs2005_beta_cleanup_tool.zip might help.

If that does not help on your system, then I'm not sure what other workarounds to suggest.  It might help to post a question on one of the MSDN forums (http://forums.microsoft.com) to see if someone there has any additional ideas.

I'm sorry I'm not able to be more helpful in this scenario.

Monday, December 03, 2007 4:53 AM by Fabien G.

# Visual Studio 2005 and .NET

Hi astebner,

thanks for your help, but the cleanup tool didn't solve the issue.

I feel that my computer is corrupted, but I don't know how to inspect it.

I asked a collegue to look at it, but we'll probably have to reinstall the computer if we don't find any other solution :(

Thanks

Tuesday, April 22, 2008 2:59 PM by Aaron Stebner's WebLog : Updated: what to do if other .NET Framework setup troubleshooting steps do not help

# Aaron Stebner's WebLog : Updated: what to do if other .NET Framework setup troubleshooting steps do not help

PingBack from http://blogs.msdn.com/astebner/archive/2008/03/07/8108332.aspx

Anonymous comments are disabled
 
Page view tracker