Visual Basic Development Bookmark and Share   
 Home > Visual Basic Interop and Upgrade > Unexpected exception occurred during upgrade engine operation
 

Unexpected exception occurred during upgrade engine operation

Hi,

During a every conversion of a 'VB6 project' to 'VB 2005 Express', I'm always getting folowing error:

---------------------------
Visual Basic Upgrade Wizard error
---------------------------
Unexpected exception occurred during upgrade engine operation: Kan niet aan de bron binden (Exception from HRESULT: 0x8004000A (OLE_E_CANT_BINDTOSOURCE))
---------------------------
OK
---------------------------

My System: Windows 2000 SP4 (Clean Install) - Visual Basic 2005 Express ed.

Any ideas howto resolve this?

Thx.

HomeBunny  Tuesday, August 22, 2006 8:52 AM

I'm sorry to hear that wasn't the cause of the problem.I would like to work with you directly offline to see if we can determine what the cause is.

Can you please email me directly at JohnHart@Microsoft.com. ?

This way we canget to the bottom of this quicker.

JohnHart_MSFT  Thursday, August 24, 2006 4:22 PM

We took a closer look at this offline. For some reason there was a key missing from the registry. We simply added the following keys back to the registryand the Upgrade Wizardworked correctly.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\VBUpgrade\Source Language Drivers\Visual Basic]
@="Visual Basic 6.0"
"FileLocation"="vbsld"


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\VBUpgrade\Target Language Drivers\VB7]
@="Visual Basic 7"
"FileLocation"="vb7tld"

If you’re experiencing a similar error please take care when editing or changing your registry.

JohnHart_MSFT  Wednesday, August 30, 2006 3:14 PM
Hi,
Copy Following lines:
;---------------------------------------------------------------------------------------------------------------------------------------
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\VBUpgrade]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\VBUpgrade\Source Language Drivers]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\VBUpgrade\Source Language Drivers\Visual Basic]
@="Visual Basic 6.0"
"FileLocation"="VBSLD"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\VBUpgrade\Target Language Drivers]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\VBUpgrade\Target Language Drivers\VB7]
@="Visual Basic 7"
"FileLocation"="vb7tld"
;---------------------------------------------------------------------------------------------------------------------------------------
and paste them in a new notepad, save this as eq. 'ResolveError.reg'
Greetz,
HomeBunny  Saturday, November 04, 2006 10:02 AM

This is a bug with the Upgrade Tool where it gets confused on where its registry settings are if there is an HLKM\Software\Wow3264Node key in the registry on a 32-bit machine.

Take a look at your registry by running RegEdit at the command line and opening the node HKEY_LOCAL_MACHINE\Software and check to see if you have key called Wow3264Node. If so temporarily rename it by right clicking on the key and selecting rename from the pop-up menu.

Then run the Upgrade Wizard. It should now run fine.

Once you have finished with the wizard you can go back and rename the registry key.

I'm sorry for the inconvenience but I hope that helps.

JohnHart_MSFT  Tuesday, August 22, 2006 4:05 PM

Hi John,

I've searched the complete register, no key 'Wow3264Node' founded.

Any other ideas?

Greetz,

HomeBunny  Wednesday, August 23, 2006 7:15 AM

I'm sorry. There was a typo in my answer the registry path should have been Wow6432Node. Specifically please look for HLKM\Software\Wow6432Node. If it exists temporarily rename the Wow6432Node key.

JohnHart_MSFT  Wednesday, August 23, 2006 2:50 PM

Hi,

I've searched the whole register for 'Wow6432Node', without luck.

There are no 'Wow' keys under 'HLKM\Software\' at all.

Any other ideas what could causing this?

Greetz,

HomeBunny  Thursday, August 24, 2006 10:52 AM

I'm sorry to hear that wasn't the cause of the problem.I would like to work with you directly offline to see if we can determine what the cause is.

Can you please email me directly at JohnHart@Microsoft.com. ?

This way we canget to the bottom of this quicker.

JohnHart_MSFT  Thursday, August 24, 2006 4:22 PM

We took a closer look at this offline. For some reason there was a key missing from the registry. We simply added the following keys back to the registryand the Upgrade Wizardworked correctly.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\VBUpgrade\Source Language Drivers\Visual Basic]
@="Visual Basic 6.0"
"FileLocation"="vbsld"


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\VBUpgrade\Target Language Drivers\VB7]
@="Visual Basic 7"
"FileLocation"="vb7tld"

If you’re experiencing a similar error please take care when editing or changing your registry.

JohnHart_MSFT  Wednesday, August 30, 2006 3:14 PM

Can send me the .reg file to my email...

vgta_@hotmail.com

thans

vgta  Friday, November 03, 2006 7:19 PM
Hi,
Copy Following lines:
;---------------------------------------------------------------------------------------------------------------------------------------
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\VBUpgrade]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\VBUpgrade\Source Language Drivers]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\VBUpgrade\Source Language Drivers\Visual Basic]
@="Visual Basic 6.0"
"FileLocation"="VBSLD"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\VBUpgrade\Target Language Drivers]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\VBUpgrade\Target Language Drivers\VB7]
@="Visual Basic 7"
"FileLocation"="vb7tld"
;---------------------------------------------------------------------------------------------------------------------------------------
and paste them in a new notepad, save this as eq. 'ResolveError.reg'
Greetz,
HomeBunny  Saturday, November 04, 2006 10:02 AM
renaming the Wow6432Node key worked for me thanks
Smokestack Herman  Wednesday, July 08, 2009 4:09 PM
renaming the Wow6432Node worked thxx a ton
arvinder06  Thursday, November 19, 2009 4:24 PM

You can use google to search for other answers

Custom Search

More Threads

• Interop Default Property not resolved in VBScript
• CLASS NOT REGISTERED EXCEPTION
• Upgrading Sage Data Object code to VB.NET
• Using True DB Grid with VB.net ---True DB grid events are not executing
• VB6 Upgrade Assesment Tool - Missing Main Report
• Call a vb.net form from a vb6 mdi Container
• VBA call to VB 2005 DLL (COM) fails
• Null reference exception
• REGTLIB.EXE
• VB Runtime? What is it?