FieldDoc Posted May 21, 2003 Posted May 21, 2003 I loaded up Visual Basic.NET 2002 Standard edition today to carry on writing a program i'm doing at the moment. However, whilst the project was loading a message box popped up saying: Fatal Execution Engine Error (0x7924c900) I can only click OK. When I do so, another box pops up saying: Just in Time Debugging, and gives me a list of debuggers. As I have no idea what these do, I click that I don't want to debug and then VB exits. I am not only unable to load this project, I cannot load ANY projects, nor create any new projects as this error just pops up! The only thing that I have done recently is to install XP Service Pack 1 and .NET framework SP2. I'm guessing it has something to do with this but it may be a coincidence. Can anybody help me please? Quote
Guest mutant Posted May 21, 2003 Posted May 21, 2003 My guess is that some files got corrupted. Did you try reinstalling VB.NET? Quote
FieldDoc Posted May 21, 2003 Author Posted May 21, 2003 I haven't tried reinstalling it.....but how could VB files have gotten corrupted? Could SP1 have done it? Quote
*Gurus* divil Posted May 22, 2003 *Gurus* Posted May 22, 2003 I wouldn't have thought so but then, anything is possible. When I installed .NET 1.1 I lost all the documentation support in VS.NET 2002 and the .NET 1.0 SDK. These things happen. I'd give reinstalling it a shot. Quote MVP, Visual Developer - .NET Now you see why evil will always triumph - because good is dumb. My free .NET Windows Forms Controls and Articles
Noodles Posted July 14, 2004 Posted July 14, 2004 having same problem... this is on a fresh install of vbnet the first time I tried to open one of my projects, it crapped out. I have tried a repair without success. I uninstalled and attempted a reinstall. It completes most of it and stumbles at end with "fatal execution engine error... Can anyone suggest a workaround? Quote
sjn78 Posted July 15, 2004 Posted July 15, 2004 See if you can open any files in notepad and then start you project again from scatch. Copy and paste!!! Thats what I had to do. Quote
Wile Posted July 15, 2004 Posted July 15, 2004 Maybe this article helps? It also describes problems with Visual Studio .NET. Could be that your scripting engine somehow got corrupted. http://support.microsoft.com/default.aspx?scid=kb;en-us;323885 Quote Nothing is as illusive as 'the last bug'.
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.