DTS Logs and Scheduled Jobs

#1

I have a scheduled job which run two dts packages in succession. Both
packages are set up to log to sql server and do so if I run the package
from enterprise manager. If I run the packages from the job, the job logs
show that the package steps completed successfully, however there are no
step logs for the packages. Anyone know how to force the package to start
logging or why it's not currently?

We are using SQL2000 and VB6.

Dave Phelan
Pitman

#2

Whilst i have not seen your problem make sure that your

SQL Server Agent service Account: if the job owner is a sysadmin, has rights
to the SQL Server for logging
Proxy Accout: if job is not owned by a sysadmin, has rights to log to the
SQL Server for logging.

If everything still appears OK then log in as either the Agent service
account or the proxy account and no try executing the package.

Have a read as well of this

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

--
--

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

"David Phelan" <dphelan (AT) nopitmanspam (DOT) com> wrote

Quote:

I have a scheduled job which run two dts packages in succession. Both
packages are set up to log to sql server and do so if I run the package
from enterprise manager. If I run the packages from the job, the job logs
show that the package steps completed successfully, however there are no
step logs for the packages. Anyone know how to force the package to start
logging or why it's not currently?

We are using SQL2000 and VB6.

Dave Phelan
Pitman

#3

Ok Let me have a hook.

I created a Package

1* DataPump task

In package properties i set it to log to my local server

I clear all previous invocations

I schedule the package

Package fires

It look in MSDB and a row has been added to sysdtssteplog.

What kind of steps do you have ?

--
--

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

"David Phelan" <dphelan (AT) nopitmanspam (DOT) com> wrote

Quote:

I checked through the security on the server. The job is owned by the
administrator and the administrator is set up as a sysadmin. I added the
administrator account to the MSDB owners list, gave exec permissions to
logging stored procs, and ran the job. I recreated the dtsrun command
lines
for the job to make sure it was applying the right user information.
Still, no log files were created. I can get the log files for the job
without problem, just not for the steps in the packages.

Dave

"Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote in
news:eqgPxE6VEHA.2844 (AT) TK2MSFTNGP09 (DOT) phx.gbl:

Whilst i have not seen your problem make sure that your

SQL Server Agent service Account: if the job owner is a sysadmin, has
rights to the SQL Server for logging
Proxy Accout: if job is not owned by a sysadmin, has rights to log to
the SQL Server for logging.

If everything still appears OK then log in as either the Agent service
account or the proxy account and no try executing the package.

Have a read as well of this

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

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

DTS Logs and Scheduled Jobs

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts

DTS Logs and Scheduled Jobs - 06-21-2004 , 09:26 AM

Re: DTS Logs and Scheduled Jobs - 06-21-2004 , 10:03 AM

Re: DTS Logs and Scheduled Jobs - 06-21-2004 , 01:34 PM