RE: dts package error
- From: "Donna Lambert" <DonnaLambert@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 9 May 2005 07:47:59 -0700
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.
> What can I do to resolve this
.
- Follow-Ups:
- RE: dts package error
- From: Cynthia
- RE: dts package error
- References:
- dts package error
- From: Cynthia
- dts package error
- Prev by Date: Re: Schedule Error CmdExec
- Next by Date: Re: Schedule Error CmdExec
- Previous by thread: RE: dts package error
- Next by thread: RE: dts package error
- Index(es):
Relevant Pages
|