We have a SQL Server Agent Job set up to run a package from the MSDB Stored Package. That package runs a SSIS project (ETL). The job is scheduled to run daily. When the job runs, it reports back as a success, but the SQL tables are empty. If we run the SSIS ETL or the MSDB package manually, the tables are populated.
The SQL Job is complaining about a wrong file type for the connection manager. The connection manager "LocalHost.CMD" is for a SQL database on the same server as SSIS. We have always used OLE DB as the connection type. "CMD" is a database, not a file. Any ideas?
This is the results of the SQL job.
Executed as user: CMDANALYTICS\mzuniga. Microsoft (R) SQL Server Execute Package Utility Version 11.0.6020.0 for 32-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 10:02:49 AM Error: 2019-10-29 10:02:50.46 Code: 0xC020801E Source: HubspotDealsV2 Log provider "{9156B21A-F4FE-4643-8916-BDA41A6FDFF5}" Description: The connection manager "LocalHost.CMD" is an incorrect type. The type required is "FILE". The type available to the component is "OLEDB". End Error Error: 2019-10-29 10:02:52.13 Code: 0xC020801E Source: HubspotDealsV2 Log provider "{9156B21A-F4FE-4643-8916-BDA41A6FDFF5}" Description: The connection manager "LocalHost.CMD" is an incorrect type. The type required is "FILE". The type available to the component is "OLEDB". End Error DTExec: The package execution returned DTSER_SUCCESS (0). Started: 10:02:49 AM Finished: 10:02:54 AM Elapsed: 4.836 seconds. The package executed successfully. The step succeeded.