Executing it manually though after logging in as the Agent account may give
- The site for all your DTS needs.
"Kevin Vogler" <kvogler@voglerandassociates.com> wrote in message
news:ublFDEu1DHA.2948@TK2MSFTNGP09.phx.gbl...
> I have set all the logins - server, agent, sqlserver, dts package owner
the
> same. The login also has appropriate rights on the other server with the
> Access db
>
> The only change has been installing EM 2000
>
> Kevin
> "Allan Mitchell" <allan@no-spam.sqldts.com> wrote in message
> news:Of%23bcjt1DHA.2680@TK2MSFTNGP11.phx.gbl...
> > I have seen this type of problem before where no errors were returned
and
> > nothing happened (in fact it should have failed because I made it so
that
> it
> > would)
> >
> > If you log in as the SQL Server Agent account and execute the package
> > manually what happens
> >
> >
> > --
> >
> > 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 Vogler" <kvogler@voglerandassociates.com> wrote in message
> > news:uM%23dSdt1DHA.4060@TK2MSFTNGP11.phx.gbl...
> > > No errors. Job log indicates success.
> > >
> > > Thanks
> > > Kevin Vogler
> > > "Allan Mitchell" <allan@no-spam.sqldts.com> wrote in message
> > > news:OASip5s1DHA.560@TK2MSFTNGP11.phx.gbl...
> > > > Can you remind me please of any errors you get
> > > >
> > > > --
> > > >
> > > > 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 Vogler" <kvogler@voglerandassociates.com> wrote in message
> > > > news:OcRpWgs1DHA.2872@TK2MSFTNGP09.phx.gbl...
> > > > > Thanks for the response.
> > > > >
> > > > > That said, the Agent proxy account has permissions on the other
> > server.
> > > > In
> > > > > fact nothing has changed but now the job won't run. Any
suggestions
> > for
> > > > > troubleshooting?
> > > > >
> > > > > Thanks
> > > > > Kevin Vogler
> > > > > "Allan Mitchell" <allan@no-spam.sqldts.com> wrote in message
> > > > > news:u05vtco1DHA.1704@tk2msftngp13.phx.gbl...
> > > > > > Correct. The Agent account, if the job runs as a user in the
> > sysadmin
> > > > > role,
> > > > > > or the Agent Proxy Account, if the job runs as someone not in
the
> > > > sysadmin
> > > > > > role, must have permissions to go wherever you are directing
them.
> > > > > >
> > > > > > --
> > > > > >
> > > > > > 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 Vogler" <kvogler@voglerandassociates.com> wrote in
message
> > > > > > news:O5oWY8g1DHA.4060@TK2MSFTNGP11.phx.gbl...
> > > > > > > I finally got the jobs to run if I changed the owner of the
dts
> > > > packages
> > > > > > to
> > > > > > > the admin account and also set the job to run under 'self'
which
> > is
> > > > > > > different from the Agent account. However, one of the jobs
that
> > > > > connects
> > > > > > to
> > > > > > > another server and an Access mdb file still won't work
(reports
> > > > success
> > > > > > > though). My understanding is that the Agent account has to
have
> > > > > > permissions
> > > > > > > on the other server which it still does plus this worked
before.
> > > I'm
> > > > > > really
> > > > > > > confused on that one. Any suggestions?
> > > > > > >
> > > > > > > Thanks in advance
> > > > > > > Kevin Vogler
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>