“Runtime error Exception has been thrown by the target of an invocation” from Script task

Question

I have a SSIS package with a script task, I get the following error when i try to run it in my local system. It works fine for my collegues as well as in production. However

Answer 1

In my case it was missing DLLs or not having the correct version installed on the server.

Locally all tests were fine but on the server the error message Runtime error Exception has been thrown by the target of an invocation kept popping up.

No exception handler would be able to catch that error - the code in the script task would not even be executed, as soon as a DLL would be needed, that is not in the assembly cache on the server (it could happen on a local machine as well, with the same error).

The difficulty here is finding out what is missing and then either update the references to the correct version or install the missing DLL in the assembly cache with gacutil. The way I approached the debugging was to remove parts of the code in the script task until that error wouldn't appear, then analyze the missing part for references.

Answer 2

I got this error message when I referred to a passed ssis variable in Dts.Variables["User::xxxx].Value(); where xxxx did not exist and was not passed from the calling program. It was a simple Console.Writeline referring to a passed variable that didn't exist.

Answer 3

This is just a different situation and not intended to be the end all be all solution for everyone.

When I was installing my DLLs into the GAC I forgot to run my script as Administrator and the script ran silently without error as though it was working.

I felt really dumb when I realized that's what I did wrong. Hopefully this can help prevent other people from wasting time on something so silly.

For reference this is what I use for installing my DLLs into the GAC and I modified it to tell me when I am not running it as Administrator now:

#https://superuser.com/questions/749243/detect-if-powershell-is-running-as-administrator
$isAdmin = ([Security.Principal.WindowsPrincipal] `
  [Security.Principal.WindowsIdentity]::GetCurrent() `
).IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)

if($isAdmin -eq $false)
{
    Write-Host "You have to run this script as Administrator or it just won't work!" -ForegroundColor Red

    return;
}

$strDllPath = "C:\PathToYourDllsHere\"

#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            


$arr = @(
    "YourDLL01.dll",
    "YourDLL02.dll",
    "YourDLL03.dll"
)

get-date

foreach($d in $arr)
{
    $p = ($strDllPath + $d);

    $p

    $publish.GacInstall($p);
}

#If installing into the GAC on a server hosting web applications in IIS, you need to restart IIS for the applications to pick up the change.
#Uncomment the next line if necessary...
#iisreset

Credit for how to determine if your PowerShell script is running in Admin mode or not: https://superuser.com/questions/749243/detect-if-powershell-is-running-as-administrator

Answer 4

Its fixed, when added reference to dll version 12.0.0 and changed Target Framework to .Net Framework 4.5

Answer 5

I fixed this error by changing the TargetServerVersion of the SSIS Project.

Integration Services Project Property Pages

Answer 6

I had the same Problem (i.e. the same error code Error: 0x1 ...).

The issue was with some of the libraries referenced from a missing folder.

Removing the references and adding them back from the correct path fixed the issue.

The Microsoft Reference (https://msdn.microsoft.com/en-us/library/ms345164.aspx) related to the Error code is very generic and doesn't help you much. However, reading other articles it is quite likely it indicates an unknown failure reason to run the Script Task.

• Hexadecimal code: 0x1
• Decimal Code: 1
• Symbolic Name: DTS_MSG_CATEGORY_SERVICE_CONTROL
• Description: Incorrect function.