.NET Problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I just installed the newest version of .NET. Now when I go to the Administrative Tools and double click on the Microsoft .NET Framework 1.1 Configuration option, it comes up with this message:

Snap-in failed to initialize.
Name:.NET Framework 1.1 Configuration
CLSID:{some guid}

Also if I try to open the Microsoft .NET Framework 1.1 Wizards option, it comes up with this message:

ConfigWizards.exe - Common Language Runtime Debugging Services
Application has generated an exception that could not be handled.
Process id=0xcf4 (3316), Thread id=0x6dc (1756).
Click OK to terminate the application.
Click Cancel to debug the application.

If I hit Cancel I get this:

ConfigWizards.exe - No debugger found.
Registered JIT debugger is not available. An attempt to launch a JIT debugger with the following command resulted in an error code of 0x2(2). Please check computer settings.
cordbg.exe !a 0xcf4

I get almost exactly the same thing when I try to open Web Matrix.

If have unintalled and reinstalled .NET several times, making sure that my antivirus software was turned off. Anybody have any clue what is going on here?
 
I have exactly the same problem on two different machines, both running OS Win2K SP4. A 3rd running under WinXP home work fine. Any luck wih your problem?

Launch Error:

ConfigWizards.exe - Common Language Runtime Debugging Services

Application has generated an exception that could not be handled.
Process id=0x9a0(2464), Thread id=0x760(1888)

Click OK to terminate the application
Click CANCEL to debug the application

Clicked Cancel
No debugger found
Registered JIT debugger is not available. An attempt to launch a JIT debugger
with the following command resulted in an error code 0x2(2)
Please check computer settings
cordbg.exe !a0x8f4

Click on Retry to have the process wait while attaching a debugger manually.

Click on Cancel to abort the JIT debug request.

**********************************************************************
Sent via Fuzzy Software @ http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...
 
Fixed

I'm not sure what went wrong. A previous installation got mixed up with the new setup stuff, causing the program to lose grip on one of the assemblies.

Manually removing old assemblies and running the setup again solved my problem

I guess that when you get a process/thread error message, you should give a better look at the assemblies you need to deploy with your application

Jeroen.
 
Back
Top