Could not load file or assembly 'Seagull.Data, Version=11.1.4.1, Culture=neutral, PublicKeyToken=109ff779a1b4cbc7' or one of its dependencies. Access is denied. S’abonner

0
Avatar
Nikhil Patel

I have installed Bartender 2019 enterprise automation edition on windows 10. Created file integration and tested successfully but when I am to deploy file integration to server(current machine) I am getting error : "Could not load file or assembly 'Seagull.Data, Version=11.1.4.1, Culture=neutral, PublicKeyToken=109ff779a1b4cbc7' or one of its dependencies. Access is denied."

If any one could help me that would be great.

Thanks.

4 commentaires

0
Avatar
David Lindner
Actions pour les commentaires Permalien

Have you found a solution?  I am running into the same situation.

0
Avatar
James Christian
Actions pour les commentaires Permalien

Have either of you found a solution to this?

1
Avatar
Jasper Wen
Modérateur
Actions pour les commentaires Permalien

We have seen some reports of this issue, but we have not been able to reproduce this issue internally. Generally, one of the following items helps resolve the issue.

  1. The Seagull.Data.Core.dll is stored in the BarTender installation directory C:\Program Files\Seagull\BarTender 2019. Make sure the user account that you are running BarTender has full permissions to this directory and file.
  2. Manually install the Seagull.Data.Core.dll into the Windows Global Assembly Cache. You can do this by running the following Windows PowerShell script as a local administrator. You may also need to restart your system for this to take effect. You can find more information from Microsoft here.
    #Note that you should be running PowerShell as an Administrator
    [System.Reflection.Assembly]::Load("System.EnterpriseServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a")
    $publish = New-Object System.EnterpriseServices.Internal.Publish
    $publish.GacInstall("C:\Program Files\Seagull\BarTender 2019\Seagull.Data.Core.dll")
0
Avatar
James Christian
Actions pour les commentaires Permalien

Jasper,

I can confirm option #2 fixed my problem.  Thanks!

Jame

Vous devez vous connecter pour laisser un commentaire.