SSIS Package Failing when called through DTExec - fine through VS - ssis

Question

I have an SSIS package that is running fine when I press the "Start" button in VS, but when I run it via DTExec, it's bombing part way through with the following errors.
Error: 2020-06-10 13:47:20.22
Code: 0xC0047038
Source: JCMAST to SQL SSIS.Pipeline
Description: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on JCMAST - WA returned error code 0x80004005. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
End Error
Error: 2020-06-10 13:47:20.49
Code: 0xC0047022
Source: JCMAST to SQL SSIS.Pipeline
Description: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Co, Job Yesterday Sort" (47) failed with error code 0xC0047020 while processing input "Sort Input" (50). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.
End Error
I can see that the package is called properly, as I can see all of the different validation and pre-execution steps. These are the only errors that come up in the entire run.
Everything that I've Googled so far with these errors typically come with some sort of additional error. Not the case here.
What's so confusing to me is why it would run manually, but not through cmd.
EDIT: Full error output
Started: 2:55:09 PM
Error: 2020-06-10 14:55:14.35
Code: 0xC0047038
Source: JCMAST to SQL SSIS.Pipeline
Description: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on JCMAST - WA returned error code 0x80004005. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
End Error
Error: 2020-06-10 14:55:14.64
Code: 0xC0047022
Source: JCMAST to SQL SSIS.Pipeline
Description: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Co, Job Yesterday Sort" (47) failed with error code 0xC0047020 while processing input "Sort Input" (50). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.
End Error
Error: 2020-06-10 14:55:20.67
Code: 0xC0047038
Source: EMP Files to SQL SSIS.Pipeline
Description: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on PREMP - WA returned error code 0x80004005. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 2:55:09 PM
Finished: 2:55:34 PM
Elapsed: 24.343 seconds
SSIS package "D:\SafetyServicesProjects\WebAppsTest2\WebAppsTest2\Package.dtsx" starting.
Information: 0x4004300A at Data Flow Task, SSIS.Pipeline: Validation phase is beginning.
Information: 0x4004300A at Data Flow Task, SSIS.Pipeline: Validation phase is beginning.
Warning: 0x80049304 at Data Flow Task, SSIS.Pipeline: Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator, or on the system's console.
Information: 0x40043006 at Data Flow Task, SSIS.Pipeline: Prepare for Execute phase is beginning.
Information: 0x40043007 at Data Flow Task, SSIS.Pipeline: Pre-Execute phase is beginning.
Information: 0x4004300C at Data Flow Task, SSIS.Pipeline: Execute phase is beginning.
Error: 0xC0047038 at Data Flow Task, SSIS.Pipeline: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on ODBC Source returned error code 0x80004005. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
Information: 0x40043008 at Data Flow Task, SSIS.Pipeline: Post Execute phase is beginning.
Information: 0x4004300B at Data Flow Task, SSIS.Pipeline: "OLE DB Destination" wrote 0 rows.
Information: 0x40043009 at Data Flow Task, SSIS.Pipeline: Cleanup phase is beginning.
Task failed: Data Flow Task
Warning: 0x80019002 at Package: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "D:\SafetyServicesProjects\WebAppsTest2\WebAppsTest2\Package.dtsx" finished: Failure.

Answer 1

Well. Figured it out.
Turns out it all came down to versioning. I was using a version of IBM iAccess ODBC that had issues with Windows 10. Upgraded to the latest version and it worked.