Scheduling a simple local package won't stick

#1

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?

#2

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" <Rockitman (AT) discussions (DOT) microsoft.com> wrote

Quote:

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?

#3

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" <Rockitman (AT) discussions (DOT) microsoft.com> wrote

Quote:

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?

#4

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" <Rockitman (AT) discussions (DOT) microsoft.com> wrote

Quote:

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?

#5

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" <Rockitman (AT) discussions (DOT) microsoft.com> wrote

Quote:

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?

#6

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" <Rockitman (AT) discussions (DOT) microsoft.com> wrote

Quote:

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?

#7

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" <Rockitman (AT) discussions (DOT) microsoft.com> wrote

Quote:

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?

#8

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" <Rockitman (AT) discussions (DOT) microsoft.com> wrote

Quote:

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?

#9

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" <Rockitman (AT) discussions (DOT) microsoft.com> wrote

Quote:

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?

#10

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:

Quote:

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" <Rockitman (AT) discussions (DOT) microsoft.com> wrote in message
news:1AA95AF3-8BEB-419F-A59A-48A28FEB95A2 (AT) microsoft (DOT) 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?