Share via

SQL Agent job errors but package runs fine in Visual Studio 2019 ssis SQL Server 2019 Cannot create a task from XML for task due to error 0x80070057 "The parameter is incorrect.".

lmsparkle 41 Reputation points
2020-11-06T22:36:38.43+00:00

I have looked at many posts about this and have found multiple resolutions.

I have created a package from scratch in Visual Studio 2019 and the target server version is SQL Server 2019.

There is only one task in the package for testing. It runs fine from the designer, but not from the job. Here is the error:
Code: 0xC001F02A Description: Cannot create a task from XML for task due to error 0x80070057 "The parameter is incorrect.". Code: 0xC0010018

In the past, when we'd see this error it was because we had the wrong target server version. This is 2019 pointing to 2019. I have changed it to other versions and it still does not work on the 2019 SQL Server. If I run it via a job on a 2016 server, change the SQL Server version to 2016 all is well.

Is this a Visual Studio 2019 version issue? SQL Server 2019 issue?

Visual Studio Community 2019 v 16.7.3
SQL Server Integration Projects v 3.9

SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,705 questions
SQL Server | Other
Accepted answer
  1. Monalv-MSFT 5,926 Reputation points
    2020-11-09T03:24:04.57+00:00

    Hi @lmsparkle ,

    Could you please check the version of integration services in SQL Server Configuration Manager?

    Please refer to the following link:
    How to find version of installed SSIS

    Best Regards,
    Mona

    ----------

    If the answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
    Hot issues in October--Users always get connection timeout problem when using multi subnet AG via listener. Especially after failover to another subnet.

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. lmsparkle 41 Reputation points
    2020-11-09T17:08:25.74+00:00

    Mona's idea worked for us. Thank you!

    We did not have the actual Integration Services service installed. We did not think we needed it as some of our servers do not have it installed. But those servers only run SQL Server-to-SQL Server type packages. These other packages were failing on other kinds of tasks.

    To make things more clear, Microsoft should use an error more like what I got for a different issue:
    Source: Create Year Folder Description: To run a SSIS package outside of SQL Server Data Tools you must install Standard Edition (64-bit) of Integration Services or higher. That is an obvious message.

    3 people found this answer helpful.
    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.