Add-in failed in Data Access, formerly OpenAccess ORM Getting Started

ColinBowern

51 posts

Member since:
Aug 2012

Posted 18 Dec 2008 Link to this post

After installing OpenAccess I popped open Visual Studio to receive the following message:

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

Jan Blessenohl

Admin

707 posts

Posted 19 Dec 2008 Link to this post

Hello colinbo,
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.

Jan Blessenohl

Admin

707 posts

Posted 19 Dec 2008 Link to this post

Hi colinbo,
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.

ColinBowern

51 posts

Member since:
Aug 2012

Posted 21 Dec 2008 Link to this post

Hi Jan,

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

Jan Blessenohl

Admin

707 posts

Posted 22 Dec 2008 Link to this post

Hello colinbo,
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.

mthird

1 posts

Member since:
Feb 2007

Posted 29 Jan 2009 Link to this post

I had this same problem in Windows 7 x64. I had to replace __ASSEMBLY__ with the full path (e.g. C:\Program Files (x86)\Telerik\OpenAccess ORM\sdk\Telerik.OpenAccess.SDK.AddIn.dll)

Jan Blessenohl

Admin

707 posts

Posted 02 Feb 2009 Link to this post

Hello mthird,
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

1 posts

Member since:
Aug 2008

Posted 19 Feb 2009 Link to this post

I also had a problem with the add-in failing to load on Windows 7 x64 with Visual Studio 2008. I used mthird's method suggestion and was able to get the add-in to load.

Jason

Dimitar Kapitanov

Admin

632 posts

Posted 20 Feb 2009 Link to this post

Hi 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.

joshua odell

30 posts

Member since:
Sep 2008

Posted 25 Apr 2009 Link to this post

I had a similar issue when I installed Q1 release on Windows 7 (x64). the install ran without errors but I got an error when loading visual studio 2008 sp1 (stating that the addin failed to load). I uninstalled and then reinstalled from an elevated privilage command window (right clicked your cmd.exe shortcut, and selected "Run as Administrator" i then ran the msi from that elevated command window, and the install went flawlessly. after that I was able to run visual studio and the open access addin loaded correctly.

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.

Joel

1 posts

Member since:
Mar 2009

Posted 29 Jul 2009 Link to this post

The same technique of running Setup.exe from a command prompt in Administrator mode also seems to be required for Windows Server 2008 and for Windows Server 2008 R2. Telerik ORM version: 2009.01.0405.1

Jan Blessenohl

Admin

707 posts

Posted 30 Jul 2009 Link to this post

Hi Joel,
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.

sbe

5 posts

Member since:
Jul 2007

Posted 17 Sep 2009 Link to this post

I had the same problem, do not run the msi file, but run the setup.exe. Then it works fine

Davide Vernole

3 posts

Member since:
Dec 2005

Posted 18 Oct 2009 Link to this post

Same issue in Windows 7 x64. I have followed Joshua tip and now it works fine.

Thanks

MiddleTommy

163 posts

Member since:
Nov 2009

Posted 24 Nov 2009 Link to this post

I have tried uninstalling/reinstalling I could not get it to work. I uninstalled visual studio 2010 Beta 2 thinking there might be a conflict with Open Access. Now I can not uninstall OpenAccess. I even tried removing it manually after several uninstall failures and still no go. Open Access is not installed but the installer thinks it is. How do I manually uninstall OpenAcces ORM so I can try again to get this installed?
Windows 7 x64, Visual Studio 2008 SP1

MiddleTommy

163 posts

Member since:
Nov 2009

Posted 24 Nov 2009 Link to this post

I deleted a bunch of registry entries then remembered revo uninstaller
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

MiddleTommy

163 posts

Member since:
Nov 2009

Posted 24 Nov 2009 Link to this post

I have tried all the suggestions and Telerik OpenAccess still will not work. It shows up on the splash screen of VS. It is listed under the Addins search path. I did regasm. No Go. I can not see OpenAccess in the Telerik menu in VS
I need some help

Jan Blessenohl

Admin

707 posts

Posted 25 Nov 2009 Link to this post

Hi TWT,
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.

MiddleTommy

163 posts

Member since:
Nov 2009

Posted 25 Nov 2009 Link to this post

The installer worked and I can now use OpenAccess
however now a
Package Load Failure of Telerik.CommonPackage.Telerik_CommonPackagePackage
Error pops up when I launch Visual Studio.

Jan Blessenohl

Admin

707 posts

Posted 26 Nov 2009 Link to this post

Hello TWT,
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.

MiddleTommy

163 posts

Member since:
Nov 2009

Posted 01 Dec 2009 Link to this post

Thanks
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

Jan Blessenohl

Admin

707 posts

Posted 02 Dec 2009 Link to this post

Hello TWT,
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.