SSIS package works in Visual Studio 2022 but not from command line?

Greg Troyan 0 Reputation points
2025-08-13T20:37:02.52+00:00

I have a snippet of a workload that involves importing data from a CSV file into a MySQL database via ODBC. When I run it within Visual Studio it works just fine but when I run it via DTexec.exe (64-bit) it fails with the following errors:

Description: The value of the property 'ExclusionGroup' is incorrect. Description: "ODBC Destination" failed validation and returned validation status "VS_ISCORRUPT".

Google tells me that I need to configure ExclusionGroup but I've never had to do this before in the 20 years of using SSIS so this feels like a red herring. Similarly Google results for VS_ISCORRUPT say that I must have edited a package XML file directly and messed it up, which I have not done.

This seems like a bog-standard data import process but these errors have me completely stumped. It seems like there's something else wrong but these are the errors that manifest so I'm troubleshooting them with no success.

Help?

The package is simple:

dataflowtask

dataflow

The details:

-the CSV file has approximately 180,000 rows

  • the destination is a AWS Aurora MySQL 3.08.2 (MySQL 8.0.39 compatible)
  • visual studio 2022 with SSIS extension 1.6.2 (64-bit)
  • The ETL server is Windows Server 2019 with SSIS from SQL Server 2017
  • MySQL Connector/ODBC 9.4 (64-bit)
SQL Server Integration Services
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Shruti Dhruv 0 Reputation points
    2025-11-12T04:44:41.3266667+00:00

    Hi Greg Troyan,

    Thanks for sharing the details and screenshots! Based on what you’ve described, the issue seems to be not about ExclusionGroup. The error VS_ISCORRUPT usually means the component metadata is invalid or incompatible in the runtime environment.
    You can try:

    1. Run DTExec in 32-bit mode or Or in SQL Agent, enable (Use 32-bit runtime) in the job step
    2. Use ADO.NET Destination Instead of ODBC
    3. Try MySQL ODBC 8.0.33 or 5.3.14, which are widely tested with SSIS.

    ExclusionGroup is an internal property for mutually exclusive precedence constraints. The error is misleading because the real issue is the component metadata corruption during validation in DTExec.

    Hope this helps!

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.