I have two DTS local packages that have been running fine as scheduled jobs
for years. Suddenly one of them is creating an empty output file while the
other one functions normally.

What's mysterious (at least to me) is that the one that creates the empty
file only does so when it's running as a scheduled job. If I right-click on
the job in Enterprise Manager and do a "Start Job", it creates the file as
expected.

Anyone have any ideas that would address this scenario?
--
Art Cabot
Director, Information Technology
Sizemore, Inc.

Hi Art,

Usually when a job behaves differently when scheduled vs manually run,
it is due to permission differences between the SQL Agent service
account (which runs the scheduled job) and your personal account
(which runs the job manually).

Have any permissions been modified recently?

Good luck!
J

Hi Art,

Usually when a job behaves differently when scheduled vs manually run,
it is due to permission differences between the SQL Agent service
account (which runs the scheduled job) and your personal account
(which runs the job manually).

Have any permissions been modified recently?

Good luck!
J

Hi Art,

Usually when a job behaves differently when scheduled vs manually run,
it is due to permission differences between the SQL Agent service
account (which runs the scheduled job) and your personal account
(which runs the job manually).

Have any permissions been modified recently?

Good luck!
J

Hi Art,

Usually when a job behaves differently when scheduled vs manually run,
it is due to permission differences between the SQL Agent service
account (which runs the scheduled job) and your personal account
(which runs the job manually).

Have any permissions been modified recently?

Good luck!
J

Hi Art,

Usually when a job behaves differently when scheduled vs manually run,
it is due to permission differences between the SQL Agent service
account (which runs the scheduled job) and your personal account
(which runs the job manually).

Have any permissions been modified recently?

Good luck!
J

Hi Art,

Usually when a job behaves differently when scheduled vs manually run,
it is due to permission differences between the SQL Agent service
account (which runs the scheduled job) and your personal account
(which runs the job manually).

Have any permissions been modified recently?

Good luck!
J

Hi Art,

Usually when a job behaves differently when scheduled vs manually run,
it is due to permission differences between the SQL Agent service
account (which runs the scheduled job) and your personal account
(which runs the job manually).

Have any permissions been modified recently?

Good luck!
J

Hi Art,

Usually when a job behaves differently when scheduled vs manually run,
it is due to permission differences between the SQL Agent service
account (which runs the scheduled job) and your personal account
(which runs the job manually).

Have any permissions been modified recently?

Good luck!
J