Post reply

Unsafe assembly 'microsoft.sqlserver.integrationservices.server, version=12.0.0.0

  • December 2, 2015 at 8:51 am

    #305724

    We're running SQL Server 2014 Enterprise edition (12.0.4100 x64) on Windows Server 2012 R2 Data Center -- on a 2 node cluster

    > Using SSDT (VS 2013) we added existing SQL 2008 R2 SSIS pkg and it converted/upgraded clean

    > We tweaked the CONNECTION to point to new SQL Server name

    > We successfully tested / executed the SSIS Pkg in SSDT (VS 2013)

    > We successfully deployed the SSIS pkg to Integration Services Catalog

    > We successfully created JOB to execute the pkg (using a PROXY w/ Credential)

    > Job executes clean and everything completes successfully BUT we see a funky message on ERROR LOG for SQL Server:

    Unsafe assembly 'microsoft.sqlserver.integrationservices.server, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil' loaded into appdomain 2 (SSISDB.dbo[runtime].1).

    Does anyone know what this is? Do we need to correct this?

    BT

  • December 3, 2015 at 12:04 am

    #1843697

    https://msdn.microsoft.com/en-us/library/hh213291.aspx

    Integration Services CLR stored procedures require UNSAFE permissions to be granted to the login because the login requires additional access to restricted resources, such as the Microsoft Win32 API.

    For this one, I believe Peril-Sensitive Sunglasses would make no difference :).

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply