If an SSIS load fails due to incorrect connection strings, then the SSIS package will fail to create at run time. The connection string information in both the source connection and the data warehouse connection (the destination) must be checked to ensure that they are correct.
If the SSIS load fails due to incorrect extraction SQL, due to mismatched destination Load table structure or due to constraint violation, then the SSIS package is created in the file system for the developer to check. The SSIS package file is created in the WhereScape RED Work Directory; shown in the window opened from Help > About WhereScape RED (refer to the screen below).
This SSIS package will have a DTSX file extension and can be opened using the appropriate version of Microsoft's BI Development Studio add-in to Visual Studio.
The Integration Services load in RED does not currently automatically handle spaces in source field names. You need to put square brackets( [ ] ) around the source column in the column Properties of the Load table column that contains spaces in Excel. This prevents the SSIS (runtime) from crashing and returning an error message. The SSIS package file is created in the WhereScape RED Work Directory; shown in the above window, opened from Help > About WhereScape RED.
The Source tab for a Load_table has a drop-down list that provides the options for SSIS Source-Identifier Encapsulation. We use encapsulation to ensure that column aliases are not changed during an SSIS load: 