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.
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.
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,
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 can get to the bottom of this quicker.
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 registry and the Upgrade Wizard worked 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.