Globalscape Eft Server Error Codes
Contents |
Enterprise » EFT Server Client Log Explained EFT Server Client Log Explained 4 Years Ago GlobalSCAPE 5 EFT SMB & EFT Enterprise THE INFORMATION IN THIS ARTICLE APPLIES TO: EFT Server (All Versions) DISCUSSION When EFT ftp error codes Server’s Download and Copy/Move action offloads or downloads files to/from other servers,
Ftp 421 Error
the session is recorded to a log file: cl[yymmdd].log, e.g., cl060312.log. The log file is formatted as follows: Time; sftp return codes Protocol; Host Name; Port; User Name; Local Path; Remote Path; Operation; GetLastCode For example: 2006-03-06 10:11:03; ftp; 192.168.20.171; 21; ClientA; C:\test1.txt; /test1.txt; download; 226; (In v6.4 and later) A tenth ftp error 421 service not available column can be added to the CL log by defining a registry entry. The tenth column indicates status of the Event, Success (0) or Failure (1). To enable the tenth column, create the DWORD Enable10ColumnInClientLog at the following path: 32-bit: HKEY_LOCAL_MACHINE\SOFTWARE\GlobalSCAPE Inc.\EFT Server 4.0 64-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\GlobalSCAPE Inc.\EFT Server 4.0 Value: - 0 or not present = disabled - 1 = enabled With
Ftp Return Codes Mainframe
the tenth column enabled, the CL log columns are: TIME; PROT: HOST:PORT; USER; LOCAL_PATH; REMOTE_PATH; OPERATION; LAST_RESULT_CODE; ACTION_RESULT If ACTION_RESULT = 0, any "if action FAILED" Actions in the Rule are skipped. The log can be used for trouble-shooting connection and transfer errors. The "GetLastCode" value returns the protocol success or error code or socket error. For example, trying to connect to an non-existent website will result in the socket error code 10060, connection timeout. See a Microsoft Library article for a complete list of common socket error codes. Aside from the standard socket error codes (1nnnn), EFT Server defines a few of its own: 0 - Success (connected ok) 1 - General socks failure 2 - Socket connection not allowed by ruleset 3 - The network is unreachable 4 - The host is unreachable 5 - The remote server actively refused the connection 6 - The Time To Live (TTL) expired. This could indicate a network problem. 7 - The command was not supported by the remote host. Also a catch all error code. 8 - The address type or format
the most common status and error codes. When determining a course of action, review the entire log; some codes are informational only, others indicate that ftp response 421 received. server closed connection. you have entered the wrong information, and others indicate what information you ftp error 451 need to provide before continuing. If a remote server is actively refusing your attempt to connect to it, try
Ftp Command Codes
the following to correct the error: Verify that the destination server name, IP address, and port numbers are correct. Try again later. The remote server may be temporarily or permanently https://kb.globalscape.com/KnowledgebaseArticle10262.aspx inaccessible Verify that you have chosen the right protocol (SSH2, SSL, FTP, etc.) and have configured all required options for that protocol. Try using only one connection thread when connecting to this particular server. The remote server may be refusing multiple connections from the same client. Try pinging the IP address of the server. If you are using a router, http://help.globalscape.com/help/archive/eft5/admin/ftp_status_and_error_codes.htm verify the router is up and running. (Check it by pinging it and then ping an address outside of the router.) Use tracert to verify all routers along the connection path are operational. Verify that your subnet mask is configured properly. Verify that your local software or hardware firewall is not blocking outbound connections originating from your FTP client. Disable your anti-virus software to determine if it is blocking the connection. Code Description Possible Solutions: 100 Series The requested action was initiated; expect another reply before proceeding with a new command. 110 Restart marker reply. (Informational) 120 Service ready in nn minutes. (Informational) 125 Data Connection already open, transfer starting. (Informational) 150 File status okay, about to open data connection. FTP uses two ports: 21 for sending commands, and 20 for sending data. A status code of 150 indicates that the server is about to open a new connection on port 20 to send some data. (Informational) 200 Series The requested action has been successfully completed. 200 Command okay. (Informational) 202 Command not implemented, superfluous at this site. (Informational) 2
Enterprise » Does EFT Server have some sort of reporting or logging feature... Does EFT Server have some sort of reporting or logging feature for troubleshooting? 3 Months Ago GlobalSCAPE 5 EFT SMB https://kb.globalscape.com/KnowledgebaseArticle11047.aspx & EFT Enterprise THE INFORMATION IN THIS ARTICLE APPLIES TO: EFT, version 6.0 and later QUESTION Does EFT have some sort of reporting or logging feature for troubleshooting? ANSWER Yes! ARM includes the following preconfigured troubleshooting reports in which you can include or exclude fields to create custom reports: Troubleshooting - Connection Errors - This report displays the number ftp error of connection errors occurred while connecting to a Site. Troubleshooting - IP Address Activity (Detailed) - This report displays the details of the user, the date/Time on which the user logged on to EFT; other details such as local port, socket result ID, protocol, password, physical folder name, virtual folder name, and so on are also displayed. To view ftp return codes this report, you must specify the IP address in the Enter Report Parameters dialog box that opens when you click Show Report. Troubleshooting - Operation Errors - This report displays protocol error codes and corresponding commands, sorted in reverse chronological order. The report includes the date and time the error occurred, remote IP address, protocol used, username, command, filename, virtual folder, and result (e.g., transfer completed). Troubleshooting - Event Rules Failures - This report displays failures related to the Event Rules. For details ofARM reports,refer to "The Auditing and Reporting Module" section of the EFT help documentation. You can also use the EFT logs to assist with troubleshooting: The main EFT activity log is saved in the Logs subdirectory of the installation directory (e.g., C:\Documents and Settings\All Users\Application Data\GlobalSCAPE\EFT Server Enterprise\Logs; on Windows 2008, Application Data files for all users are in a hidden folder named %systemroot%\ProgramData). The file name depends on the log file format (ex, in, nc) and the date/time it was created. For example, a log file in the Microsoft IIS form