WhenEVER something works when kicked off manually, but fails through
scheduler...suspect a permissions issue. When scheduled the package runs
under the context of the SQL Agent account. Does the SQL agent account have
rights to the directory that the file is in? Is SQL Agent even RUNNING under
an account, or is it running under local system? Is the mdb on another
server? If so, and the Agent is running under Local System, you'll either
have to make sure you are running in an Active Directory and you've given the
SQL server Machine account rights to the share and directory...or you will
have to change SQL Agent to use a domain account.
If SQL Agent is already starting under a user account, log in with that
account and try to manually kick off the package.
Also, turn on package logging (right click the background in designer,
package properties, logging tab...error handling).
Sorry if this seems like a lot of info.
Let us know what you find out
Donna Lambert
[quoted text, click to view] "Cynthia" wrote:
> created package through sql using the all tasks extract info selected a
> mdb file on my server. then asked this to create a dts package and
> scheduled it for once a week. when I run it manually I have no problem.
> When it runs through the scheduler it cannot find the mdb file on the server.
I need to get with our IT to find out about permissions, and if it is running
under an account or locat system. I do know that it is running on a
different server. Someone suggest I use a script for what I am doing, but I
do not know how to even begin to do that. I am trying to populate an access
database on a different server with information on my SQL once a week. It is
to keep our client uptodate without having access to our SQL. I appreciate
your help and will let you know if I get it working.
[quoted text, click to view] "Donna Lambert" wrote:
> WhenEVER something works when kicked off manually, but fails through
> scheduler...suspect a permissions issue. When scheduled the package runs
> under the context of the SQL Agent account. Does the SQL agent account have
> rights to the directory that the file is in? Is SQL Agent even RUNNING under
> an account, or is it running under local system? Is the mdb on another
> server? If so, and the Agent is running under Local System, you'll either
> have to make sure you are running in an Active Directory and you've given the
> SQL server Machine account rights to the share and directory...or you will
> have to change SQL Agent to use a domain account.
>
> If SQL Agent is already starting under a user account, log in with that
> account and try to manually kick off the package.
>
> Also, turn on package logging (right click the background in designer,
> package properties, logging tab...error handling).
>
> Sorry if this seems like a lot of info.
> Let us know what you find out
> Donna Lambert
>
> "Cynthia" wrote:
>
> > created package through sql using the all tasks extract info selected a
> > mdb file on my server. then asked this to create a dts package and
> > scheduled it for once a week. when I run it manually I have no problem.
> > When it runs through the scheduler it cannot find the mdb file on the server.
Donna,
IT fixed the permissions, now I get an error that the database is opened by
another user. No one else has access to the directory where the mdb file is?
Cynthia
[quoted text, click to view] "Donna Lambert" wrote:
> WhenEVER something works when kicked off manually, but fails through
> scheduler...suspect a permissions issue. When scheduled the package runs
> under the context of the SQL Agent account. Does the SQL agent account have
> rights to the directory that the file is in? Is SQL Agent even RUNNING under
> an account, or is it running under local system? Is the mdb on another
> server? If so, and the Agent is running under Local System, you'll either
> have to make sure you are running in an Active Directory and you've given the
> SQL server Machine account rights to the share and directory...or you will
> have to change SQL Agent to use a domain account.
>
> If SQL Agent is already starting under a user account, log in with that
> account and try to manually kick off the package.
>
> Also, turn on package logging (right click the background in designer,
> package properties, logging tab...error handling).
>
> Sorry if this seems like a lot of info.
> Let us know what you find out
> Donna Lambert
>
> "Cynthia" wrote:
>
> > created package through sql using the all tasks extract info selected a
> > mdb file on my server. then asked this to create a dts package and
> > scheduled it for once a week. when I run it manually I have no problem.
> > When it runs through the scheduler it cannot find the mdb file on the server.
Don't see what you're looking for? Try a search.
