The creator of the job has very little to do with it. It has to do with
who owns the job and what role they play on the server.
Sysadmin - jobs are executed with the SQL Server Agent account
! sysadmin - jobs are executed using the proxy account
Log on to the server as one of these accounts (the one that would be
used) and try to execute the job now.
Have passwords changed? If you used the /U and /P to log on when
creating the job then this may have changed but you would not
immediately see it because of the ~/Z syntax
Have a look at generating the cmdline using DTSRUNUI.
Allan
[quoted text, click to view] "jaylou" <jaylou@discussions.microsoft.com> wrote in message
news:jaylou@discussions.microsoft.com:
> Thanks for the link.
>
> The problem is that I am not getting error messages and this article is
> talking about security. I create the job using the DTS wizard directly on
>
> the server that is running it. So I don't think it has anything to do
> with
> securities. I log onto the server thru Terminal server and create and
> schedule the package. It works fine if I right click on the job and click
>
> start.
>
> You are saying the error is not buibbling up, do you know of a place where
> I
> can look to see the execution after the fact?
> Thanks again,
> Joe