Yes when the package is run as a job, the majority of the
packages run using the script below, 3 of the packages do
not run, and no errors occurs.

I have isolated one of the packages the section of script
to call it, created a new package with a connection to the
server and the activex script as below, and a new job and
tried this with the existing package that does the loading
and a new recreated package.

Again the jon completes successfully but none of the steps
appear to have been run.

I have even inlcuded the GUID of the package and version
in the below script, the first time it errored due to me
not including the curly brackets, second time it ran
reporting no errors.

The steps in the package doing the loading, first log an
entry in a table stating the time the package started
running, the second step is to truncate the destination
table, and the third is to transfer the data about 300,000
rows from an Oracle database which should take circa 10
mins to run, but the job completes in seconds !!

I hope this helps as I have just about run out of things
to try.

Further more the job is owned by sa, a member of sysadmins.

The scripts are all in the same ActiveX control.

There is a problem (Believe it is on the KB) and I have seen it whereby the
job reports successful as do all the steps but in fact it should fail.

Try logging into the server as the SQL Server Agent account and executing
the package.

--


Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org

"Mark Phillips" <mark.phillips (AT) db (DOT) com> wrote