How to fix error in running of .DTSX file

Jerome C. Espenilla 20 Reputation points
2025-10-07T10:27:18.56+00:00

Message

Executed as user: HRPROWSIDB\SYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 10.50.6560.0 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 6:12:38 PM Error: 2025-10-07 18:12:38.27 Code: 0xC0202009 Source: ExportToCSV Connection manager "HRPROWSIDB\HRPROWSI.DBHRPRO_2e.sa" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E4D Description: "Login failed for user 'sa'.". End Error Error: 2025-10-07 18:12:38.27 Code: 0xC020801C Source: Export to CSV Source Data (Generate SM Vendor Portal DTR Connection) [1] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "HRPROWSIDB\HRPROWSI.DBHRPRO_2e.sa" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2025-10-07 18:12:38.27 Code: 0xC0047017 Source: Export to CSV SSIS.Pipeline Description: component "Source Data (Generate SM Vendor Portal DTR Connection)" (1) failed validation and returned error code 0xC020801C. End Error Error: 2025-10-07 18:12:38.27 Code: 0xC004700C Source: Export to CSV SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2025-10-07 18:12:38.27 Code: 0xC0024107 Source: Export to CSV Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 6:12:38 PM Finished: 6:12:38 PM Elapsed: 0.125 seconds. The package execution failed. The step failed.

SQL Server Integration Services
{count} votes

Answer accepted by question author
  1. Erland Sommarskog 127.4K Reputation points MVP Volunteer Moderator
    2025-10-07T21:19:08.3766667+00:00

    I see something about "Login failed for user 'sa'.". I guess that is the root of your problem. You will need to make sure that you have the correct password for sa.

    Although, running an SSIS package as sa does not sound like a wise idea to me. The package should run with a login with lesser permissions.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

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