Ssis 134

SSIS 134 — Draft Content

2. Error Identification

| Attribute | Typical Value | |-----------|----------------| | Error Code (numeric) | 134 (in catalog.operations.message) | | HRESULT | 0x80020009 | | Symbolic Name | DISP_E_EXCEPTION | | Description | An exception occurred during a COM or scripting operation. | | SSIS Component | Script Task, Script Component, or third-party data flow component. |

Step-by-Step Troubleshooting

1. Read the full error message – SSIS errors include a "Description" field. Look for column names, data values, or system error details.
2. Check the component type – Is it from a Data Flow Task, Execute SQL Task, or Script Task?
3. Enable logging – Set logging to Verbose or Diagnostic for the failing task.
4. Use a Data Viewer – For data flow issues, attach a data viewer to the path just before the error occurs.
5. Search the numeric code – In some cases, the "Error Code" is a hex HRESULT. Convert decimal 134 to hex: 0x86. SSIS internal errors often start with 0x8004… So 134 might be a sub-code of a larger error (e.g., 0x800470C2 = decimal -2147466046, not 134).

5.1 Immediate Fix

• Wrap Script Task code in a try-catch and log the actual exception:

  public void Main()
  try
  // Your logic
          Dts.TaskResult = (int)ScriptResults.Success;
  catch (Exception ex)
  Dts.Events.FireError(0, "Script Task", ex.Message, "", 0);
          Dts.TaskResult = (int)ScriptResults.Failure;
  

Step 2: Inspect the ErrorColumn Property

When an error occurs, the SSIS pipeline populates system variables like ErrorCode (134) and ErrorColumn. Capture these in a script transformation or log them to a flat file. The ErrorColumn returns the LineageID of the column causing the issue. ssis 134

• How to find the column name: In your Data Flow, go to Advanced Editor → Input and Output Properties → Find the output containing the LineageID matching the number. That column is your culprit.

5. Buffer Size Limitations (Less Common)

In very large row sizes (>8KB per row) with high default buffer sizes, memory allocation can fail, generating a variant of SSIS 134 referencing buffer allocation failure. However, this is rarer than data type issues. SSIS 134 — Draft Content 2

4. Diagnostic Approach

| Step | Action | Tool | |------|--------|------| | 1 | Identify exact package and task failing | SSIS Catalog reports / catalog.executions | | 2 | Retrieve full error message (including inner exception) | catalog.operation_messages | | 3 | Enable verbose logging (OnError, OnTaskFailed) | SSIS Logging / Data Taps | | 4 | Reproduce locally with breakpoints | Visual Studio / SSDT | | 5 | Check script code for unhandled exceptions | C#/VB code review | | 6 | Validate data types of input/output columns in Script Component | Advanced Editor | Read the full error message – SSIS errors