Scheduling a simple local package won't stick

[Database Administrator]

If I right click the local package I created in Enterprise Manager( a simple
FTP download),
there
are options to Execute the package as well as Schedule the package. When I
select Execute package, it works fine. When I select Schedule package, I
then set my schedule and click OK. But it never runs when scheduled. When I
go back into Schedule package, my schedule is not there anymore either. Just
the default schedule which states run daily every day at midnight with no end
date. It doesn't run there either, only when I manually execute the
package.
What gives?

[Database Administrator]

Rockitman,

DTS packages do not retain a schedule. That dialog is just to help you
create a SQL Agent job with a schedule to run the DTS package. If you look
at the SQL Agent jobs on your server you should see one or more jobs that
you created when setting up schedules.

Look at those jobs to see their execution history, as well as any problems
running that may have caused their failure.

RLF

"Rockitman" wrote in message
news:1AA95AF3-8BEB-419F-A59A-48A28FEB95A2@microsoft.com...
>
>
> If I right click the local package I created in Enterprise Manager( a
> simple
> FTP download),
> there
> are options to Execute the package as well as Schedule the package. When
> I
> select Execute package, it works fine. When I select Schedule package, I
> then set my schedule and click OK. But it never runs when scheduled.
> When I
> go back into Schedule package, my schedule is not there anymore either.
> Just
> the default schedule which states run daily every day at midnight with no
> end
> date. It doesn't run there either, only when I manually execute the
> package.
> What gives?
>
>

[Database Administrator]

Thanks for clarifying Russell.

I have viewed the job history in the SQL Server Agent and see an error
message for this package:

"Executed as user: S2K3-FRE-SQL1\SYSTEM. DTSRun: Loading... DTSRun:
Executing... DTSRun OnStart: DTSStep_DTSFTPTask_1 DTSRun OnError:
DTSStep_DTSFTPTask_1, Error = -2147220489 (800403F7) Error string:
Folder K:\Gasline Master Copy\ does not exist or is not accesible on
destination. Error source: File Transfer Protocol Task Help file:
Help context: 0 Error Detail Records: Error: 0 (0);
Provider Error: 0 (0) Error string: Folder K:\Gasline Master Copy\
does not exist or is not accesible on destination. Error source: File
Transfer Protocol Task Help file: Help context: 0 DTSRun
OnFinish: DTSStep_DTSFTPTask_1 DTSRun: Package execution complete.
Process Exit Code 1. The step failed."

So it appears that it doesn't like the destination folder that the FTP is
supposed to download the file to. I don't understand why though. When I
manually execute the package, it works just fine. Please advise.

"Russell Fields" wrote:

> Rockitman,
>
> DTS packages do not retain a schedule. That dialog is just to help you
> create a SQL Agent job with a schedule to run the DTS package. If you look
> at the SQL Agent jobs on your server you should see one or more jobs that
> you created when setting up schedules.
>
> Look at those jobs to see their execution history, as well as any problems
> running that may have caused their failure.
>
> RLF
>
> "Rockitman" wrote in message
> news:1AA95AF3-8BEB-419F-A59A-48A28FEB95A2@microsoft.com...
> >
> >
> > If I right click the local package I created in Enterprise Manager( a
> > simple
> > FTP download),
> > there
> > are options to Execute the package as well as Schedule the package. When
> > I
> > select Execute package, it works fine. When I select Schedule package, I
> > then set my schedule and click OK. But it never runs when scheduled.
> > When I
> > go back into Schedule package, my schedule is not there anymore either.
> > Just
> > the default schedule which states run daily every day at midnight with no
> > end
> > date. It doesn't run there either, only when I manually execute the
> > package.
> > What gives?
> >
> >
>
>

[Database Administrator]

Rockitman,

Now you are into the problem that I was describing to GC in this group.

1 - When you run the DTS package yourself, it runs with your credentials,
your file mappings, and so forth.

2 - When the server runs the DTS Package from SQL Agent it runs in one of
two security contexts.
(a) - The job is owned by a sysadmin account, so it runs as the SQL Server
service account.
(b) - The job is owned by a non-sysadmin account, so it runs as the SQL
Agent Proxy Account.

