Ssis-171 Review

# 3️⃣ Force package to run 64‑bit (most production servers)
$proj.PropertyGroup.Run64BitRuntime = "true"
$proj.Save($dtprojPath)
Write-Host "Run64BitRuntime = true"

If you must run 32‑bit (e.g., legacy Jet/ACE drivers), set it to false and also edit the SQL Agent job step:

EXEC msdb.dbo.sp_update_jobstep
    @job_name = N'MySSISJob',
    @step_id = 1,
    @subsystem = N'SSIS',
    @command = N'/ISSERVER "\SSISDB\MyFolder\MyProject\MyPackage.dtsx" /CHECKPOINTING OFF /X86';

# 1️⃣ Open the .dtproj in SSDT (or via command line)
$dtprojPath = "C:\SSIS\MyProject.dtproj"
# 2️⃣ Update the TargetServerVersion element
[xml]$proj = Get-Content $dtprojPath
$ns = @ msb = "http://schemas.microsoft.com/developer/msbuild/2003" 
$proj.Project.PropertyGroup.TargetServerVersion = "SQLServer2022"   # or 2019/2017
$proj.Save($dtprojPath)
Write-Host "TargetServerVersion set to SQLServer2022"

Tip: After changing, rebuild the project (msbuild MyProject.dtproj /p:Configuration=Release). SSIS-171

| Property | Value | |----------|-------| | Error Number | 171 | | Message (SQL Server 2019+) | “The package failed validation. The package contains a component that is not supported on the target platform.” | | Typical Source | Data Flow → OLE DB Source / Destination, ADO.NET, Script Component, or any custom component that was built for a different SSIS version/bitness. | | Why It Happens | The runtime engine (DTExec / SSIS Catalog) cannot locate, load, or run the component because of one (or more) of the following mismatches:
1. Version mismatch – component compiled for SSIS 2008/2012 but running on SSIS 2019+.
2. Bitness mismatch – 32‑bit component on a 64‑bit run‑time (or vice‑versa).
3. Missing assembly – DLL not present in the GAC or in the C:\Program Files\Microsoft SQL Server\150\DTS\Binn folder.
4. Platform target – the package was saved as “SQL Server 2008” (or an older version) but is being executed on a newer server that enforces “TargetServerVersion”. | | Impact | Package validation fails before any data moves. The package never starts, and the SSIS Catalog logs the error with severity 16. | # 3️⃣ Force package to run 64‑bit (most