How to fix Error 11571 on Windows Server 2025 / Windows 11

by

Troubleshooting Guide: Error 11571 – All Output Columns Declared as PARTITION Columns

Why This Error Happens

This error occurs when a DATA_EXPORT query in SQL Server 2025 is constructed with a SELECT list in which every column is mapped to a PARTITION BY clause, leaving no actual data columns for the export engine to serialize. The export engine requires at least one non-partition column to generate output content, and because partition columns are treated purely as metadata routing keys (used to determine file/folder splits), the engine has nothing left to write. This typically happens after a schema change, a copy-paste error in the export definition script, or an automated ETL template that incorrectly flags all source fields as partition keys.

Step-by-Step Resolution Guide

Step 1: Review the DATA_EXPORT Query Definition

  • Open the query or stored procedure that defines the DATA_EXPORT job in SQL Server Management Studio (SSMS) 21 or Azure Data Studio.
  • Locate the WITH (PARTITION_COLUMNS = (...)) clause and compare it against the full SELECT column list.
  • Confirm whether every column name listed in the SELECT statement also appears in the PARTITION_COLUMNS argument.

Step 2: Reclassify at Least One Column as a Data Column

  • Remove one or more non-key columns (e.g., measure values, timestamps, descriptive text fields) from the PARTITION_COLUMNS list.
  • Example correction:
  EXPORT DATA_EXPORT
  FROM (SELECT Region, SaleDate, Amount FROM Sales.Transactions)
  WITH (PARTITION_COLUMNS = ('Region', 'SaleDate'));

Here, Amount remains a true output/data column while Region and SaleDate drive partitioning.

  • Save the updated script to C:\SQLScripts\DataExport\export_definition.sql or your version-controlled repository.

Step 3: Validate Export Configuration via SQL Server Configuration Manager

  • Open SQL Server Configuration Manager on Windows Server 2025 / Windows 11 and confirm the Export Service (if running as a separate agent) is using the updated script path.
  • Restart the SQL Server Integration Services (SSIS) or Data Export Agent service to clear any cached query plans referencing the old column mapping.
  • Check C:\Program Files\Microsoft SQL Server\160\DTS\Binn\ (or the 2025 equivalent version folder) for stale .dtsx packages that may still reference the old partition schema.

Step 4: Re-run the Export Job in Validation Mode

  • Execute the export with the -ValidateOnly flag (or the SSMS “Estimate Export Plan” option) to confirm the engine now detects at least one non-partition output column before committing a full run.
  • Monitor the SQL Server Error Log (Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\ERRORLOG) to ensure Error 11571 no longer appears.

Alternative or Verification Steps

  • Run sys.dm_exec_describe_first_result_set against your export query to confirm at least one column is flagged as a standard output column rather than a partition key.
  • If the error persists, temporarily disable partitioning entirely (PARTITION_COLUMNS = NULL) to isolate whether the issue is in the export logic or a deeper metadata corruption in the source table’s column properties.