Likely, neither of these accounts will have your drive mapping, so using the
UNC path is better. E.g.
\\Servername\Sharename\Directory\File.Ext

Also, it may be that the two accounts doe not have rights to the folder. If
they do not, then that needs to be granted.

RLF

"Rockitman" wrote in message
news:CE53C590-A123-4ACA-AAA6-CB3DD3F0378C@microsoft.com...
> Thanks for clarifying Russell.
>
> I have viewed the job history in the SQL Server Agent and see an error
> message for this package:
>
> "Executed as user: S2K3-FRE-SQL1\SYSTEM. DTSRun: Loading... DTSRun:
> Executing... DTSRun OnStart: DTSStep_DTSFTPTask_1 DTSRun OnError:
> DTSStep_DTSFTPTask_1, Error = -2147220489 (800403F7) Error string:
> Folder K:\Gasline Master Copy\ does not exist or is not accesible on
> destination. Error source: File Transfer Protocol Task Help
> file:
> Help context: 0 Error Detail Records: Error: 0 (0);
> Provider Error: 0 (0) Error string: Folder K:\Gasline Master Copy\
> does not exist or is not accesible on destination. Error source:
> File
> Transfer Protocol Task Help file: Help context: 0 DTSRun
> OnFinish: DTSStep_DTSFTPTask_1 DTSRun: Package execution complete.
> Process Exit Code 1. The step failed."
>
> So it appears that it doesn't like the destination folder that the FTP is
> supposed to download the file to. I don't understand why though. When I
> manually execute the package, it works just fine. Please advise.
>
> "Russell Fields" wrote:
>
>> Rockitman,
>>
>> DTS packages do not retain a schedule. That dialog is just to help you
>> create a SQL Agent job with a schedule to run the DTS package. If you
>> look
>> at the SQL Agent jobs on your server you should see one or more jobs that
>> you created when setting up schedules.
>>
>> Look at those jobs to see their execution history, as well as any
>> problems
>> running that may have caused their failure.
>>
>> RLF
>>
>> "Rockitman" wrote in message
>> news:1AA95AF3-8BEB-419F-A59A-48A28FEB95A2@microsoft.com...
>> >
>> >
>> > If I right click the local package I created in Enterprise Manager( a
>> > simple
>> > FTP download),
>> > there
>> > are options to Execute the package as well as Schedule the package.
>> > When
>> > I
>> > select Execute package, it works fine. When I select Schedule package,
>> > I
>> > then set my schedule and click OK. But it never runs when scheduled.
>> > When I
>> > go back into Schedule package, my schedule is not there anymore either.
>> > Just
>> > the default schedule which states run daily every day at midnight with
>> > no
>> > end
>> > date. It doesn't run there either, only when I manually execute the
>> > package.
>> > What gives?
>> >
>> >
>>
>>

[Database Administrator]

Well my domain account is the owner, and it is member of the local
administrator group on the server, so I assume that the SQL server service
account is running the job?

Where do I find out if this Sql server service account has the necessary
rights?
I do not see this account listed in Users, nor in SQL server logins.


"Russell Fields" wrote:

> Rockitman,
>
> Now you are into the problem that I was describing to GC in this group.
>
> 1 - When you run the DTS package yourself, it runs with your credentials,
> your file mappings, and so forth.
>
> 2 - When the server runs the DTS Package from SQL Agent it runs in one of
> two security contexts.
> (a) - The job is owned by a sysadmin account, so it runs as the SQL Server
> service account.
> (b) - The job is owned by a non-sysadmin account, so it runs as the SQL
> Agent Proxy Account.
>
> Likely, neither of these accounts will have your drive mapping, so using the
> UNC path is better. E.g.
> \\Servername\Sharename\Directory\File.Ext
>
> Also, it may be that the two accounts doe not have rights to the folder. If
> they do not, then that needs to be granted.
>
> RLF
>
> "Rockitman" wrote in message
> news:CE53C590-A123-4ACA-AAA6-CB3DD3F0378C@microsoft.com...
> > Thanks for clarifying Russell.
> >
> > I have viewed the job history in the SQL Server Agent and see an error
> > message for this package:
> >
> > "Executed as user: S2K3-FRE-SQL1\SYSTEM. DTSRun: Loading... DTSRun:
> > Executing... DTSRun OnStart: DTSStep_DTSFTPTask_1 DTSRun OnError:
> > DTSStep_DTSFTPTask_1, Error = -2147220489 (800403F7) Error string:
> > Folder K:\Gasline Master Copy\ does not exist or is not accesible on
> > destination. Error source: File Transfer Protocol Task Help
> > file:
> > Help context: 0 Error Detail Records: Error: 0 (0);
> > Provider Error: 0 (0) Error string: Folder K:\Gasline Master Copy\
> > does not exist or is not accesible on destination. Error source:
> > File
> > Transfer Protocol Task Help file: Help context: 0 DTSRun
> > OnFinish: DTSStep_DTSFTPTask_1 DTSRun: Package execution complete.
> > Process Exit Code 1. The step failed."
> >
> > So it appears that it doesn't like the destination folder that the FTP is
> > supposed to download the file to. I don't understand why though. When I
> > manually execute the package, it works just fine. Please advise.
> >
> > "Russell Fields" wrote:
> >
> >> Rockitman,
> >>
> >> DTS packages do not retain a schedule. That dialog is just to help you
> >> create a SQL Agent job with a schedule to run the DTS package. If you
> >> look
> >> at the SQL Agent jobs on your server you should see one or more jobs that
> >> you created when setting up schedules.
> >>
> >> Look at those jobs to see their execution history, as well as any
> >> problems
> >> running that may have caused their failure.
> >>
> >> RLF
> >>
> >> "Rockitman" wrote in message
> >> news:1AA95AF3-8BEB-419F-A59A-48A28FEB95A2@microsoft.com...
> >> >
> >> >
> >> > If I right click the local package I created in Enterprise Manager( a
> >> > simple
> >> > FTP download),
> >> > there
> >> > are options to Execute the package as well as Schedule the package.
> >> > When
> >> > I
> >> > select Execute package, it works fine. When I select Schedule package,
> >> > I
> >> > then set my schedule and click OK. But it never runs when scheduled.
> >> > When I
> >> > go back into Schedule package, my schedule is not there anymore either.
> >> > Just
> >> > the default schedule which states run daily every day at midnight with
> >> > no
> >> > end
> >> > date. It doesn't run there either, only when I manually execute the
> >> > package.
> >> > What gives?
> >> >
> >> >
> >>
> >>
>
>

[Database Administrator]

Rockitman,

It depends on how your server has been set up, but the local administrator
group does not need to be, and on my servers is not, a SQL Server sysadmin.
(That group actually has no SQL Server rights.)

Therefore, it is not obvious to me which account you are running under
because I don't know if you are a sysadmin. In a query window run the
following. If it returns 1 you are a system administrator.

SELECT IS_Srvrolemember('sysadmin')

The rights you need to check are not SQL Server rights, but rights to the
directory path you are trying to access. This is a domain rights issue, so
it will not be listed in the SQL Server security tables.

Go to the directory in question and look at its security membership. Browse
to the directory using Explorer, right click on the folder and choose
Properties, choose the Security tab. If the answer is not obvious, talk to
your domain administrators to get their help.

RLF

"Rockitman" wrote in message
news:6A298E87-4465-4850-A216-91B800BA5581@microsoft.com...
> Well my domain account is the owner, and it is member of the local
> administrator group on the server, so I assume that the SQL server
> service
> account is running the job?
>
> Where do I find out if this Sql server service account has the necessary
> rights?
> I do not see this account listed in Users, nor in SQL server logins.
>
>
> "Russell Fields" wrote:
>
>> Rockitman,
>>
>> Now you are into the problem that I was describing to GC in this group.
>>
>> 1 - When you run the DTS package yourself, it runs with your credentials,
>> your file mappings, and so forth.
>>
>> 2 - When the server runs the DTS Package from SQL Agent it runs in one of
>> two security contexts.
>> (a) - The job is owned by a sysadmin account, so it runs as the SQL
>> Server
>> service account.
>> (b) - The job is owned by a non-sysadmin account, so it runs as the SQL
>> Agent Proxy Account.
>>
>> Likely, neither of these accounts will have your drive mapping, so using
>> the
>> UNC path is better. E.g.
>> \\Servername\Sharename\Directory\File.Ext
>>
>> Also, it may be that the two accounts doe not have rights to the folder.
>> If
>> they do not, then that needs to be granted.
>>
>> RLF
>>
>> "Rockitman" wrote in message
>> news:CE53C590-A123-4ACA-AAA6-CB3DD3F0378C@microsoft.com...
>> > Thanks for clarifying Russell.
>> >
>> > I have viewed the job history in the SQL Server Agent and see an error
>> > message for this package:
>> >
>> > "Executed as user: S2K3-FRE-SQL1\SYSTEM. DTSRun: Loading... DTSRun:
>> > Executing... DTSRun OnStart: DTSStep_DTSFTPTask_1 DTSRun OnError:
>> > DTSStep_DTSFTPTask_1, Error = -2147220489 (800403F7) Error string:
>> > Folder K:\Gasline Master Copy\ does not exist or is not accesible on
>> > destination. Error source: File Transfer Protocol Task Help
>> > file:
>> > Help context: 0 Error Detail Records: Error: 0 (0);
>> > Provider Error: 0 (0) Error string: Folder K:\Gasline Master
>> > Copy\
>> > does not exist or is not accesible on destination. Error source:
>> > File
>> > Transfer Protocol Task Help file: Help context: 0
>> > DTSRun
>> > OnFinish: DTSStep_DTSFTPTask_1 DTSRun: Package execution complete.
>> > Process Exit Code 1. The step failed."
>> >
>> > So it appears that it doesn't like the destination folder that the FTP
>> > is
>> > supposed to download the file to. I don't understand why though.
>> > When I
>> > manually execute the package, it works just fine. Please advise.
>> >
>> > "Russell Fields" wrote:
>> >
>> >> Rockitman,
>> >>
>> >> DTS packages do not retain a schedule. That dialog is just to help
>> >> you
>> >> create a SQL Agent job with a schedule to run the DTS package. If you
>> >> look
>> >> at the SQL Agent jobs on your server you should see one or more jobs
>> >> that
>> >> you created when setting up schedules.
>> >>
>> >> Look at those jobs to see their execution history, as well as any
>> >> problems
>> >> running that may have caused their failure.
>> >>
>> >> RLF
>> >>
>> >> "Rockitman" wrote in message
>> >> news:1AA95AF3-8BEB-419F-A59A-48A28FEB95A2@microsoft.com...
>> >> >
>> >> >
>> >> > If I right click the local package I created in Enterprise
>> >> > Manager( a
>> >> > simple
>> >> > FTP download),
>> >> > there
>> >> > are options to Execute the package as well as Schedule the package.
>> >> > When
>> >> > I
>> >> > select Execute package, it works fine. When I select Schedule
>> >> > package,
>> >> > I
>> >> > then set my schedule and click OK. But it never runs when
>> >> > scheduled.
>> >> > When I
>> >> > go back into Schedule package, my schedule is not there anymore
>> >> > either.
>> >> > Just
>> >> > the default schedule which states run daily every day at midnight
>> >> > with
>> >> > no
>> >> > end
>> >> > date. It doesn't run there either, only when I manually execute
>> >> > the
>> >> > package.
>> >> > What gives?
>> >> >
>> >> >
>> >>
>> >>
>>
>>

[Database Administrator]

Aha, I got it. I had to change the drive mapping from the K: mapping (which
is really the local D: drive of the server), changed it to D: and it works!!

Now, the FTP is just the first part of this package I wish to accomplish.
The FTP downloads a flat file into a directory where there is an Access
database. I need to import the file into a table in the database. I cannot
figure out which Task to use in the local package creation. Can you point me
to the right one?

"Russell Fields" wrote:

