S
scorpion53061
First the obvious lets make sure your wrappers and dlls are registered
and properly imported.
I have heard of this occurring in the past, usually because of a
registry corruption of some registered interfaces
(generally not caused by the Visual Studio install, but some other
application). It appears that at least one in
instance showed that the entries for the IEnumVARIANT interface were
corrrupted. You should check your registry
and see if it matches the following:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{00020404-0000-0000-C000-0000
00000046}]
@="IEnumVARIANT"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{00020404-0000-0000-C000-0000
00000046}\NumMethods]
@="7"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{00020404-0000-0000-C000-0000
00000046}\ProxyStubClsid]
@="{00020421-0000-0000-C000-000000000046}"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{00020404-0000-0000-C000-0000
00000046}\ProxyStubClsid32]
@="{00020421-0000-0000-C000-000000000046}"
If not, that is probably the source of your problem. Export the above
to a .reg file and run it.
Of course, in stuff like this there are not guarantees.
and properly imported.
I have heard of this occurring in the past, usually because of a
registry corruption of some registered interfaces
(generally not caused by the Visual Studio install, but some other
application). It appears that at least one in
instance showed that the entries for the IEnumVARIANT interface were
corrrupted. You should check your registry
and see if it matches the following:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{00020404-0000-0000-C000-0000
00000046}]
@="IEnumVARIANT"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{00020404-0000-0000-C000-0000
00000046}\NumMethods]
@="7"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{00020404-0000-0000-C000-0000
00000046}\ProxyStubClsid]
@="{00020421-0000-0000-C000-000000000046}"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{00020404-0000-0000-C000-0000
00000046}\ProxyStubClsid32]
@="{00020421-0000-0000-C000-000000000046}"
If not, that is probably the source of your problem. Export the above
to a .reg file and run it.
Of course, in stuff like this there are not guarantees.