Hi,

just wondering whether anyone has had this experience as well and if so how
they've fixed it. It appears that a particular DTS package, scheduled as a
job refuses to run an 'Execute Package' task.

When the package is run in the context of the DTS designer it's fine - as
soon as it runs from a scheduled job it does not. I have checked that the
Execute Package task is pointing to the correct job and even the correct
version of that job, but the logs show that package finished executing at the
step before. No errors are returned.

Would appreciate any help that anyone could give on this one.

Is there a workflow constraint going to the Execute Package task?
Is that condtion being met fron the previous task?

Do you have package and Datapump logging enabled.

Packages as jobs and packages run from EM can be two different beasts

http://support.microsoft.com/?kbid=269074


--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com


"hubristicbob" <hubristicbob (AT) discussions (DOT) microsoft.com> wrote

Hi, Alan - thanks for the response.

there is a workflow precedent - 'on success' and I have package log enabled
as well - the log simply shows that the previous task exits successfully;
there is no mention of execute package task.

I have already checked the security for these packages as well, running them
from Enterprise manager on the server where the job is scheduled: the package
completed successfully.

"Allan Mitchell" wrote:

Running them from the server on which the Agent runs is not enough. You
need to be logged in as the account that will do the executing so either the
proxy account or the Agent account

--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.Konesans.com


"hubristicbob" <hubristicbob (AT) discussions (DOT) microsoft.com> wrote