Chilkat
HOME
Android™
ASP
Visual Basic
VB.NET
C#
iOS (IPhone)
Objective-C
C++
C
MFC
Delphi
FoxPro
Java
Perl
PHP Extension
PHP ActiveX
Python
PowerShell
Ruby
SQL Server
VBScript
|
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: LOCAL loFtp LOCAL lnSuccess LOCAL lnFailReason loFtp = CreateObject('Chilkat.Ftp2') * Any string unlocks the component for the 1st 30-days. lnSuccess = loFtp.UnlockComponent("Anything for 30-day trial") IF (lnSuccess <> 1) THEN =MESSAGEBOX(loFtp.LastErrorText) QUIT ENDIF loFtp.Hostname = "ftp.****.com" loFtp.Username = "****" loFtp.Password = "****" * Connect and login to the FTP server. lnSuccess = loFtp.Connect() IF (lnSuccess <> 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. * lnFailReason = loFtp.ConnectFailReason ? "connect fail reason = " + STR(lnFailReason) =MESSAGEBOX(loFtp.LastErrorText) QUIT ENDIF * ... |
© 2000-2010 Chilkat Software, Inc. All Rights Reserved.
Mail Component · .NET Email Component · ASP Mail Component · XML Parser