Avatar of Bill Park
Bill Park
Flag for United States of America asked on

SSIS project runs OK within Visual Studio, fails using DTExecUI

This is my first attempt at a Visual Studio SSIS project.
It works OK and produces the expected output to SQL tables when I run within Visual Studio.
It fails without any output to SQL tables when I run the dtsx from DTExecUI.
How should I approach this?
Visual Studio Enterprise 2019
DTExecUI Version 2.0
SQL Server Microsoft SQL Server 2019 (RTM-GDR) (KB4583458) - 15.0.2080.9 (X64)   Nov  6 2020 16:50:01   Copyright (C) 2019 Microsoft Corporation  Developer Edition (64-bit) on Windows 10 Pro 10.0 <X64> (Build 19042: ) (Hypervisor)
I've attached a screenshot of the Package Execution Progress from DTExecUI.
The debug output from Visual Studio,
and the dtsx file.

Thank you.

* DTEXECSSISMicrosoft Visual StudioSQLDatabases

Avatar of undefined
Last Comment
Raja Jegan R

8/22/2022 - Mon
Raja Jegan R

I've encountered this error before when using Visual Studio 2019 and using SQL Server 2016.
If there is a difference between Visual Studio and SQL Server version, then the package will run from SSDT or Visual Studio but won't execute as a Job or from outside and the solution to fix this is to change the Target Server version property in SSIS by following the steps below: (Don't have access to SSDT and hence guessing the steps)
1. In SSDT or Visual Studio, open your Solution and Right Click on your project and choose Properties.
2. Under Configuration properties, you can see a property named TargetServerVersion and change it to match your SQL Server version like 2014 or 2016 or 2017 and your package execution would work fine.
Bill Park

Thank you but no, the TargetServerVersion was set to SQL Server 2019.
Bill Park

View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
Raja Jegan R

Glad to hear you have resolved it out..
Error message you raised in the question and the one in screenshot seems different.
Yes, to resolve the error in the snapshot "the runtime connection manager with the id cannot be found" you would need to map all the connection managers properly as you have exlained..
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy