I wrote a simple vb.net program to identify and track the number and
size of backup files for the default instance of SQL Server 2000 SP3
instance on a Windows 2000 Server.

This program is set up to run in a dts package. When a job that
executes the dts package runs, the vb.net program does not run and no
errors are reported. The only activity in profiler is exec
msdb..sp_get_dtspackage N'dts_PACKAGENAME', null, null

I had thought that the problem was within the program or the permissions
of the SQL Server Agent account. However, the program runs as expected
when I manually execute the dts package or double-click on the .exe file
while I am logged in with SQL Server Agent account.

Any thoughts as what I can check out next?



*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

That is good unless the job is not executing as the Agent Account. If the
job is not owned by a member of the sysadmin role then the package is
executed as the Agent Proxy Account.



--
--

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


"Mark Lane" <majalane (AT) hotmail (DOT) com> wrote

Thank you for your feedback.

Unfortunately the job is owned by a member of the sysadmin role.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!