Colette, I know Allan Mitchell is already helping you but I just wanted to
let you know that I experienced the same problem as you. If I ran the package
manually, it ran fine. But when I ran the package using the scheduler, it did
not produce the desired result even though the package appeared to complete
successfully.
If I may ask, what does your package do and what is the desired
final result of your package? Thank you.
[quoted text, click to view] "Colette" wrote:
> I have a job set up to execute a local package automatically daily at a
> scheduled time. After the job fires, the status indicates it ran
> successfully but when you verify what it was supposed to do, it shows nothing
> happened. The job history step details show:
>
> Executed as user: (domain)\(account). ...ons ('/?' shows this screen; '-'
> May be substituted for '/'): Package retrieval: /~S Server Name
> /~U User Name /~P Password /E <Use trusted connection
> instead of /U /P> /~N Package Name /~M Package Password /~G
> Package Guid String /~V Package Version Guid String /~F
> Structured Storage UNC filename (overwritten if /S also specified) /~R
> Repository Database Name <uses default if blank; loads package from
> repository database> Package operation (overrides stored Package
> settings): /~A Global Variable Name:typeid=Value <may quote entire
> string (including name:typeid)> /~L Log file name /~W Write
> Completion Status to Windows Event Log <True or False> DTSRun action
> (default is to execute Package): /!X <Do not execute; retrieves Package
> to /F filename> /!D <Do not execute; drop package from SQL Server
> (cannot drop from Sto... Process Exit Code 0. The step succeeded.
>
> What does this mean? When I execute the local package manually, everything
> works fine. Any help would be greatly appreciated.
>
> Thanks.
>
