Microsoft Knowledge Base Email Alertz

KBAlertz.com: You may receive an error message when you try to open a .vb file in Visual Studio 2005, in Visual Studio .NET 2003, or in Visual Studio .NET 2002

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **


Community Site



We Send hundreds of thousands of emails using ASP.NET Email


ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 919482 - Last Review: February 7, 2007 - Revision: 2.6

You may receive an error message when you try to open a .vb file in Visual Studio 2005, in Visual Studio .NET 2003, or in Visual Studio .NET 2002

On This Page

SYMPTOMS

When you try to open a .vb file in Microsoft Visual Studio 2005, in Microsoft Visual Studio .NET 2003, or in Microsoft Visual Studio .NET 2002, you may experience one of the following symptoms.

Visual Studio 2005

You receive the following error message:
Microsoft (R) Visual Basic Compiler has encountered a problem and needs to close. We are sorry for the inconvenience.

No information has been lost. Check the compiler output for possible ways to avoid this error.
If you click What data does this error report contain?, you receive the following Event information:

Error signature
AppName: devenv.exe AppVer: 8.0.50727.42 AppStamp:4333e699
ModName: msvb7.dll ModVer: 8.0.50727.42 ModStamp:4333e976
fDebug: 0 Offset: 00131828

Additionally, events that resemble the following are logged in the Application log:
Event message 1

Event Type: Information
Event Source: Microsoft (R) Visual Basic Compiler
Event Category: None
Event ID: 1001
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
Bucket 241946298, bucket table 1, faulting application devenv.exe, version 8.0.50727.42, stamp 4333e699, faulting module msvb7.dll, version 8.0.50727.42, stamp 4333e976, debug? 0, fault address 0x00131828.For more information, see Help and Support Center at http://support.microsoft.com.

Event message 2

Event Type: Error
Event Source: Microsoft (R) Visual Basic Compiler
Event Category: None
Event ID: 1000
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
Faulting application devenv.exe, version 8.0.50727.42, stamp 4333e699, faulting module msvb7.dll, version 8.0.50727.42, stamp 4333e976, debug? 0, fault address 0x00131828.For more information, see Help and Support Center at http://support.microsoft.com.

Visual Studio .NET 2003 or Visual Studio .NET 2002

You receive the following error message:
Microsoft Developement Environment has encountered a problem and needs to close. We are sorry of the inconvenience.
If you click Click here, you receive the following Event information:

Error details
An unhandled exception has been caught by the VSW exception filter.

Error signature
AppName: devenv.exe AppVer: 7.10.3077.0 ModName: kernel32.dll
ModVer: 5.1.2600.2180 Offset: 0001eb33

Additionally, an event that resembles the following may be logged in the Application log:

Event Type: Error
Event Source: Microsoft Development Environment
Event Category: None
Event ID: 1000
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
Faulting application devenv.exe, version 7.10.3077.0, faulting module kernel32.dll, version 5.1.2600.2180, fault address 0x0001eb33.For more information, see Help and Support Center at http://support.microsoft.com.

CAUSE

This problem occurs because the Visual Basic runtime installation has become corrupted.

RESOLUTION

To resolve this problem, repair or reinstall Visual Studio. To do this, use one of the following methods, depending on the version of Visual Studio that you have installed.

Visual Studio 2005

  1. Insert the Visual Studio 2005 installation CD.
  2. Click Change or Remove Visual Studio 2005.
  3. Click Next, and then click Repair/Reinstall to start the installation.
  4. When the installation has completed, click Finish.

Visual Studio .NET 2003 or Visual Studio .NET 2002

  1. Insert the Visual Studio .NET 2003 or Visual Studio .NET 2002 installation CD.
  2. Click Visual Studio .NET.
  3. Click Repair/Reinstall to start the installation.
  4. When the installation has completed, click Finish.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

APPLIES TO
  • Microsoft Visual Studio 2005 Professional Edition
  • Microsoft Visual Studio 2005 Standard Edition
  • Microsoft Visual Basic 2005
  • Microsoft Visual Basic .NET 2003 Standard Edition
  • Microsoft Visual Basic .NET 2002 Standard Edition
  • Microsoft Visual Studio .NET 2003 Enterprise Architect
  • Microsoft Visual Studio .NET 2003 Enterprise Developer
  • Microsoft Visual Studio .NET 2003 Academic Edition
  • Microsoft Visual Studio .NET 2003 Professional Edition
  • Microsoft Visual Studio .NET 2002 Professional Edition
  • Microsoft Visual Studio .NET 2002 Enterprise Architect
  • Microsoft Visual Studio .NET 2002 Enterprise Developer
  • Microsoft Visual Studio .NET 2002 Academic Edition
Keywords: 
kbtshoot kberrmsg kbbug kbprb KB919482
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Anonymous User - k.kuroda NOSPAM-AT-NOSPAM comcast.net Report As Irrelevant  
Written: 9/14/2009 5:07 PM
Faulting application devenv.exe, version 9.0.21022.8, stamp 47317b3d, faulting module unknown, version 0.0.0.0, stamp 00000000, debug? 0, fault address 0x000002b7. Bucket 1461895058, bucket table 1, faulting application devenv.exe, version 9.0.21022.8, stamp 47317b3d, faulting module unknown, version 0.0.0.0, stamp 00000000, debug? 0, fault address 0x000002b7. here are the error messages I was receiving. Doing the above fixed my problem. Thanks!!

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please