> Rockitman,
>
> It depends on how your server has been set up, but the local administrator
> group does not need to be, and on my servers is not, a SQL Server sysadmin.
> (That group actually has no SQL Server rights.)
>
> Therefore, it is not obvious to me which account you are running under
> because I don't know if you are a sysadmin. In a query window run the
> following. If it returns 1 you are a system administrator.
>
> SELECT IS_Srvrolemember('sysadmin')
>
> The rights you need to check are not SQL Server rights, but rights to the
> directory path you are trying to access. This is a domain rights issue, so
> it will not be listed in the SQL Server security tables.
>
> Go to the directory in question and look at its security membership. Browse
> to the directory using Explorer, right click on the folder and choose
> Properties, choose the Security tab. If the answer is not obvious, talk to
> your domain administrators to get their help.
>
> RLF
>
> "Rockitman" wrote in message
> news:6A298E87-4465-4850-A216-91B800BA5581@microsoft.com...
> > Well my domain account is the owner, and it is member of the local
> > administrator group on the server, so I assume that the SQL server
> > service
> > account is running the job?
> >
> > Where do I find out if this Sql server service account has the necessary
> > rights?
> > I do not see this account listed in Users, nor in SQL server logins.
> >
> >
> > "Russell Fields" wrote:
> >
> >> Rockitman,
> >>
> >> Now you are into the problem that I was describing to GC in this group.
> >>
> >> 1 - When you run the DTS package yourself, it runs with your credentials,
> >> your file mappings, and so forth.
> >>
> >> 2 - When the server runs the DTS Package from SQL Agent it runs in one of
> >> two security contexts.
> >> (a) - The job is owned by a sysadmin account, so it runs as the SQL
> >> Server
> >> service account.
> >> (b) - The job is owned by a non-sysadmin account, so it runs as the SQL
> >> Agent Proxy Account.
> >>
> >> Likely, neither of these accounts will have your drive mapping, so using
> >> the
> >> UNC path is better. E.g.
> >> \\Servername\Sharename\Directory\File.Ext
> >>
> >> Also, it may be that the two accounts doe not have rights to the folder.
> >> If
> >> they do not, then that needs to be granted.
> >>
> >> RLF
> >>
> >> "Rockitman" wrote in message
> >> news:CE53C590-A123-4ACA-AAA6-CB3DD3F0378C@microsoft.com...
> >> > Thanks for clarifying Russell.
> >> >
> >> > I have viewed the job history in the SQL Server Agent and see an error
> >> > message for this package:
> >> >
> >> > "Executed as user: S2K3-FRE-SQL1\SYSTEM. DTSRun: Loading... DTSRun:
> >> > Executing... DTSRun OnStart: DTSStep_DTSFTPTask_1 DTSRun OnError:
> >> > DTSStep_DTSFTPTask_1, Error = -2147220489 (800403F7) Error string:
> >> > Folder K:\Gasline Master Copy\ does not exist or is not accesible on
> >> > destination. Error source: File Transfer Protocol Task Help
> >> > file:
> >> > Help context: 0 Error Detail Records: Error: 0 (0);
> >> > Provider Error: 0 (0) Error string: Folder K:\Gasline Master
> >> > Copy\
> >> > does not exist or is not accesible on destination. Error source:
> >> > File
> >> > Transfer Protocol Task Help file: Help context: 0
> >> > DTSRun
> >> > OnFinish: DTSStep_DTSFTPTask_1 DTSRun: Package execution complete.
> >> > Process Exit Code 1. The step failed."
> >> >
> >> > So it appears that it doesn't like the destination folder that the FTP
> >> > is
> >> > supposed to download the file to. I don't understand why though.
> >> > When I
> >> > manually execute the package, it works just fine. Please advise.
> >> >
> >> > "Russell Fields" wrote:
> >> >
> >> >> Rockitman,
> >> >>
> >> >> DTS packages do not retain a schedule. That dialog is just to help
> >> >> you
> >> >> create a SQL Agent job with a schedule to run the DTS package. If you
> >> >> look
> >> >> at the SQL Agent jobs on your server you should see one or more jobs
> >> >> that
> >> >> you created when setting up schedules.
> >> >>
> >> >> Look at those jobs to see their execution history, as well as any
> >> >> problems
> >> >> running that may have caused their failure.
> >> >>
> >> >> RLF
> >> >>
> >> >> "Rockitman" wrote in message
> >> >> news:1AA95AF3-8BEB-419F-A59A-48A28FEB95A2@microsoft.com...
> >> >> >
> >> >> >
> >> >> > If I right click the local package I created in Enterprise
> >> >> > Manager( a
> >> >> > simple
> >> >> > FTP download),
> >> >> > there
> >> >> > are options to Execute the package as well as Schedule the package.
> >> >> > When
> >> >> > I
> >> >> > select Execute package, it works fine. When I select Schedule
> >> >> > package,
> >> >> > I
> >> >> > then set my schedule and click OK. But it never runs when
> >> >> > scheduled.
> >> >> > When I
> >> >> > go back into Schedule package, my schedule is not there anymore
> >> >> > either.
> >> >> > Just
> >> >> > the default schedule which states run daily every day at midnight
> >> >> > with
> >> >> > no
> >> >> > end
> >> >> > date. It doesn't run there either, only when I manually execute
> >> >> > the
> >> >> > package.
> >> >> > What gives?
> >> >> >
> >> >> >
> >> >>
> >> >>
> >>
> >>
>
>

