DTS Package Not Running When Schedlued

I have been having a problem where I can not get a scheduled DTS pachkage t
o
run. It fails at all launch intervals. The Job can be launched manually and
it will import the data just fine. I am trying to import foxpro files into
the SQL server. Is this a permissions issue? What persmissions are passed
from SQL to the other server I am trying to import from?
Thanks
--
MitchTry granting permissions to the folder that contains the import FoxPro files
to the Windows account that the SQL Server and SQL Server Agent services are
starting under.
HTH
Jerry
"Mitchm" <Mitchm@.discussions.microsoft.com> wrote in message
news:4D64AB57-815C-4A91-87C2-9B5AFF3D26F5@.microsoft.com...
>I have been having a problem where I can not get a scheduled DTS pachkage
>to
> run. It fails at all launch intervals. The Job can be launched manually
> and
> it will import the data just fine. I am trying to import foxpro files into
> the SQL server. Is this a permissions issue? What persmissions are passed
> from SQL to the other server I am trying to import from?
> Thanks
> --
> Mitch|||Running from the scheduler, your DTS package is going to run under the
context of the user that SQL Agent is running under. Check the
properties of SQL Agent, see what user the service is running as. That
user needs to have access to the share that your Foxpro database is on.

DTS Package Not Running When Schedlued

I have been having a problem where I can not get a scheduled DTS pachkage to
run. It fails at all launch intervals. The Job can be launched manually and
it will import the data just fine. I am trying to import foxpro files into
the SQL server. Is this a permissions issue? What persmissions are passed
from SQL to the other server I am trying to import from?
Thanks
--
MitchTry granting permissions to the folder that contains the import FoxPro files
to the Windows account that the SQL Server and SQL Server Agent services are
starting under.
HTH
Jerry
"Mitchm" <Mitchm@.discussions.microsoft.com> wrote in message
news:4D64AB57-815C-4A91-87C2-9B5AFF3D26F5@.microsoft.com...
>I have been having a problem where I can not get a scheduled DTS pachkage
>to
> run. It fails at all launch intervals. The Job can be launched manually
> and
> it will import the data just fine. I am trying to import foxpro files into
> the SQL server. Is this a permissions issue? What persmissions are passed
> from SQL to the other server I am trying to import from?
> Thanks
> --
> Mitch|||Running from the scheduler, your DTS package is going to run under the
context of the user that SQL Agent is running under. Check the
properties of SQL Agent, see what user the service is running as. That
user needs to have access to the share that your Foxpro database is on.

DTS launch from SQL Server Agent

Hi,

I want to build a task that does 3 things automatically at a fixed time interval:

1) Refresh the data (copy newly inserted data from a datamart to a datawarehouse)
2) Run a program (exe) to produce some external reports
3) Refresh an OLAP Cube with the new data so that users can access it

Basically, using SQL Server Agent, setting up steps 1 and 2 was pretty straightforward (for step 1, the main point of entry is a single sp).

I ran into some trouble figuring the easiest way to complete step 3. I created a DTS package with one object that updates the Cude on my server. This seems to be working fine. Then, I created step 3 in Agent and chose 'CmdExec' as the type of command. I then referenced the external exe 'dtsrun' to execute my DTS package.

Everything seems fine but I'm not sure I used the "best" way of doing things. Since the SQL Server Agent and DTS manager are both SQL Server tools (so is the Analysis services), I'm wondering if there wasn't an easier (thus more robust) way of completing my 3rd step?

Anyone? How is this done where you've worked?

Thanks,

Skip.Well, that is the technique that MSDN (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht_dts_pkgmng_9vck.asp) suggests.

You could always make the DTS Package into a SQL Agent job (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht_dts_pkgmng_71v2.asp), then run the job using sp_start_job (http://msdn.microsoft.com/library/en-us/tsqlref/ts_sp_sa-sz_11uq.asp) (but that is deviant).

-PatP|||As always I suggest this kBA http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q269074 to help DTS to schedule as a job.