Hello
I am having a problem setting up the scheduling of a DTS package. The package is correct because when I execute it by hand it runs fines. However I have tried to schedule this two ways and it is not working.

First of all when I created the DTS package by export data in SQL Server 2000, towards the last screen there is an option to run immediately or schedule it. I clicked the '...' button to schedule it and set the date and time (daily at noon for example). It DTS finished by saying that there were no errors. But the DTS doesn't execute. I looked at the empty table it is suppose to populate and I set it so after it successfully executes it sends me the email- and of course I get no email.

Then I tried another way, by saving it as SQL Server rather than Meta Data Services or Structured storage file. Then I went to Data Transformation Services --> Local Package --> Right click --> select
Schedule Package to set the date and time the click ok. It doesn't run.
What I noticed is that after I Schedule Package, it doesn't save those setting. When I go to Schedule Package again, it shows the defaults. Is it suppose to do that?

Also SQL Server Agent is running.

Help me. Thank you.

Just a thought! Did u by chance modify the package after scheduling. If yes, I think DTS assigns a new GUID each time the package is changed. Just try pointing to the package again and scheduling it.
Hope it helps.
----

Distributed computing ->Causality-> EventDriven ->We have the last laugh.!!

The DTS Designer in Enterprise Manager creates a new version GUID, but the Package GUID remains the same. When the Wizards schedule a DTS package for you they use the Package GUID not the version GUID. So while hemanth_p2p has a good thought process the GUID is not the problem.

David_the_DBA
www.mutuallybeneficial.com

Make sure 'Enabled' option is checked in Schedule tab.

Bekim,

To solve your problem we need to enable DTS Logging. Open the DTS package, right click on some whitespace in the Package, select Properties. Then click on the Logging Tab (beware of overanxious environmentalists ;) then check the box next to Log package execution to SQL Server. If this is the default instance then accepting the default of local with windows authentication will do. If this is a named instance you need to space the named instance in the Server text box.

Then click OK. Save your package. Exit the DTS Designer. Go to Jobs, run the job by right clicking on the job and selecting Start Job. When the job is done, return to the DTS area of Enterprise Manager, Right click on the Package and select Package Logs. In here you will be able to see what steps ran and what steps did not.

David Lundell
Principal Consultant and Trainer
www.mutuallybeneficial.com

Bekim,

Any result?

David Lundell
Principal Consultant and Trainer
www.mutuallybeneficial.com

scheduling the dts creates an sql agent job , but the job doesn't show up when you go to the jobs , you need to manually refresh jobs view

Yes, it does solve my problem! Many thanks.:)

To be is to do
To do is to be
To be do be do

I have been searhing all over the web for help with a similar problem. Thank you very much for posting this information!

I have taken over as DBA for a position that has been vacant for 1 year and the last worker left no documentation.... it has been a nightmare figuring why things have been failing for months! Thanks again.

To do some more advanced logging in DTS that will make your logs more usable and readable look at:
http://www.mutuallybeneficial.com/in...s_portable.htm
http://www.mutuallybeneficial.com/co...ing_Script.txt

David Lundell
Principal Consultant and Trainer
www.mutuallybeneficial.com