[Database Administrator]

Rockitman,

Either the Transform Data task or the Bulk Insert task will probably do, but
read about them first to determine which to choose.

RLF

"Rockitman" wrote in message
news:361FB9C2-8F87-4BB8-8309-297138D63A62@microsoft.com...
> Aha, I got it. I had to change the drive mapping from the K: mapping
> (which
> is really the local D: drive of the server), changed it to D: and it
> works!!
>
> Now, the FTP is just the first part of this package I wish to accomplish.
> The FTP downloads a flat file into a directory where there is an Access
> database. I need to import the file into a table in the database. I
> cannot
> figure out which Task to use in the local package creation. Can you point
> me
> to the right one?
>
> "Russell Fields" wrote:
>
>> Rockitman,
>>
>> It depends on how your server has been set up, but the local
>> administrator
>> group does not need to be, and on my servers is not, a SQL Server
>> sysadmin.
>> (That group actually has no SQL Server rights.)
>>
>> Therefore, it is not obvious to me which account you are running under
>> because I don't know if you are a sysadmin. In a query window run the
>> following. If it returns 1 you are a system administrator.
>>
>> SELECT IS_Srvrolemember('sysadmin')
>>
>> The rights you need to check are not SQL Server rights, but rights to the
>> directory path you are trying to access. This is a domain rights issue,
>> so
>> it will not be listed in the SQL Server security tables.
>>
>> Go to the directory in question and look at its security membership.
>> Browse
>> to the directory using Explorer, right click on the folder and choose
>> Properties, choose the Security tab. If the answer is not obvious, talk
>> to
>> your domain administrators to get their help.
>>
>> RLF
>>
>> "Rockitman" wrote in message
>> news:6A298E87-4465-4850-A216-91B800BA5581@microsoft.com...
>> > Well my domain account is the owner, and it is member of the local
>> > administrator group on the server, so I assume that the SQL server
>> > service
>> > account is running the job?
>> >
>> > Where do I find out if this Sql server service account has the
>> > necessary
>> > rights?
>> > I do not see this account listed in Users, nor in SQL server logins.
>> >
>> >
>> > "Russell Fields" wrote:
>> >
>> >> Rockitman,
>> >>
>> >> Now you are into the problem that I was describing to GC in this
>> >> group.
>> >>
>> >> 1 - When you run the DTS package yourself, it runs with your
>> >> credentials,
>> >> your file mappings, and so forth.
>> >>
>> >> 2 - When the server runs the DTS Package from SQL Agent it runs in one
>> >> of
>> >> two security contexts.
>> >> (a) - The job is owned by a sysadmin account, so it runs as the SQL
>> >> Server
>> >> service account.
>> >> (b) - The job is owned by a non-sysadmin account, so it runs as the
>> >> SQL
>> >> Agent Proxy Account.
>> >>
>> >> Likely, neither of these accounts will have your drive mapping, so
>> >> using
>> >> the
>> >> UNC path is better. E.g.
>> >> \\Servername\Sharename\Directory\File.Ext
>> >>
>> >> Also, it may be that the two accounts doe not have rights to the
>> >> folder.
>> >> If
>> >> they do not, then that needs to be granted.
>> >>
>> >> RLF
>> >>
>> >> "Rockitman" wrote in message
>> >> news:CE53C590-A123-4ACA-AAA6-CB3DD3F0378C@microsoft.com...
>> >> > Thanks for clarifying Russell.
>> >> >
>> >> > I have viewed the job history in the SQL Server Agent and see an
>> >> > error
>> >> > message for this package:
>> >> >
>> >> > "Executed as user: S2K3-FRE-SQL1\SYSTEM. DTSRun: Loading...
>> >> > DTSRun:
>> >> > Executing... DTSRun OnStart: DTSStep_DTSFTPTask_1 DTSRun
>> >> > OnError:
>> >> > DTSStep_DTSFTPTask_1, Error = -2147220489 (800403F7) Error
>> >> > string:
>> >> > Folder K:\Gasline Master Copy\ does not exist or is not accesible on
>> >> > destination. Error source: File Transfer Protocol Task
>> >> > Help
>> >> > file:
>> >> > Help context: 0 Error Detail Records: Error: 0 (0);
>> >> > Provider Error: 0 (0) Error string: Folder K:\Gasline Master
>> >> > Copy\
>> >> > does not exist or is not accesible on destination. Error
>> >> > source:
>> >> > File
>> >> > Transfer Protocol Task Help file: Help context: 0
>> >> > DTSRun
>> >> > OnFinish: DTSStep_DTSFTPTask_1 DTSRun: Package execution
>> >> > complete.
>> >> > Process Exit Code 1. The step failed."
>> >> >
>> >> > So it appears that it doesn't like the destination folder that the
>> >> > FTP
>> >> > is
>> >> > supposed to download the file to. I don't understand why though.
>> >> > When I
>> >> > manually execute the package, it works just fine. Please advise.
>> >> >
>> >> > "Russell Fields" wrote:
>> >> >
>> >> >> Rockitman,
>> >> >>
>> >> >> DTS packages do not retain a schedule. That dialog is just to help
>> >> >> you
>> >> >> create a SQL Agent job with a schedule to run the DTS package. If
>> >> >> you
>> >> >> look
>> >> >> at the SQL Agent jobs on your server you should see one or more
>> >> >> jobs
>> >> >> that
>> >> >> you created when setting up schedules.
>> >> >>
>> >> >> Look at those jobs to see their execution history, as well as any
>> >> >> problems
>> >> >> running that may have caused their failure.
>> >> >>
>> >> >> RLF
>> >> >>
>> >> >> "Rockitman" wrote in message
>> >> >> news:1AA95AF3-8BEB-419F-A59A-48A28FEB95A2@microsoft.com...
>> >> >> >
>> >> >> >
>> >> >> > If I right click the local package I created in Enterprise
>> >> >> > Manager( a
>> >> >> > simple
>> >> >> > FTP download),
>> >> >> > there
>> >> >> > are options to Execute the package as well as Schedule the
>> >> >> > package.
>> >> >> > When
>> >> >> > I
>> >> >> > select Execute package, it works fine. When I select Schedule
>> >> >> > package,
>> >> >> > I
>> >> >> > then set my schedule and click OK. But it never runs when
>> >> >> > scheduled.
>> >> >> > When I
>> >> >> > go back into Schedule package, my schedule is not there anymore
>> >> >> > either.
>> >> >> > Just
>> >> >> > the default schedule which states run daily every day at midnight
>> >> >> > with
>> >> >> > no
>> >> >> > end
>> >> >> > date. It doesn't run there either, only when I manually execute
>> >> >> > the
>> >> >> > package.
>> >> >> > What gives?
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >>
>> >>
>>
>>