(PowerBuilder) ConnectFailReason

The ConnectFailReason property can be examined to determine the reason why the Connect method failed. The possible values are listed in the source code below:

Chilkat ActiveX Downloads ActiveX for 32-bit and 64-bit Windows

integer li_rc
oleobject loo_Ftp
integer li_Success
integer li_FailReason

// This example requires the Chilkat API to have been previously unlocked.
// See Global Unlock Sample for sample code.

loo_Ftp = create oleobject
// Use "Chilkat_9_5_0.Ftp2" for versions of Chilkat < 10.0.0
li_rc = loo_Ftp.ConnectToNewObject("Chilkat.Ftp2")
if li_rc < 0 then
    destroy loo_Ftp
    MessageBox("Error","Connecting to COM object failed")
    return
end if

loo_Ftp.Hostname = "ftp.example.com"
loo_Ftp.Username = "login"
loo_Ftp.Password = "password"

// Connect and login to the FTP server.
li_Success = loo_Ftp.Connect()
if li_Success <> 1 then

    // The possible failure reasons are:
    // 0 = success
    // Non-SSL socket fail reasons:
    //  1 = empty hostname
    //  2 = DNS lookup failed
    //  3 = DNS timeout
    //  4 = Aborted by application.
    //  5 = Internal failure.
    //  6 = Connect Timed Out
    //  7 = Connect Rejected (or failed for some other reason)
    // SSL failure reasons:
    //  100 = Internal schannel error
    //  101 = Failed to create credentials
    //  102 = Failed to send initial message to proxy.
    //  103 = Handshake failed.
    //  104 = Failed to obtain remote certificate.
    // 300 = asynch op in progress
    // 301 = login failure.
    // 
    li_FailReason = loo_Ftp.ConnectFailReason

    Write-Debug "connect fail reason = " + string(li_FailReason)

    Write-Debug loo_Ftp.LastErrorText
    destroy loo_Ftp
    return
end if

// ..


destroy loo_Ftp