Certificate error in new version

Question

Made a reference to version 7.4.2, re-compiled and now this error gets thrown:

Module: ThunderFileRouter

Procedure: ConnectSecureFTP

Message: Calling Sub:ResultsHL7CheckForFiles

Error Message: The certificate could not be verified: -1 - The certificate is invalid.

Error Source: edtFTPnetPRO

Error Target: WY5HOtJdbev

Error Stack Trace:    at QoHLMGvKKOMFW5Wq7gm.xQ3rc1ve2g9Sd3vWKEw.WY5HOtJdbev(BaseSocket )
   at QoHLMGvKKOMFW5Wq7gm.xQ3rc1ve2g9Sd3vWKEw.vmBHOwuQoYg()
   at EnterpriseDT.Net.ftp.Ssl.SSLFTPClient.Auth(SSLFTPSSLVersion sslVersion, Boolean secureDataChannels)
   at EnterpriseDT.Net.ftp.Ssl.SSLFTPClient.Auth(SSLFTPSSLVersion sslVersion)
   at EnterpriseDT.Net.ftp.SecureFTPConnection.SecureConnection()
   at EnterpriseDT.Net.ftp.SecureFTPConnection.Connect()
   at CLPThunderFileRouter.ThunderFileRouter.ConnectSecureFTP(String callingSub) in C:\Dotnet\Projects\CLPThunderFileRouter\CLPThunderFileRouter\ThunderFileRouter.vb:line 157

This is code that has been running for over 3 years using edtFTPnetPRO.

here is the connection code:

           EnterpriseDT.Util.Debug.Logger.CurrentLevel = EnterpriseDT.Util.Debug.Level.ERROR
            EnterpriseDT.Util.Debug.Logger.AddAppender(New EnterpriseDT.Util.Debug.FileAppender("C:\\ftp.txt"))
            sFTP = New SecureFTPConnection
            With sFTP
                .LicenseOwner = "xxxxxxxxxxxxxxx"
                .LicenseKey = "xxxxxxxxxxxxxxxxxxxxxx"

                .ServerAddress = ftpServer
                .ServerPort = CType(ftpPort, Integer)
                .UserName = ftpUser
                .Password = ftpPassword

                .Protocol = FileTransferProtocol.FTPSExplicit
                .ServerValidation = SecureFTPServerValidationType.Automatic
                .ServerCommonName = "ftp.clptestpoint.com"
                .SSLVersion = SSLFTPSSLVersion.SSL3

                .Connect()
            End With

pointed back to version 7.3.1.20 and all is well again

Answer 1

and here is the DEBUG:

DEBUG [LicenseProperties] 16 Jun 2011 14:52:24.218 : Looking for subkey Software\Enterprise Distributed Technologies\edtFTPnet PRO (fallback )
DEBUG [LicenseProperties] 16 Jun 2011 14:52:24.250 : Found license subkey Software\Enterprise Distributed Technologies\edtFTPnet PRO
DEBUG [LicenseProperties] 16 Jun 2011 14:52:24.250 : Looking for subkey Software\Enterprise Distributed Technologies\edtFTPnet PRO (fallback )
DEBUG [LicenseProperties] 16 Jun 2011 14:52:24.250 : Found license subkey Software\Enterprise Distributed Technologies\edtFTPnet PRO
DEBUG [LicenseProperties] 16 Jun 2011 14:52:24.281 : Looking for subkey Software\Enterprise Distributed Technologies\edtFTPnet PRO (fallback )
DEBUG [LicenseProperties] 16 Jun 2011 14:52:24.281 : Found license subkey Software\Enterprise Distributed Technologies\edtFTPnet PRO
DEBUG [LicenseProperties] 16 Jun 2011 14:52:24.281 : Looking for subkey Software\Enterprise Distributed Technologies\edtFTPnet PRO (fallback )
DEBUG [LicenseProperties] 16 Jun 2011 14:52:24.281 : Found license subkey Software\Enterprise Distributed Technologies\edtFTPnet PRO
INFO [LicenseProperties] 16 Jun 2011 14:52:24.296 : Licence expiry date: 12/31/9999
INFO [LicenseProperties] 16 Jun 2011 14:52:24.296 : Production license
DEBUG [FTPConnection] 16 Jun 2011 14:52:24.296 : Set LocalDirectory='C:\Dotnet\Projects\CLPThunderFileRouter\CLPThunderFileRouter\bin\Debug'
DEBUG [SecureFTPConnection] 16 Jun 2011 14:52:24.296 : Set LocalDirectory to C:\Dotnet\Projects\CLPThunderFileRouter\CLPThunderFileRouter\bin\Debug
INFO [LicenseProperties] 16 Jun 2011 14:52:24.296 : Licence expiry date: 12/31/9999
INFO [LicenseProperties] 16 Jun 2011 14:52:24.296 : Production license
DEBUG [SSLFTPClient] 16 Jun 2011 14:52:24.296 : Connecting to 204.130.8.3:21
DEBUG [SSLFTPControlSocket] 16 Jun 2011 14:52:24.296 : waitOnShutdownSSL=True
DEBUG [HostNameResolver] 16 Jun 2011 14:52:24.328 : Resolving 204.130.8.3
DEBUG [HostNameResolver] 16 Jun 2011 14:52:24.328 : 204.130.8.3 resolved to 204.130.8.3
DEBUG [ExFTPControlSocket] 16 Jun 2011 14:52:24.328 : Connecting directly to ftp-server 204.130.8.3:21
INFO [SSLFTPSocket] 16 Jun 2011 14:52:24.328 : Connecting to 204.130.8.3:21 with timeout 120000 ms
DEBUG [FTPControlSocket] 16 Jun 2011 14:52:24.343 : Setting socket timeout=120000
INFO [FTPControlSocket] 16 Jun 2011 14:52:24.343 : Command encoding=System.Text.SBCSCodePageEncoding
DEBUG [ExFTPControlSocket] 16 Jun 2011 14:52:24.359 : Created control-socket: SocksContext=, ProxySettings=NoProxy, RemoteHost=204.130.8.3, controlPort=21, timeout=120000
DEBUG [FTPControlSocket] 16 Jun 2011 14:52:24.359 : StrictReturnCodes=False
DEBUG [FTPControlSocket] 16 Jun 2011 14:52:24.359 : 220 Serv-U FTP Server v6.4 for WinSock ready...
DEBUG [FTPControlSocket] 16 Jun 2011 14:52:24.359 : ---> AUTH TLS
DEBUG [FTPControlSocket] 16 Jun 2011 14:52:24.359 : 234 AUTH command OK. Initializing SSL connection.
DEBUG [SSLFTPControlSocket] 16 Jun 2011 14:52:24.375 : Beginning Ssl3 handshake.
DEBUG [SocketController] 16 Jun 2011 14:52:24.406 : Processing hello
ERROR [SocketController] 16 Jun 2011 14:52:24.484 : OnReceive - caught exception - closing: The certificate could not be verified: -1 - The certificate is invalid.
DEBUG [SocketController] 16 Jun 2011 14:52:24.484 : CloseConnection(e=The certificate could not be verified: -1 - The certificate is invalid.)
DEBUG [SocketController] 16 Jun 2011 14:52:24.484 : Shut down socket
DEBUG [SocketController] 16 Jun 2011 14:52:24.484 : Closed socket
DEBUG [TransferBuffer] 16 Jun 2011 14:52:24.484 : Close() called when open
DEBUG [SecureSocket] 16 Jun 2011 14:52:24.484 : OnHandshakeComplete(False,The certificate could not be verified: -1 - The certificate is invalid.)
ERROR [SecureSocket] 16 Jun 2011 14:52:24.484 : Exception during handshake: The certificate could not be verified: -1 - The certificate is invalid.

Answer 2

I'm not sure what the error is, which is partly because our software is printing out a generic error message instead of the specific message that Windows is passing back. We're adding code to print out more detailed error messages and can provide you with a modified build on Monday. Could you please e-mail support@enterprisedt so that we can send you the new build?

- Hans (EnterpriseDT)

Answer 3

Will do. We are eventually migrating to Serv-U 10.x or the new 11.x and will not be using certificates.