>>>>>>>>>>>Hi Sergey
>>>>>>>>>>>
>>>>>>>>>>>I eventually realised that :-)
>>>>>>>>>>>
>>>>>>>>>>>Any thought on how I could do it ?
>>>>>>>>>>>
>>>>>>>>>>>IS FTP Task does not support SSL/SFTP/SSH/TSL
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>I want to add an FTP step to my dataflow package.
>>>>>>>>>>>>>
>>>>>>>>>>>>>I've added connection details that work in Filezilla but they don't connect in the FTP task step
>>>>>>>>>>>>>
>>>>>>>>>>>>>the message if I test the connection is
>>>>>>>>>>>>>
>>>>>>>>>>>>>Connection can not be established. Server name, port number, or credentials may be invalid.
>>>>>>>>>>>>>
>>>>>>>>>>>>>Is there anywhere I can find out more detail of what the actual problem is.
>>>>>>>>>>>>>
>>>>>>>>>>>>>The site uses port 9900 and Require implicit FTP over TLS.
>>>>>>>>>>>>>
>>>>>>>>>>>>> In the FTP task I can specify the port but not Require implicit FTP over TLS..
>>>>>>>>>>>>>
>>>>>>>>>>>>>Anyone got any ides ?
>>>>>>>>>>>>>
>>>>>>>>>>>>>Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>>Update
>>>>>>>>>>>>>
>>>>>>>>>>>>>Looks like this is a problem with the FTP task not supporting FTPS. Any suggestions on a way round this would be appreciated.
>>>>>>>>>>
>>>>>>>>>>Is using CLR integration an option ?
>>>>>>>>>>The FTP handling would be simple in .NET
>>>>>>>>>
>>>>>>>>>What do you mean by CLR (worried thats a ridiculous question)
>>>>>>>>>
>>>>>>>>>I am wondering about a script task as the only other options seem to be an expensive bought package task or unsecuring the ftp step (thats not necessarily a problem but might depend on the holder of the ftp site )
>>>>>>>>
>>>>>>>>CLR integration allow you to use .NET code for many purposes within SQL. See
>>>>>>>>
>>>>>>>>http://msdn.microsoft.com/en-us/library/ms254498(v=vs.80).aspx
>>>>>>>>http://msdn.microsoft.com/en-us/library/ms345136(v=sql.90).aspx
>>>>>>>>
>>>>>>>>It can also be used with SQL Express. You could write your own .NET code to send via FTP and simply refer to it as an inbuilt SQL SP. A routine in .NET using FTPWebRequest would be very simple. See
>>>>>>>> (http://msdn.microsoft.com/en-us/library/system.net.ftpwebrequest.aspx)
>>>>>>>>
>>>>>>>>If you can't use CLR integration I guess you could write the neccessary info to a file which could act as a queue for a separate .NET service.....
>>>>>>>
>>>>>>>
>>>>>>>Well now I'm trying that as a script task
>>>>>>>using the code as in
>>>>>>>
>>>>>>>http://msdn.microsoft.com/en-us/library/system.net.ftpwebrequest.aspx
>>>>>>>
>>>>>>>and I'm getting
>>>>>>>
>>>>>>>The underlying connection was closed: The server committed a protocol violation.
>>>>>>>
>>>>>>>any thoughts ?
>>>>>>
>>>>>>Maybe try setting UseUnsafeHeaderParsing true (at least worth a try):
>>>>>>http://msdn.microsoft.com/en-us/library/system.net.configuration.httpwebrequestelement.useunsafeheaderparsing.aspx
>>>>>
>>>>>Didn't help thanks.
>>>>
>>>>Hmm. From what I read on the web this error usually arises where the server is either being a bit sloppy on the protocol or using a older HTTP protocol (i.e 1.0 rather than 1.1)
>>>>On that basis another thing to try would be to explicitly set the protocol used on the client to 1.0:
>>>>http://msdn.microsoft.com/en-us/library/system.net.httpwebrequest.protocolversion.aspx
>>>>
>>>>If that doesn't work maybe you can use something like Fiddler to review exactly what is being returned by the server.......
>>>>Is the server accessible to the public (i.e. me) ?
>>>
>>>
>>>Thanks Viv
>>>
>>>I'll give that a go.
>>>
>>>No the server is owned by a 3rd party mailing house called telebank.
>>>
>>>I can connect ok to it using FileZilla. They seem to be having trouble making their plain FTP location available to me.
>>
>>Is this happening in GetResponse() ? If so take a look at the ProtocolViolationException and the following remarks here :http://msdn.microsoft.com/en-us/library/system.net.httpwebrequest.getresponse.aspx
>>Presumably that is an exhaustive list of conditions that can cause the error so it should just be a question of eliminating these one by one :-}
>
>I think I'm going to have to see if I can get non secure access to the remote FTP site. I thought this step of the process would take me a couple of hours to set up and instead its eating up time. :-(

That may or may not help. The .NET classes are certainly capable of supporting TLS. I've got code somewhere using them to go against a FileZilla FTP server that was configured that way but can't remember where it is :-{