What causes ADF Pipeline Error 2200?

Incorrect or unsupported SQL/query syntax sent via the ODBC driver. Misconfigured ODBC connection string or missing DSN on the Self-hosted Integration Runtime node. ODBC driver version mismatch or missing driver installation on the IR machine. Insufficient permissions for the ODBC user account to execute the requested operation

How do I fix ADF Pipeline Error 2200?

Step 1: Review the full error message in the ADF activity run details to identify the specific ODBC driver error code and message beneath error 2200.. Step 2: Verify the ODBC connection string and DSN configuration on the Self-hosted Integration Runtime machine using the ODBC Data Source Administrator tool.. Step 3: Confirm the correct ODBC driver version is installed on the IR node and matches the bitness (32-bit vs 64-bit) of the Integration Runtime.. Step 4: Test the query or stored procedure independently using a local ODBC client to rule out syntax or permission issues.. Step 5: Check that the ODBC user account has the necessary read/write permissions on the target data source, and update linked service credentials if needed.

High severityconnectivityAzure Data Factory →

Power BI Refresh Error:
ADF Pipeline Error 2200

What does this error mean?

Error code 2200 (UserErrorOdbcOperationFailed) occurs when an ODBC-based copy activity in Azure Data Factory fails due to an invalid operation, bad query, or misconfigured ODBC connection. This is a general copy activity error that can surface across multiple connectors.

Common causes

1Incorrect or unsupported SQL/query syntax sent via the ODBC driver
2Misconfigured ODBC connection string or missing DSN on the Self-hosted Integration Runtime node
3ODBC driver version mismatch or missing driver installation on the IR machine
4Insufficient permissions for the ODBC user account to execute the requested operation

How to fix it

1Step 1: Review the full error message in the ADF activity run details to identify the specific ODBC driver error code and message beneath error 2200.
2Step 2: Verify the ODBC connection string and DSN configuration on the Self-hosted Integration Runtime machine using the ODBC Data Source Administrator tool.
3Step 3: Confirm the correct ODBC driver version is installed on the IR node and matches the bitness (32-bit vs 64-bit) of the Integration Runtime.
4Step 4: Test the query or stored procedure independently using a local ODBC client to rule out syntax or permission issues.
5Step 5: Check that the ODBC user account has the necessary read/write permissions on the target data source, and update linked service credentials if needed.

Frequently asked questions

Can error 2200 occur with non-ODBC connectors in ADF?

No — error 2200 specifically maps to UserErrorOdbcOperationFailed and is only raised by ODBC-based connectors or activities that route through an ODBC driver layer.

Do I need to restart the Integration Runtime after installing a new ODBC driver?

Yes. After installing or updating an ODBC driver on the Self-hosted IR node, restart the Integration Runtime service so the new driver is picked up correctly.