The add-in 'Telerik OpenAccess' failed to load or caused an exception.
The error message is "Unspecified Error" and the number is 80004005 (which is typically access denied). Any thoughts?
Thanks,
Colin
21 Answers, 1 is accepted
There is a chapter in the programmer's guide about checking the correct installation of the addin. Can you pls. look into that and check if esp. the addin file has the right content?
Kind regards,
Jan Blessenohl
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
You will find the chapter online here:
http://www.telerik.com/help/openaccess-orm/troubleshooting.html
Greetings,
Jan Blessenohl
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
I checked the troubleshooting guide and the missing piece appears to be the registry entry. I should note I am running Visual Studio 2008 on Windows Vista x64. I can try re-installing it, but I suspect it will result in the same given that it was a fresh install in the first place. What should be in the registry?
Thanks,
Colin
Can you nevertheless pls. uninstall OpenAccess completely, delete the installation folder and install it again?
The important registry entry is the addin load path: Inside VS go to Tools->Options->Environment->Add in/Macro Security and see if there is the path of the addin file in the list. If not just add it.
The other thing is a regasm call with the Telerik.OpenAccess.SDK.Addin dll:
regasm /codebase /register Telerik.OpenAccess.SDK.AddIn.dll
Best wishes,
Jan Blessenohl
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Sorry about those problems, I just tried it on my Windows 7 x64 and I was able to install it without any problems. We will investigate further to see where the problems comes from.
Best wishes,
Jan Blessenohl
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Jason
We are signing our installers currently, and elevated the rights for some of the actions performed by the installer. We believe that the Q1 2009 release will allow installation without any problems.
Greetings,
Dimitar Kapitanov
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
FYI I do this now with most of the installs of software that is even moderatly ciomplex, I remember the early days of Vista where you pretty much always had to do this on every install. Most products work without having to do this, but it's a good thing to try if you feel the product hasn't installed perfectly the first time.
The setup.exe knows that it has to run in admin mode. You should see a UAC if you start it. If you start the msi directly in some circumstances it does not seem to elevated the user rights.
It is recommended to start setup.exe. It is able to do an update of the existing installation, this will not be done if you use the msi.
Best wishes,
Jan Blessenohl
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Thanks
Windows 7 x64, Visual Studio 2008 SP1
My Registry deletes and Revo did the trick. I can now install OpenAccess again.
But now when I install OpenAccess I am back to the beginning. I dont get error messages. It shows up on the VS splash screen but there is no menu option under Telerik for OpenAccess. Also there is no AddIn in the AddinManager. I checked the Registry but my registry is different than the on described in the Trouble shooting docs.
The Key shows up under 9.0 not 90
and in the CurrentUser not the LocalMachine
I tried the suggestions about regasm and the Addin path and that did not work
I will try the setup.exe from an elevated cmd and report back
I need some help
Can you please use the tool Telerik.OpenAccess.AddinInstaller.exe from the sdk directory of our OpenAccess installation. You should click uninstall/install. If that does not work please send me the content of the log window of the tool after doing uninstall/install.
Regards,
Jan Blessenohl
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
however now a
Package Load Failure of Telerik.CommonPackage.Telerik_CommonPackagePackage
Error pops up when I launch Visual Studio.
I have found the problem, the AddinInstaller registers the package with a wrong version number. Can you please change the version in the registry by hand or generate one of the two regfiles and execute them:
Change the package registry key by hand:
Regfile content for 32 bit machines:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\Packages\{d4f5086c-54b9-4b07-bd22-af72d5b9228f}]
@="Telerik.CommonPackage.Telerik_CommonPackagePackage, Telerik.CommonPackage, Version=1.0.5.0, Culture=neutral, PublicKeyToken=d63abc9583eb6f32"
Regfile content for 64 bit machines:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\8.0\Packages\{d4f5086c-54b9-4b07-bd22-af72d5b9228f}]
@="Telerik.CommonPackage.Telerik_CommonPackagePackage, Telerik.CommonPackage, Version=1.0.5.0, Culture=neutral, PublicKeyToken=d63abc9583eb6f32"
Sincerely yours,
Jan Blessenohl
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
I also had to change the CodeBase REG_SZ to
"C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\Telerik.CommonPackage.dll"
it was C:\Program Files...\telerik\sdk\...
Now I dont get any errors
I have fixed this as well, your telerik points have been updated.
Kind regards,
Jan Blessenohl
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.