Hi all,
I have created a package in a remote pc of a client (working as a Consultant) using VS2017 triggering an SQL procedure and using a C# script. The package could be successfully deployed both in the remote PC of my client and his local PC (using Visual Studio 2015). I had to edit the C# script to do some Excel file editing within the package before loading it to the SQL server.
The package is successfully executed in the remote PC (VS017) but when I try to execute it from the local I get the following error ('runtime error exception has been thrown by the target of an invocation'). I tried to put a breakpoint at the start of the script but I get the error before it can reach it. I suspect it has something to do with the libraries since when I comment out the excel editing from the C# it works fine. Both the remote PC and the local have Microsoft Office 2013 installed .
As the remote PC has both VS2015 and VS2017 I tried to execute the package with V2015 and it worked. I have tried removing all references and adding them back but I get the same error. My client is a Bank and I noticed that in local PC folder "C:windows\assembly\GAC_MSIL" is hidden or protected (however I can see it exists when browsing from the add reference Window). I tried to download the Microsoft.Office.Interop.Excel using the Nuget package where it will install the excel.dll in different folder (that is not hidden) but again I get the same error. I finally realized that in the local PC I am not able to run simple script just opening an excel file in a totally new package because of the same error.
Does anyone have a clue of what could be the problem here?
The package could be successfully deployed both in the remote PC of my client and his local PC (using Visual Studio 2015).
Overall, SSIS has 2 environments:
Development environment, on a dev. workstation, with VS and SSDT (or SQL Server Integration Services Projects for VS2019)
Run-time environment, on a server with SQL Server instance and SSIS with SSISDB Catalog.
It is not clear what and where you are
deploying
the SSIS project.
There is no need to install the entire MS Office for what you are doing. Just Microsoft Office Interop Assemblies. Check it out here:
office-primary-interop-assemblies
Useful links:
SSIS-Script-Task-and-Microsoft-Office-Automation.htm
how-to-add-the-microsoft-office-interop-in-ssis-c-sharp-script-task
Hi
@stefaen_pap
,
('runtime error exception has been thrown by the target of an invocation')
1.Check if package variables referenced in script task are correct
2. Check if package variables are being set correctly outside of the script task
3. Check if the script task’s references match up with the server’s framework
4. Check if you have full permissions
Please refer to
SSIS – Script Task: Exception Thrown by Target of an Invocation
.
Best Regards,
----------
If the answer is helpful, please click "
Accept Answer
" and upvote it.
Note: Please follow the steps in our
documentation
to enable e-mail notifications if you want to receive the related email notification for this thread.
