Re: Scheduled DTS package fails even when SQLSERVERAGENT logs on as ow

And in what DB role on SQL Server is domain\user1?

Remember if they are not in the sysadmin role the job will execute under the
proxy account

http://support.microsoft.com/default.aspx?scid=kb;en-us;269074&sd=tech

--



Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know


"Mark Pea***" <fbmarkp@xxxxxxxxxxxxxxxx> wrote in message
news:DB4B13F8-39A6-4A68-9358-6387C9F9D2D7@xxxxxxxxxxxxxxxx
>
> Successful DTS package fails when scheduled as a SQL Agent job.
>
> The package runs only one ActiveX script, which makes a call to a COM DLL
> that uses DAO to run read-only queries against an Access 2000 .mdb file
> with
> workgroup security.
>
> Domain\user1 is assigned to the workgroup, and has full NTFS file and
> folder
> permissions.
>
> The DTS package owner is domain\user1;
> the Agent job owner is domain\user1;
> the SQLSERVERAGENT service logs on as domain\user1.
>
> SQL Agent security context can write files to the same folder as the .mdb
> file.
>
> All paths involved are confirmed UNCs.
>
> Have I missed something? With these security settings, what's the
> difference
> between Agent and DTS security context as far as Access is concerned?
>
> Thank you.


.