SQL - DTEXEC.exe - Microsoft.SqlServer.PipelineXml.dll is properly registered

Eugen Buss 1 Reputation point
2022-07-01T11:05:38.627+00:00

Hello all,
I am currently stuck with the following problem:
I have created a package using the Import/ Export Wizard of MS SQL Management Studio (v18.12.1), which is supposed to copy tables from database A to database B. (on the same SQL instance).
I am also moving around a Windows Server 2019 which also has MS SQL Management Studio installed,
On another server, Windows Server 2019 is running MS SQL 2019 (15.0.4236.7).

If the package is run immediately, it works.

When the package is saved to the filesystem, and later run with DTEXEC.exe, I get the following error message:

Microsoft (R) SQL Server Execute Package Utility
Version 15.0.2000.229 for 32-bit
Copyright (C) 2019 Microsoft. All rights reserved.
Started: 12:08:46
Error: 2022-07-01 12:08:48.15
Code: 0xC0040019
Source: Data Flow Task 1 Data Flow Task 1 (SSIS.Pipeline)
Description: Data Flow objects cannot be loaded. Check if Microsoft.SqlServer.PipelineXml.dll is properly registered.
End Error
Error: 2022-07-01 12:08:48.16
Code: 0xC0010018
Source: Data Flow Task 1
Description: Failed to load task "Data Flow Task 1", type "SSIS.Pipeline.7". The contact information for this task is "Performs high-performance data extraction, transformation and loading;Microsoft Corporation; Microsoft SQL Server; (C) Microsoft Corporation; All Rights Reserved;http://www.microsoft.com/sql/support/default.asp;1".
End Error
Error: 2022-07-01 12:08:48.18
Code: 0xC001F02A
Source: Package3
Description: Cannot create a task from XML for task "Preparation SQL Task 1", type "Microsoft.ExecuteSQLTask" due to error 0x80070057 "Wrong parameter.
End Error
Error: 2022-07-01 12:08:48.18
Code: 0xC0010018
Source: Preparation SQL Task 1
Description: Failed to load task "Preparation SQL Task 1", type "". The contact information for this task is "".
End Error
Error: 2022-07-01 12:08:48.21
Code: 0xC0024107
Source: Data Flow Task 1
Description: There were errors during task validation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 12:08:46
Finished: 12:08:48
Elapsed: 1.937 seconds

It also makes no difference whether the package is stored on the file system or in the SQL Server.

The subsequent registration of the Microsoft.SqlServer.PipelineXml.dll with the following command:

regsvr32 "C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\CommonExtensions\Microsoft\SSIS\150\Binn\Microsoft.SqlServer.PipelineXML.dll".

brings the following error message:

Module C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\CommonExtensions\Microsoft\SSIS\150\Binn\Microsoft.SqlServer.PipelineXML.dll has been loaded, but the DllRegisterServer entry point was not found.
Make sure that C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\CommonExtensions\Microsoft\SSIS\150\Binn\Microsoft.SqlServer.PipelineXML.dll is a valid .DLL or .OCX file and repeat the procedure.

Could you please assist me in troubleshooting this!!?
In older versions it all worked fine.

Thank you very much and best regards

SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,703 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Yitzhak Khabinsky 26,586 Reputation points
    2022-07-01T14:27:37.747+00:00

    Hi @Eugen Buss ,

    It would be better to start using Integration Services Catalog and SSISDB.
    They are available starting from SQL Server 2012 onwards.

    creating-the-ssis-catalog
    introduction-to-the-ssis-catalog-database-ssisdb

    217023-ssis-database-and-catalog.png


  2. ZoeHui-MSFT 41,491 Reputation points
    2022-07-04T02:13:18.06+00:00

    Hi @Eugen Buss ,

    Please first make sure that version of dtexec.exe is same as your SQL Server.

    As said here, this issue is more likely to occur when the computer experiences high memory pressure.

    To work around this issue, do not run too many SSIS packages at the same time. For example, do not run several hundred SSIS packages at the same time.

    Regards,

    Zoe


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    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.


  3. Eugen Buss 1 Reputation point
    2022-07-04T06:24:40.673+00:00

    Does anyone else have any ideas what this could be?
    and thank you for the responses so far!

    Update - 06.07.2022

    I have now experimented a little further. It can be verified that in Management Studio v.18.x (buildnumber 15.0.x) the import/export function (with the DTSWizard and DTEXEC) no longer works properly. See messages from above. The last working version is the Management Studio v.17.9.1 (buildnumber 14.0.x). I have just tested it again and it works in my constellation.

    Microsoft (R) SQL Server Execute Package Utility
    Version 14.0.3026.27 for 32-bit
    Copyright (C) 2017 Microsoft. All rights reserved.

    Started: 08:58:27
    DTExec: The package execution returned DTSER_SUCCESS (0).
    Started: 08:58:27
    Finished: 08:58:29
    Elapsed: 1.688 seconds

    regards
    Eugen

    maybe the developers could check this again and fix it.

    THX


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.