none
Could not load file or assembly 'microsoft.sqlserver.integrationservices.server RRS feed

  • Question

  • I'm trying to deploy a SSIS package from Visual Studio to my secondary server.  The db owner is the same on server 2 as it is on server 1.  This is the error message that I get.

    An error occurred in the Microsoft .NET Framework while trying to load assembly id 65536. The server may be running out of resources, or the assembly may not be trusted with PERMISSION_SET = EXTERNAL_ACCESS or UNSAFE. Run the query again, or check documentation to see how to solve the assembly trust issues. For more information about this error: 
    System.IO.FileLoadException: Could not load file or assembly 'microsoft.sqlserver.integrationservices.server, Version=13.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. An error relating to security occurred. (Exception from HRESULT: 0x8013150A)
    System.IO.FileLoadException: 
       at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
       at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
       at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
       at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
       at System.Reflection.Assembly.Load(String assemblyString)
     (Microsoft SQL Server, Error: 10314)


    Wednesday, September 18, 2019 8:22 PM

All replies

  • Hi shewright,

    I hope you are deploying SSIS project to a SSISDB Catalog, which is a standard option for SSIS 2012 onwards.

    It the best option to do the following:

    1. Create an *.ispac file on the dev. machine in VS.
    2. Copy *ispac file to the SSIS run-time server.
    3. Deploy it locally there in SSMS.


    Useful link: What is .ispac file in SSIS and deploy using 


    Wednesday, September 18, 2019 8:38 PM
  • Hi shewright,

    • If there is no other password or "sensitive" data incorporated into the package, please use "DontSaveSensitive" option. If SQL Server Authorization is used for any of the connections, or if any other "sensitive" data is incorporated into the package, then the package needs to have a Package Configuration file to save the password.
    • To work around this problem,  please use one of the following methods in this link.
    • The database owner hasn't changed and the database wasn't moved to a new server. The database no longer had the trustworthy property. Running the following might correct the issue:

    ALTER DATABASE SSISDB SET TRUSTWORTHY ON;

    Please refer to SSIS 2012 Project Deployment Failure to SSIS Catalog.

    Regards,

    Zoe


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Thursday, September 19, 2019 1:45 AM
  • Hi shewright,

    Have you resolve your issue? Would you kindly give us some feedback?

    If you found above answer is helpful, please mark it as answer, this can be beneficial to this community.

    Regards,
    Zoe


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Friday, September 27, 2019 7:23 AM