![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
-----Original Message----- There seems to be a problem running the sql ftp task object in a dts package on the sql server itself. The same process runs fine from a remote PC workstation, however, when run on the server the ftp task indicates completion but does not actually create the file. There is one caveat. If the filename being transferred has an extension as in "FILE_WITH.EXTENSION" then the result is OK. If the transferred file has no extension, as in "FILE_NO_EXTENSION", the result is NO FILE. Is there some kind of setting on a Windows Server that disallows file names with no extension or the creation of filenames with no extension that would cause this? There may be something with the FTP task that assumes the "path" plus the source name with no extension is still just a path. The FTP Task has a "path" property and the "source files" list, but there's no way to specify the output file names. This would be a great enhancement. --Paul . |
#3
| |||
| |||
|
#4
| |||
| |||
|
|
Just wanted to add that in my research of Msoft Knowledge base, there are articles on other SQL FTP problems with the resolution being the installation of the latest SQL2000 service pack. We have installed SP3a, but still have the problem. Please offer any suggestions. We'd appreciate your assistance in trying to resolve this issue. As a work- around, we are pursuing the option of changing our filenames to include extensions. This however is an elaborate effort as it requires changes in our ORACLE Financials package. Paul Bagdriwicz -----Original Message----- There seems to be a problem running the sql ftp task object in a dts package on the sql server itself. The same process runs fine from a remote PC workstation, however, when run on the server the ftp task indicates completion but does not actually create the file. There is one caveat. If the filename being transferred has an extension as in "FILE_WITH.EXTENSION" then the result is OK. If the transferred file has no extension, as in "FILE_NO_EXTENSION", the result is NO FILE. Is there some kind of setting on a Windows Server that disallows file names with no extension or the creation of filenames with no extension that would cause this? There may be something with the FTP task that assumes the "path" plus the source name with no extension is still just a path. The FTP Task has a "path" property and the "source files" list, but there's no way to specify the output file names. This would be a great enhancement. --Paul . |
#5
| |||
| |||
|
|
-----Original Message----- I did a quick test with two files, one with an extension and one without. Both came down fine. On the machine where the package is running, can you check the version of custtask.dll (C:\Program Files\Microsoft SQL Server\80\Tools\Binn). I have 2000.80.760.0 (SP3) and as I say it works. -- Darren Green (SQL Server MVP) DTS - http://www.sqldts.com PASS - the definitive, global community for SQL Server professionals http://www.sqlpass.org . |
#6
| |||
| |||
|
|
-----Original Message----- Paul, You said ANY suggestions right? :-) If you want a fully functional FTP solution you could try this... http://www.seekfordsolutions.com/Products/FTPWizard/ It is VERY reliable and adds flexibility to what you're able to do. You mention your workaround... Personally, I would go with the FTPWizard... It will run you $199 I would be willing to give you a sample of the activeX code to get you going right off the bat. They have a functional eval version you could use to see if it will work for you too... Good Luck... REM7600 "Paul Bagdriwicz" <anonymous (AT) discussions (DOT) microsoft.com wrote in message news:124ee01c3c034$b38ed2e0$a601280a (AT) phx (DOT) gbl... Just wanted to add that in my research of Msoft Knowledge base, there are articles on other SQL FTP problems with the resolution being the installation of the latest SQL2000 service pack. We have installed SP3a, but still have the problem. Please offer any suggestions. We'd appreciate your assistance in trying to resolve this issue. As a work- around, we are pursuing the option of changing our filenames to include extensions. This however is an elaborate effort as it requires changes in our ORACLE Financials package. Paul Bagdriwicz -----Original Message----- There seems to be a problem running the sql ftp task object in a dts package on the sql server itself. The same process runs fine from a remote PC workstation, however, when run on the server the ftp task indicates completion but does not actually create the file. There is one caveat. If the filename being transferred has an extension as in "FILE_WITH.EXTENSION" then the result is OK. If the transferred file has no extension, as in "FILE_NO_EXTENSION", the result is NO FILE. Is there some kind of setting on a Windows Server that disallows file names with no extension or the creation of filenames with no extension that would cause this? There may be something with the FTP task that assumes the "path" plus the source name with no extension is still just a path. The FTP Task has a "path" property and the "source files" list, but there's no way to specify the output file names. This would be a great enhancement. --Paul . . |
![]() |
| Thread Tools | |
| Display Modes | |
| |