Home Forums .NET libraries Xceed SFTP/FTP for .NET XCeed Error on 64Bit Server

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • User (Old forums)
    Member
    Post count: 23064
    #21022 |

    Getting the following error, but only on 64bit windows server.  Works fine on 32bit servers.  Saw another thread about it, but no solution was posted.

    — SPECS —
    Windows 2003
     .Net 2.0
    Xceed FTP version 3.7.8312.9580

    — ERROR —
     Xceed.Ftp.FtpSslException: An SSL error occurred while sending a command. —> Xceed.Utils.Security.SecurityException: An error occured while communicating with the remote host. —> Xceed.Utils.Security.Ssl.Shared.SslException: The pulic key should be at least 512 bits.
       at Xceed.Utils.Security.Ssl.Shared.HandshakeLayer.ProcessCertificate(HandshakeMessage message, Boolean client)
       at Xceed.Utils.Security.Ssl.Shared.ClientHandshakeLayer.ProcessMessage(HandshakeMessage message)
       at Xceed.Utils.Security.Ssl.Shared.HandshakeLayer.ProcessMessages(RecordMessage message)
       at Xceed.Utils.Security.Ssl.Shared.RecordLayer.ProcessBytes(Byte[] buffer, Int32 offset, Int32 size)
       at Xceed.Utils.Security.Ssl.Shared.CompatibilityLayer.ProcessServerHello(Byte[] bytes, Int32 offset, Int32 size)
       at Xceed.Utils.Security.Ssl.Shared.CompatibilityLayer.ProcessHello(Byte[] bytes, Int32 offset, Int32 size)
       at Xceed.Utils.Security.Ssl.Shared.SocketController.OnReceive(IAsyncResult ar)
       — End of inner exception stack trace —
       at Xceed.Utils.Security.Ssl.SecureSocket.EndSend(IAsyncResult asyncResult)
       at Xceed.Ftp.Engine.FtpCommandChannel.SendString(String command)
       — End of inner exception stack trace —

    Applies to Xceed FTP for .NET. Imported from legacy forums. Posted by Kipper (had 2628 views)

    Xceed Support
    Member
    Post count: 5658

    Hi kipper,

      would it be possible to send a repro app to support@xceedsoft.com at Christian’s attention and mention this forum post?

    This would help us identify the source of the problem.

    Thanks, 

    Applies to Xceed FTP for .NET. Imported from legacy forums. Posted by Chris [Xceed] (had 1000 views)

    User (Old forums)
    Member
    Post count: 23064

    Hi Chris, has there been any resolution to this issue as I am also getting this issue now on Windows 7 64bit, switching to 32bit output works, but 64bit fails.

    Applies to Xceed FTP for .NET. Imported from legacy forums. Posted by Daniel (had 1082 views)

    User (Old forums)
    Member
    Post count: 23064

    Same problem here using v3.2.6563.0 on Windows 7 x64. Is this something that is fixed in a newer XCeed FTP for .NET version?

    Applies to Xceed FTP for .NET. Imported from legacy forums. Posted by Mathias (had 594 views)

    User (Old forums)
    Member
    Post count: 23064

    Hi Christian,

    Is there any update to this issue?  We are having similar issue. Everything runs fine on 32 bit Windows server but not on Windows 2008 R2 servers. Here is the error we are getting when attempting to connect using SSL authentication. I have tried both Ssl and Tls types and resulted in the same exception. Any help would be appreciated. Thank you.

    Geeva

    ———————————————–

    Inner Exception:

    ———————————————–

    FTPException: Xceed.Ftp – An SSL error occurred while sending a command.
    Xceed.Utils.Security.SecurityException: An error occured while communicating with the remote host. —> Xceed.Utils.Security.Ssl.Shared.SslException: The pulic key should be at least 512 bits.
       at Xceed.Utils.Security.Ssl.Shared.HandshakeLayer.ProcessCertificate(HandshakeMessage message, Boolean client)
       at Xceed.Utils.Security.Ssl.Shared.ClientHandshakeLayer.ProcessMessage(HandshakeMessage message)
       at Xceed.Utils.Security.Ssl.Shared.HandshakeLayer.ProcessMessages(RecordMessage message)
       at Xceed.Utils.Security.Ssl.Shared.RecordLayer.ProcessBytes(Byte[] buffer, Int32 offset, Int32 size)
       at Xceed.Utils.Security.Ssl.Shared.CompatibilityLayer.ProcessServerHello(Byte[] bytes, Int32 offset, Int32 size)
       at Xceed.Utils.Security.Ssl.Shared.CompatibilityLayer.ProcessHello(Byte[] bytes, Int32 offset, Int32 size)
       at Xceed.Utils.Security.Ssl.Shared.SocketController.OnReceive(IAsyncResult ar)
       — End of inner exception stack trace —
       at Xceed.Utils.Security.Ssl.SecureSocket.EndSend(IAsyncResult asyncResult)
       at Xceed.Ftp.Engine.FtpCommandChannel.SendString(String command) 

     

    ——————————————

    My code:

    ——————————————

    private void ConnectFTPviaSSL()

    {

    try

    {

    Xceed.Ftp.

    Licenser.LicenseKey = “xxxx-xxxx-xxxx-xxxx”;

     

    FtpClient ftpclient = new FtpClient();

    ftpclient.CertificateReceived +=

    new CertificateReceivedEventHandler(ftpclient_CertificateReceived);

    ftpclient.Connect(

    “ftps.servername.com”);

    ftpclient.Authenticate(

    AuthenticationMethod.Ssl, VerificationFlags.None, null, DataChannelProtection.Private);

    ftpclient.Login(

    “userid”, “pasword”);

    ftpclient.Disconnect();

    }

    catch (Xceed.Ftp.FtpException ex)

    {

    this.txtStatus.Text += “FTPException: “ + ex.Source + ” – “ + ex.Message + Environment.NewLine + ex.InnerException;

    }

    catch (Exception ex)

    {

    this.txtStatus.Text += “Exception: “ + ex.Source + ” – “ + ex.Message + Environment.NewLine + ex.InnerException;

    }

    }

    void ftpclient_CertificateReceived(object sender, CertificateReceivedEventArgs e)

    {

    this.txtStatus.Text += “CertificateReceived : “ + e.ServerCertificate.ToString() + Environment.NewLine;

    e.Action =

    VerificationAction.Accept;

    }

    Applies to Xceed FTP for .NET. Imported from legacy forums. Posted by Geeva (had 1273 views)

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.