SSIS
Error: The “Derived Column” failed because truncation occurred, and the truncation row disposition on “Derived Column.Outputs[Derived Column Output].Columns[FilePath]” specifies failure on truncation. A truncation error occurred on the specified object of the specified component.
Category: SSIS Author: Nishant Rana Date: 6 months ago Comments: 0

We might get the error while using Derived Column in our SSIS Package To fix it right click the Derived Column component and select Show Advanced Editor .. Go to Input and Output Properties tab, expand Derived Column Output and select the field and update the length in the properties window. Hope this helps..
Source: Nishant Rana


Fixed – DTS_E_PROCESSINPUTFAILED. The Process input method on component “Script Component” failed with error code 0x80131501 in SSIS
Category: Dynamics 365,Microsoft Dynamics 365,SSIS Author: Nishant Rana Date: 7 months ago Comments: 0

Recently I had written an article for Nigel Frank that list down step by step process of using XML Source Component of KingswaySoft for integration with Dynamics 365 CE https://www.nigelfrank.com/blog/integrate-dynamics-365-for-customer-engagement-with-xml/ We have used XML Source Component to read the XML files. The packages that we developed were running fine from Visual Studio SSDT but on … Continue reading “Fixed – DTS_E_PROCESSINPUTFAILED. The Process input method on component “Script Component” failed with error code 0x80131501 in SSIS”
Source: Nishant Rana


Fixed – The Script Task uses version 15.0 script that is not supported in this release of Integration Services
Category: Microsoft Dynamics 365,SSIS Author: Nishant Rana Date: 7 months ago Comments: 0

Recently after deploying the SSIS packages, on one of the packages that uses Script Component, we started getting below error message This happened because SSIS packages had target version SQL 2017 and the SQL Server version was 2016 (select @@VERSION) The fix is to update the target version that matches the SQL Server Version. Right … Continue reading “Fixed – The Script Task uses version 15.0 script that is not supported in this release of Integration Services”
Source: Nishant Rana


Fixed – Script Component has encountered an exception in user code. Value cannot be null. Parameter name: keyword in SSIS
Category: Dynamics 365,kingswaysoft,Microsoft Dynamics 365,SSIS Author: Nishant Rana Date: 7 months ago Comments: 0

Recently while trying to use KingswaySoft’ s CRM Connection Manager in the Script Component we got the below error Turned out the issue was because of the wrong version of KingswaySoft.IntegrationToolkit.DynamicsCrm assembly being referred. C:WindowsMicrosoft.NETassemblyGAC_MSILKingswaySoft.IntegrationToolkit.DynamicsCrm Referencing the correct one fixed it. Hope it helps..
Source: Nishant Rana