BUG: You receive an "Unexpected exception occurred during upgrade engine operation" error message when you run the Visual Basic .NET or Visual Basic 2005 Upgrade Wizard (819350)
The information in this article applies to:
- Microsoft Visual Basic 2005
- Microsoft Visual Basic .NET (2003)
- Microsoft Visual Basic .NET (2002)
SYMPTOMSWhen you run the Microsoft Visual Basic .NET or Microsoft
Visual Basic 2005 Upgrade Wizard to upgrade your Microsoft Visual Basic 6.0
projects, you may receive the following error message: Unexpected exception occurred during upgrade engine
operation: Object is static; operation not allowed.
CAUSEYou can use double-byte character set (DBCS) characters to
name your Visual Basic 6.0 files and to name your Visual Basic 6.0 projects.
You can also use DBCS characters to name the folders that contain your Visual
Basic 6.0 files and to name the folders that contain your Visual Basic 6.0
projects. You can then run the Visual Basic .NET or Visual Basic 2005 Upgrade
Wizard to upgrade these projects.
You receive the error message that
is mentioned in the "Symptoms" section of this article if you use DBCS
characters with 0x5b or 0x5c trailing bytes to name your Visual Basic 6.0
files, to name your Visual Basic 6.0 projects, or to name your Visual Basic 6.0
folders. You receive the error message because the Visual Basic .NET or Visual
Basic 2005 Upgrade Wizard incorrectly interprets the trailing bytes of these
DBCS characters as the '[' (0x5b) single-byte character set (SBCS) character
and the '\' (0x5c) SBCS character. Therefore, the Visual Basic .NET or Visual
Basic 2005 Upgrade Wizard expects files, projects, or folders with names that
contain these SBCS characters. However, these files, projects, or folders only
contain DBCS characters, so you receive the error message.WORKAROUNDTo work around this bug, use names that do not contain DBCS
characters with 0x5b or 0x5c trailing bytes to rename your Visual Basic 6.0
files, to rename your Visual Basic 6.0 projects, and to rename the folders that
contain these files and projects. Use other DBCS characters or valid SBCS
characters instead. Next, run the Visual Basic .NET or Visual Basic 2005
Upgrade Wizard. You can successfully upgrade your Visual Basic 6.0 projects to
Visual Basic .NET or Visual Basic 2005 projects.STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are
listed at the beginning of this article.
REFERENCESFor more information, visit the following Microsoft
Developer Network (MSDN) Web site: For more information about upgrading Visual Basic 6.0 applications
to Visual Basic .NET and Visual Basic 2005, visit the following MSDN Web site::
Modification Type: | Minor | Last Reviewed: | 10/3/2006 |
---|
Keywords: | kbvs2005swept kbvs2005applies kbvs2002sp1sweep kbwizard kbDBCS kbSysSettings kbLocalization kbUpgrade kbMigration kbmigrate kberrmsg kbbug KB819350 kbAudDeveloper |
---|
|