Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / General / April 2004

Tip: Looking for answers? Try searching our database.

.NET Problem

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
mikemagnetic - 15 Mar 2004 22:36 GMT
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?
fuzzysoftware@ghq.net - 31 Mar 2004 21:39 GMT
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.
Jeroen - 10 Apr 2004 07:36 GMT
We are not alone!!

See
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.dotnet.fra
mework&mid=ae943614-f295-4b78-9d24-f091e3350ee


Here Tian gives some suggestions
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.dotnet.fra
mework&mid=b83657bc-b85c-49e4-b1e3-77e370b45d6


Hopefully it gets me out of here

Jeroen
jeroen - 14 Apr 2004 09:31 GMT
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

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.