News Article

"Method not found" error

Sept. 10th, 2004

Follow up: RC3 has fixed this issue.

Thanks to Gary Pupurs for contributing this information.

This may be a possible solution for the "Method not found" error mssage that some people are reporting. We continue to investigate this.

It seems as though this error may be a versioning problem related to the Microsoft .MSI installer failing to uninstall previous versions of VistaDB from the Global Assembly Cache.

After uninstalling the VistaDB Provider and Designer from the GAC, the article suggest that you will need to delete some registry keys from here:
HKEY_CURRENT_USER\Software\Microsoft\Installer\Assemblies\Global
Delete these 2 entries: VistaDB.Designer,Version="2.0.0.0",Culture="neutral",PublicKeyToken="..."
VistaDB.Provider,Version="2.0.0.0",Culture="neutral",PublicKeyToken="..."

It doesn't seem that the VistaDB installer adds entries to the following key, but the article suggests to delete them from here as well, if they exist:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Assemblies\Global

It seems that the .MSI uninstaller has a corrupt value in the registry, which is preventing a proper uninstall of the VistaDB Provider. This applies to other .NET components and assemblies. The real problem is that deleting the VistaDB directory will not fix this! That's why this error is so difficult to trace.

For more information, please read here:
http://weblogs.asp.net/alanshi/archive/2003/12/10/42690.aspx
http://weblogs.asp.net/alanshi/archive/2003/12/10/42690.aspx#159792