SSIS packages fails to run

Question

SSIS package "W:\SSIS\210805\Packages[PROD] Other Packages[PROD] Other Packages\REFERENCE_S_DESCRIPTION_RAW.dtsx" starting. Information: 0x4004300A at Data Flow Task 1, SSIS.Pipeline: Validation phase is beginning. Error: 0xC0202009 at REFERENCE_SCENARIO_IMPORT_TO_SCENARIO_DESCRIPTION_RAW, Connection manager "SourceConnectionExcel": SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft Access Database Engine" Hresult: 0x80004005 Description: "SSIS package "W:\SSIS\210805\Other\xlsx\Reference Scenario.xlsx' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.". Error: 0xC020801C at Data Flow Task 1, Source - Reference$ [41]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "SourceConnectionExcel" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. Error: 0xC0047017 at Data Flow Task 1, SSIS.Pipeline: Source - Reference$ failed validation and returned error code 0xC020801C. Error: 0xC004700C at Data Flow Task 1, SSIS.Pipeline: One or more component failed validation. Error: 0xC0024107 at Data Flow Task 1: There were errors during task validation. SSIS package "W:\SSIS\210805\Packages[PROD] Other Packages[PROD] Other Packages\REFERENCE_S_DESCRIPTION_RAW.dtsx" finished: Failure. The program '[31440] DtsDebugHost.exe: DTS' has exited with code 0 (0x0).

Answer 1

"SSIS package "W:\SSIS\210805\Other\xlsx\Reference Scenario.xlsx' is not a valid path.

As the error message says, so check path & filename. Is W: a NAS share mapped as drive in your profile? Then a SQL Server-Agent job can't access drive W:, use UNC share instead.

Answer 2

Hi @75316285,

Description: "SSIS package "W:\SSIS\210805\Other\xlsx\Reference Scenario.xlsx' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.

Please make sure:

• Machine were SQL Server is installed has access to path
• User on which SSIS is running has access rights to the file

Regards，

Zoe Hui

---

If the answer is helpful, please click "Accept Answer" and upvote it.