We are already able to import manually an Excel file into our SQL Server, but we want to try to import it automatically now, by creating a SSIS package and a job, like shown in this blog post: https://www.wiseowl.co.uk/blog/s231/schedule_data_import_in_sql_server_pt1.htm?fbclid=IwY2xjawFLkLhleHRuA2FlbQIxMAABHVL5aaLgsMlrbkEBtfzW-JIeJF3hFRRm5ESq4FX5UjoYFwtdL6HOc0fL8A_aem_wTG51Sheg-UHK_9tqcs-oA )

But I still have a problem when I want to run the job. The error is:

Executed as user: DWHSYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 16.0.1000.6 for 32-bit Copyright (C) 2022 Microsoft. All rights reserved. Started: 8:41:24 PM Error: 2024-09-13 20:41:27.38 Code: 0xC0202009 Source: TEST_IMPORT_2 Connection manager “SourceConnectionExcel” Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: “Microsoft JET Database Engine” Hresult: 0x80004005 Description: “‘V:XXXXX.xls’ 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.”. End Error Error: 2024-09-13 20:41:27.38 Code: 0xC020801C Source: Data Flow Task 1 Source – CL$ [51] Description: 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. End Error Error: 2024-09-13 20:41:27.38 Code: 0xC0047017 Source: Data Flow Task 1 SSIS.Pipeline Description: Source – CL$ failed validation and returned error code 0xC020801C. End Error Error: 2024-09-13 20:41:27.38 Code: 0xC004700C Source: Data Flow Task 1 SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2024-09-13 20:41:27.38 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: 8:41:24 PM Finished: 8:41:27 PM Elapsed: 2.812 seconds. The package execution failed. The step failed.

At the beginning I had a problem about 32/64bit, and in my job I checked the box “use 32 bit runtime”. And I think this already resolved partially. The SQL Server on its own doesn’t have Excel installed, but I read online that it is possible without it?