Greetings All,

I have a DTS package that is executing a batch file (along with store
procedures, imports, exports...), but somehow i cannot see the execute
task for the batch file in the DTS design!

I know it's being run because the .cmd prompt is being invoked. It seems
the execute task icon is hidden or is somehow being triggered when the
package runs...is this possible? Any way to view this "hidden" task?

Thanks,

Don




*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

In article <Olv$paIfDHA.1760 (AT) TK2MSFTNGP09 (DOT) phx.gbl>, don larry
<donlarry17 (AT) hotmail (DOT) com> writes
If you have hidden the task behind some other object, then select
Auto-Layout from the Package menu. This will re-work the layout and
should separate all tasks and connections that you have.

I have seen, rarely, occasions where the object model has become out of
sync with the layout information. If you save the package through the
object model and then open it again this may also fix this problem as
the layout information will be re-generated.

DTSBackup 2000 offers a simple way to do this, available on my site
below, or there are some code samples that can do a similar process also
on the site.

--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org

Hi Darren,

I have tried auto-layout and DTS2000, to no avail. So, I just decided to
re-create a DTS package with only that batch file.

The DTS works if i click on execute, but doesn't if i try and schedule
the package with the job scheduler. All my other jobs work, and i have
admin access to all files, folder and SQL accounts. The job shows
"success", but no data is compied..any idea why?

Here's the batch:

open mydomain.com
myusername
mypassword
cd public/catalog/
get myfile.txt
\\myroot\myfolder\myfile.txt
disconnect
quit

Thank you in advance,
Don Larry



*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

In article <eT#YFYJfDHA.1752 (AT) TK2MSFTNGP10 (DOT) phx.gbl>, don larry
<donlarry17 (AT) hotmail (DOT) com> writes
The most common issues with scheduled packages are around
permissions due to the execution context and the location of execution-

INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/?kbid=269074

Support WebCast: Data Transformation Services Package Scheduling - An
Inside Look
http://support.microsoft.com/default...s/webcasts/wc1
02301/wcblurb102301.asp

I would also recommend you turn on logging within the package, either to
and error file or to a SQL Server (SQL 2000 Only) to get as much
information as possible.


--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org