Ssis-913 ((new)) -

Understanding SSIS-913

1. 1. Regularly update OLE DB providers: Ensure that OLE DB providers are up-to-date and compatible with your SSIS version.
   2. Validate connection strings: Double-check connection strings for accuracy.
   3. Test packages thoroughly: Perform thorough testing of packages before deploying them to production.

   Possible Interpretations of SSIS-913

   4. Systematic troubleshooting checklist

   | Step | Action | What you’re looking for | |------|--------|------------------------| | A. Identify the offending component | Open Progress tab in SSDT, locate the line that contains “SSIS‑913”. | It will read The component "<ComponentName>" (##) failed validation …. | | B. Verify the upstream schema | Run the exact SQL query the source component uses (right‑click → Show Advanced Editor → Component Properties → SqlCommand). | Does the result set contain the missing column? | | C. Check for dynamic SQL | Look for expressions that build the SQL statement (@[User::SqlCmd], @[User::TableName]). | If you see SELECT *, consider replacing it with an explicit column list. | | D. Refresh metadata | In the source component, click Refresh (or Preview → Refresh). In downstream components, right‑click → Show Advanced Editor → Input and Output Properties → Refresh. | The component now knows the current column list. | | E. Re‑map columns | If a column was renamed, open the downstream component’s Input and Output Properties, find the old column, and map it to the new name (or delete the stale mapping). | No more dangling references. | | F. Re‑build the data flow (if the above fails) | Delete the offending component and drop it back onto the canvas, reconnect the arrows, and re‑configure its properties. | Guarantees a clean metadata state. | | G. Turn off “ValidateExternalMetadata” (last resort) | Set ValidateExternalMetadata = False on the source component (Properties window). | The engine will skip the pre‑execution validation and let the component fail at run‑time instead. Use only when you know the column will be there at execution. | | H. Upgrade / Patch | Ensure you are on the latest cumulative update for your SQL Server version. Some early SSIS releases had bugs that caused phantom 913 errors when using DataReader Source or ADO.NET Source. | Eliminates known product bugs. | SSIS-913

   Understanding SSIS-913 Error