December 20, 2024 at 7:02 pm
I recently created an SSIS package and then converted it to a Package Deployment Model. I have the configuration file all set and placed in the same folder as my .dtsx package that I grabbed from the bin\Debug folder. When I run my project in SSIS, it runs without any issues over and over again.
I now have a batch file that calls cd /d C:\Program Files\Microsoft SQL Server\150\DTS\Binn and then it calls "dtexec C:\Temp\ProjectName.dtsx"
The project launches but fails as soon as it gets to my "Execute Process Task" where I pass a project parameter value that is in the ProjectName.dtsConfig file located also in C:\Temp. The error message I get is as follows:
Error: 2024-12-20 13:48:45.31
Code: 0xC001F02A
Source: foreach_FileList
Description: Cannot create a task from XML for task "ept_ProcessTask1", type "Microsoft.ExecuteProcess" due to error 0x80070057 "The parameter is incorrect.".
End Error
Error: 2024-12-20 13:48:45.31
Code: 0xC0010018
Source: ept_ProcessTask1
Description: Failed to load task "ept_ProcessTask1", type "". The contact information for this task is "".
End Error
I am stuck and I am not sure how to proceed. Has anyone encountered this issue previously? I have SSIS installed on my computer and I can run the package from the SSIS without any issues.
Your help is greatly appreciated.
Owen
Owen White
December 21, 2024 at 4:42 am
You have set things up using the legacy method of deployment. Have you done this deliberately? If not, please consider deploying your packages to SSISDB and configuring parameters using SSISDB environment variables.
Also, why not run the package from SQL Agent?
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
December 21, 2024 at 5:51 am
Phil,
Thank you for your response. I actually found out that I did not have integration services for SQL 2019 (150) installed. After running the SQL features discovery tool, I found that I had integration services for SQL 2016 (140). Once I installed the updated integration services, everything worked as planned.
Prior to today, I did not even know about the dtexec method. I thought you had to run from SSISDB inside of a SQL instance. I am doing a project for someone else and I provided the customer with the .ispac and they stated: No, no, no, we run our dtsx packages from the command line using a batch file. The batch file is then run using scheduler. This caused me to have to change my SSIS project to a Package Deployment Model which required me to move all of my Project Connections and Project Parameters inside of the package. This did not make me happy but after a couple of hours of moving all of my variables (in a branched version of my code), I had a working model using the package deployment and a project deployment model.
Now I have two options to provide to my customers depending on the sophistication level.
Thank you for your response!
Owen
Owen White
December 21, 2024 at 7:10 am
That all makes sense! Thanks for explaining and well done on solving it.
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply