Hello all

I included a dynamic properties task in my packages in order to dynamically set the package logging properties based on a .ini file. Unfortunately, while this dynamic logging works when I execute the task from Enterprise Manager, it does not work when the package is executed from a SQL Server Agent job. Has anyone seen similar behavior or have any thoughts on how I might fix this problem

Thanks
Kevin

What happens?
Does it not change the location?
To where are you logging?

Could it be a permissions problem. Easily checked by logging in as the SQL
Server Agent service account.


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


--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.allisonmitchell.com - Expert SQL Server Consultancy.
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


"Kevin" <kwm2b (AT) hotmail (DOT) com> wrote

Unfortunately, while this dynamic logging works when I execute the task from
Enterprise Manager, it does not work when the package is executed from a SQL
Server Agent job. Has anyone seen similar behavior or have any thoughts on
how I might fix this problem?

Hello Allan

The location simply does not change. It logs, it just logs to whatever server to which it was logging when the package was saved. It doesn't seem like a permissions problem, since the user that executes has permissions on all servers

Any other thoughts out there

Kevi

----- Allan Mitchell wrote: ----

What happens
Does it not change the location
To where are you logging

Could it be a permissions problem. Easily checked by logging in as the SQ
Server Agent service account


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


--

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


"Kevin" <kwm2b (AT) hotmail (DOT) com> wrote in messag
news:C76177AF-3E23-46C7-8B14-1E1C9E60CB73 (AT) microsoft (DOT) com..
Unfortunately, while this dynamic logging works when I execute the task fro
Enterprise Manager, it does not work when the package is executed from a SQ
Server Agent job. Has anyone seen similar behavior or have any thoughts o
how I might fix this problem

By the user I presume you mean the SQL Agent Service Account as that is what
is being used when you schedule the package(if user owning the job is in the
sysadmin role)/Proxy account(if not). If the service account is the SYSTEM
account then this cannot see past it's own HDD.

Easy way to find out?

If the job owner is a member of the sysadmin role log in as the Agent
Service account, if not as the Proxy account. Now try to run the package
manually.

--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.allisonmitchell.com - Expert SQL Server Consultancy.
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


"Kevin" <kwm2b (AT) hotmail (DOT) com> wrote

like a permissions problem, since the user that executes has permissions on
all servers.

Allan,

I believe I know what happens in this case. The package begins logging before any tasks / steps can be executed. Therefore, while the dynamic properties task does change the logging information, logging has already begun and it is too late to change.

Thanks for the help.

Kevin

You cannot change the package log file from inside the package for the
current execution as by definition the package has to have started for it to
run your task and therefore logging should be running.



--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.allisonmitchell.com - Expert SQL Server Consultancy.
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


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

properties task does change the logging information, logging has already
begun and it is too late to change.