We have a job that is using a foreach loop to grab input from a text file, perform some transformations and place it into a SQL Server database using OLE DB providers. The package works fine from the local environment (within Visual Studio).
Then when you import the package from the file system into the MSDB package store, it works fine from there as well.
The problem is when we try to schedule the job using the SQL Server Agent. It is a one step job and it says its successful when we run it, but it doesn't put any information into the database itself. We have other packages running that are working
that run from the package store and take information from one database and put it into the same SQL Server DB we are trying to put our text file information into.
Has anyone encountered the problem where the package works from the file system as well as the package store, but doesn't work when you schedule it as a job?
View Complete Post