I have made a DTS package with several tasks included. When I run it through
the designer on my working computer where I have SQL Server Developer edition
installed, the package is executed successfully. When I use DTSRun.exe to run
the package on the server (where the database is installed) it fails. After
spending a lot of time debugging I have found out that it is the FTP task, I
use to download a textfile,that is causing the failure. If I delete it
everything works like a charm. The server is a MSDE database, so my obvious
question is then: Is this a MSDE limitation? or is there a way I can work
around this problem?

BTW: The error I get is "unspecified error"

Any suggestions or clarifications on this issue would be greatly appreciated.

Regards /Frederik

Is DTS correctly installed, and teh correct vesrion. Not all installs of
MSDE include DTS.

Find the tools binn folder, and look for custtask.dll. If not found then you
do not have the FTP task. If you do not have dtspkg.dll then DTS is not
installed.

dtspkg.dll version should be somethig of the order - 2000.80.760.0
2000.80.193.0 is the minimum, but means you are running RTM code, so apply
SP3 and the security hotfixes.



Normal this is "C:\Program Files\Microsoft SQL Server\80\Tools\Binn"


--
Darren Green
http://www.sqldts.com
http://www.sqlis.com
"Frederik Wehlin" <Frederik Wehlin (AT) discussions (DOT) microsoft.com> wrote in
message news:F970568D-301C-4380-BF09-47214A19326E (AT) microsoft (DOT) com...

Hi Darren, thanx for your response!

I have DTS installed the version is: 2000.80.194.0 (I have both dtspkt.dll
and custtask.dll)

The funny thing is that all other tasks work but the ftp task. The computer
OS i Windows 2000 professional with sp4 installed. Any other clues?

Regards


"Darren Green" wrote:

I know there was at least one bug in the FTP task for RTM, although I don't
recognise your symptoms. First thing I would do is apply the latest SP.
Build 194 is RTM.


--
Darren Green
http://www.sqldts.com
http://www.sqlis.com
"Frederik Wehlin" <Frederik Wehlin (AT) discussions (DOT) microsoft.com> wrote in
message news:1145173F-C0F9-4B84-9E05-0D51BC24C273 (AT) microsoft (DOT) com...

I have already done that and symptom remains.
I'm going to try on a different MSDE database to find out if I get the same
error otherwise I'll just reinstall MSDE on my server and hopefully it'll
work.

Thanx for taking your time!



"Darren Green" wrote: