Useful links

Command line parameters. Checking command line arguments passed to PS script are present.


Good article here on why we should not use triggers and special case, audit, where it might have a role  

An Integration Services class cannot be found

Scenario: .NET job run SSIS package.

4/26/2018 11:28:04 AM ---- File ID: 308 File Name: Calypso_PLDecomp_US_TDBNA_USD
.20180419.csv.

4/26/2018 11:28:04 AM ---- ERROR - Issue during import of \\NYSVMBCHDEV1W01\Inbo
und\Calypso\GMONY\Calypso_PLDecomp_US_TDBNA_USD.20180419.csv - Microsoft.SqlServ
er.Dts.Runtime.DtsComException: An Integration Services class cannot be found. M
ake sure that Integration Services is correctly installed on the computer that i
s running the application. Also, make sure that the 64-bit version of Integratio
n Services is installed if you are running a 64-bit application.
 ---> System.Runtime.InteropServices.COMException: Retrieving the COM class fact
ory for component with CLSID {BA785E28-3D7B-47AE-A4F9-4784F61B598A} failed due t
o the following error: 80040154 Class not registered (Exception from HRESULT: 0x
80040154 (REGDB_E_CLASSNOTREG)).
   at Microsoft.SqlServer.Dts.Runtime.Application..ctor()
   --- End of inner exception stack trace ---
   at Microsoft.SqlServer.Dts.Runtime.Application..ctor()
   at TDS.CALImport.Calypso.RunSSISPackage(String FileID, String FileName, Strin
g SSISPackage, DateTime BusDate, String SQLServerName, String ISLogPath, String&
 dtsErrDescription) in C:\Stash\CRR\tecny_core\calimport-job\WinAppBackend.CALIm
port\Calypso.cs:line 654
   at TDS.CALImport.Calypso.ImportFile(DataRow DataFile) in C:\Stash\CRR\tecny_c
ore\calimport-job\WinAppBackend.CALImport\Calypso.cs:line 478.

Cause.
As message specified. 64-bit version of Integration Services is not installed

Resolution.
Set Target to 32Bit

How to open existing SSIS package

Open an existing SSIS package with Business Intelligent Studio
From Business Intelligent Studio
File->New Project->Integration Services Project

How to turn on Fusion assembly binding logging

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion
Add:
DWORD ForceLog set value to 1
DWORD LogFailures set value to 1
DWORD LogResourceBinds set value to 1
DWORD EnableLog set value to 1
String LogPath set value to folder for logs (e.g. C:\FusionLog\)

Make sure you include the backslash after the folder name and that the Folder exists.

You need to restart the program that you're running to force it to read those registry settings.

BTW, don't forget to turn off fusion logging off when not needed.

https://stackoverflow.com/questions/255669/how-to-enable-assembly-bind-failure-logging-fusion-in-net