We created a simple batch file that launches a Visual Studio package, and then via Windows Task Scheduler we run this batch file each hour.
The Visual Studio package extracts data from a web service API, and pushes that data to MS SQL.
The content of the batch file is as follows:
"C:\Program Files\Microsoft SQL Server\150\DTS\Binn\DTExec.exe" /F "C:\SSIS Packages\MYOB_ARL_Import\Package.dtsx"
This command line has worked perfectly for the past year, however recently, it stopped working, and we believe there has been new policies/security applied to the server.
Now, no data is loaded into SQL when running the package via the batch file/task scheduler. If however, we open Visual Studio as Administrator and run the package, it executes perfectly.
We are happy to consider any resolution suggestion, whether trying to fix the current setup or using an alternate method for executing the Visual Studio package each hour.