August 4, 2004 at 6:46 am
I have a DTS package when I execute it manually it runs fine importing all my data from .dbf files. As a scheduled job it shows it successful but in the job history I have the following: "The step did not generate any output. Process Exit Code 0. The step succeeded." Therefore none of my .dbf files import so no records that have been changed are updated. I am running the job under my name and have sysadmin rights and all permissions for the table that I'm importing into. Does anybody know why is it not updating the records as a scheduled job but will manually?
August 4, 2004 at 12:01 pm
I could be a permissions problem since a scheduled job runs under the SQL Server Agent login rather than your login.
Enable Package logging in the package properties to get more details about what happens in the package when it executes.
Greg
Greg
August 5, 2004 at 10:35 am
You might also try running manually on the server. It could be a missing driver or drive mapping or something simple like that. When you run on your local machine, it is using the local machine's resources (drivers, drive mappings, ODBC data sources etc...) When you run on the server you are using the server's resources. So for example, if you are loading data from the E: drive, the server must have the E: drive mapped to the appropriate location.
Good Luck!
August 9, 2004 at 2:22 pm
Greg and dlink are the right place to start. Always the best way to troubleshoot the DTS pakcage is to log in as SQL ServerAgent account on the server and run it from there.
That always did the trick so far..
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply