THE INFORMATION IN THIS ARTICLE APPLIES TO:

• EFT Server, all versions

QUESTION

I am configuring EFT Server to send files received in a user's folder to our back end system where they will be processed. The files are ASCII data files and the back end system is a Solaris server. Therefore I need to be able to specify that the file transfer is an ASCII file transfer.

How can I do this?

ANSWER

In EFT Server version 6 and later, you can specify the file typesto transfer in ASCII mode in the Advanced Options dialog boxof the Copy/Move Action and the Download Action. Refer toCopy/Move (push) File to Host Action andDownload (pull) File from Host Action in the EFT Server helpdocumentation for details.

In version 4 only:

As a rule, ASCII files are simply those that are plain text and as a result, may require some translation of the different End Of Line characters. First, try it with the default configuration and only worry about changing to ASCII if you find that the file is unreadable or the back end system cannot process the file correctly.

EFT Server's Copy/Move functionality, when connected using FTP/S (neither SFTP nor HTTP/S have ASCII or Binary modes), will transfer all files using Binary mode by default except for a list of specific file name extensions which will betransferred in ASCII mode. If a file being transferred has a file name extension that matches one of the file name extensions in the list, it will be transfered in ASCII mode. Otherwise the default Binary mode is used. The default list of ASCII file name extensions includes the following entries:

If the file to be transferred has any other extension, it will be transferred in Binary mode. This list is stored in the registry as a binary value for the ASCIIFileExts entry at HKEY_LOCAL_MACHINE\SOFTWARE\GlobalSCAPE Inc.\TED 6\Settings\FileTypes.

Unfortunately, EFT Server v4 does not have a configuration option that will let you edit this list. If you need to make changes, then the easiest way is to use CuteFTP Pro to create a list of file name extensions that will be stored in the registry and then copy that registry subkey to the correct EFT Server registry key. Follow these steps to make the changes:

Caution: The following steps involve editing the Windows registry on the server computer. Incorrectly editing the registry may severely damage your system. These instructions are intended for the advanced user who is prepared to both edit and restore the registry. We recommend that you backup the registry on the server computer before proceeding.

1. Start CuteFTP Professional.
2. On the Tools menu, click Global Options.
3. Expand Transfer and then click ASCII Types.
4. Edit the list of ASCII file name extensions as needed. (Note: This process does not append to the existing list of file name extensions in the registry. The list you create here should contain all of the file name extensions shown above as well as the entries you want to add to the list.)
5. Click OK and then close CuteFTP Professional.
6. In Windows, click Start and then click Run.
7. Type regedit and click OK to start Registry Editor.
8. Navigate to HKEY_CURRENT_USER\Software\GlobalSCAPE\CuteFTP 7 Professional\Settings.
9. Expand Settings, right-click FileTypes and then click Export.
10. Type a file name and save it to a convenient location as a .reg file.
11. Close Registry Editor.
12. In Windows Explorer, right-click on the file name exported in step 10 above and click Edit.
13. Replace the existing subkey path (shown between brackets) with:

HKEY_LOCAL_MACHINE\SOFTWARE\GlobalSCAPE Inc.\TED 6\Settings\FileTypes

14. Save the file and close the editor.
15. In Windows Explorer, double-click the newly created .reg file saved above and add the information to the registry.
16. Stop and then restart the GlobalSCAPE EFT Server service to make the changes effective.

When finished, EFT Server will use the new ASCII file name extension list.

THE INFORMATION IN THIS ARTICLE APPLIES TO:

• EFT Server, version 6 - 6.3

SYMPTOM

No emails are sent from AWE actions.

RESOLUTION

Add the following entries to the Windows Registry, depending on your EFT Server version and operating system. Edit the entries to correspond with your domain and user information. (If you use the attached .txt file, be sure to edit the file with your values, then change the file extension .reg before executing it. Don't double-click the link; right-click it, then save the file on your desktop.)

Registry Location:

For EFT Server v6.3 on a 32-bit OS:

[HKEY_LOCAL_MACHINE\SOFTWARE\Network Automation\Automate 8\TaskService]

For EFT Server 6.3 on a 64-bit OS:

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Network Automation\Automate 8\TaskService]

For EFT Server v6.2 on a 32-bit OS:

[HKEY_LOCAL_MACHINE\SOFTWARE\Network Automation\Automate 7\TaskService]

For EFT Server 6.2 on a 64-bit OS:

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Network Automation\Automate 7\TaskService]

For EFT Server 6.0.x and 6.1.x on a 32-bit OS:

HKEY_LOCAL_MACHINE\SOFTWARE\Network Automation\BPA Agent\TaskService]

For EFT Server 6.0.x and 6.1.x on a 64-bit OS:

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Network Automation\BPA Agent\TaskService]

Values:

MORE INFORMATION

The SMTP configuration within EFT Server is not visible from the AWE module; therefore, you must add the registry values as described above to tell the AWE module which SMTP server and port to use.

THE INFORMATION IN THIS ARTICLE APPLIES TO:

• EFT Server (All versions)
• Mail Express (v3 and later)
• DMZ Gateway (All versions)

QUESTION

How can I change the ping interval between DMZ Gateway and the server?

ANSWER

• The Server always establishes the connection to DMZ Gateway Server through an outbound socket connection.
• DMZ Gateway never establishes connection with the Server.
• The DMZ Gateway routes all client data to the Server over the the Server-initiated socket without any translation or modification to the packet’s payload.
• To maintain security in the DMZ, DMZ Gateway Server does no interpretation whatsoever of data; it does not use a store-and-forward architecture, it is purely a forward architecture. If the connection is "plain vanilla" FTP, then it is forwarded as plain vanilla FTP. It is not modified nor inspected between the DMZ Gateway and the Server.
• The Server queries the DMZ Gateway once every 5 minutes. If a reply is not received within 10 seconds, the Server considers the connection lost, severs the current connection, and then attempts to reconnect. The DMZ Gateway also maintains its own awareness (ping/pong) of whether the Server is connected. Periodically, DMZ Gateway determines whether it has received a pong message from the Server since the last ping. If it has, it will ping again; if not, it drops the connection. This allows it to free up ports if EFT Server is not available (no longer responds to ping) and for error reporting.

If there is a device between EFT Server and DMZ Gateway that is terminating idle connections, in version EFT Server v6.2 and later (with DMZ Gateway v3.0), you can edit these settings:

• Changing the DMZ Gateway's Ping Interval—By default, DMZ Gateway will send a PING message to EFT Server every thirty seconds. This value is specified within the gwconfig.xml file that resides in the root DMZ Gateway installation directory. Stopping DMZ Gateway Service prior to making these changes is required. The value (in milliseconds) can be specified at the global level by modifying the configuration value "GlobalPNCKeepalivePeriod". Alternatively, the value can be modified on a per-site basis by specifying a new element named "PNCKeepalivePeriod" within the "Profile" element.
• Changing the EFT Server's Ping Interval—By default, EFT Server sends a PING message to DMZ Gateway every 5 minutes. This value can be overridden by adding a DWORD entry to the Windows Registry. The DWORD value must be named "gw_keepalive" and the value is specified in SECONDS. The location of the key is as follows: [HKEY_LOCAL_MACHINE\SOFTWARE\GlobalSCAPE Inc.\EFT Server 4.0\Config]. EFT Server must be restarted in order for this change to take effect.

On a 64-bit OS, the location is [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\GlobalSCAPE Inc.\EFT Server 4.0\Config].



For more information about DMZ Gateway-><-Server communication, refer to Introduction to GlobalSCAPE^® DMZ Gateway.

THE INFORMATION IN THIS ARTICLE APPLIES TO:

• EFT Server, v6 and later that run on 64-bit Windows operating systems

DISCUSSION

To edit the registry for EFT Server on a 64-bit operating system, you must type the entire path to regedit.exe in the SysWOW64 directory. 

1. Click Start > Run, type 

   C:\Windows\SysWow64\regedit.exe

2. Click OK or press ENTER.

 

THE INFORMATION IN THIS ARTICLE APPLIES TO:

• EFT Server, version 6.2.5 and later

QUESTION

Can I specify the system type so that I can switch from UNIX to Windows NT?

ANSWER

A SYST request asks for information about the server's operating system. The server accepts this request with code 215. EFT Server, and most servers, respond with 215 UNIX Type: L8:

Some clients disable essential features when they do not see particular strings in the SYST response. If your server requires a particular response, EFT Server provides a registry setting with which you can specify the value returned by the FTP SYST command.

32 bit: HKLM\SOFTWARE \GlobalSCAPE Inc.\EFT Server 4.0\FTPSYSTResponse

 Value data: Windows_NT

The string value provided in the registry will be truncated to 128 characters, if necessary.

After adding the registry key above, the response is 215 Windows_NT:

For more information about the SYST response, refer to http://cr.yp.to/ftp/syst.html.

THE INFORMATION IN THIS ARTICLE APPLIES TO:

• EFT Server Enterprise version 6.2.22 and 6.3

DISCUSSION

The number of seconds that are allowed for an ARM report to execute can be changed from the 60-second default. This value is only read from the registry once, so a restart is required to change the value.

• If the ARM report is being run from within the Reports tab, then the EFT Server administration interface is running the report and only the interface needs to be restarted.
• If the ARM report is being run from an Event Rule Action, then the EFT Server service must be restarted to change this value.

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\

Create DWORD DBTimeout and specify the number of seconds for the ARM report to complete.

THE INFORMATION IN THIS ARTICLE APPLIES TO:

• EFT Server Enterprise version 6.3 and later

DISCUSSION

The local (GlobalSCAPE) Authentication Manager does not read contents from disk again even if you have configured a refresh interval. It just re-reads the internal memory array. This makes it difficult to externally keep two machines synced in a load balanced scenario. You might prefer to have the refresh interval re-read the value from disk, as it does at Site startup time.

To make the authentication manager read from disk instead of internal memory, you can configure a registry entry, as described below.

If the value is missing or zero, the legacy behavior described above prevails; otherwise, settings are reloaded from .AUD file upon each sync with the Authentication Manager.

Add DWORD value ReloadAUDOnSync to the following registry entries:

32-bit:

HKEY_LOCAL_MACHINE\SOFTWARE\GlobalSCAPE Inc.\EFT Server 4.0\GSAM

64-bit:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\GlobalSCAPE Inc.\EFT Server 4.0\GSAM 

Note: Only client permission group information is loaded from the .AUD file; settings (protocols, password security, and other) are stored in a different configuration file.

• EFT Server 6.0.x - 6.2.x (NOT compatible with 6.3.x)
• EFT Server 5
• Not applicable for any version of Secure FTP Server

**This topic is for advanced users. If you are unfamiliar with running Windows scripts, seek help from your network administrator or contact GlobalSCAPE support.**

Copying or migrating EFT Server configuration might be necessary for several reasons, such as:

• Moving a Proof of Concept (PoC) in your staging environment without recreating all the settings and configuration data
• Creating a standard configuration for installation on multiple computers
• Updating EFT Server software with a fresh install rather than patching

The help topic "Copying an EFT Server Configuration to Several Computers" provides the steps to take before moving EFT Server to another location.

If EFT Server's physical file system has been moved, you need to update EFT Server configuration to point to the new location. In the EFT Server administration interface, you specify the path to the Site's root folder; however, pointing to the new root folder causes EFT Server to lose the permissions assigned to EFT Server’s Virtual File System (VFS). To retain all relevant folder permissions and virtual folders, download and extract the scripts in VFS-MigrationScript.zip and use the scripts to copy the VFS permissions to the new root folder structure.

To move the EFT Server root folder

1. Backup the following files in the EFT Server installation directory:
   • FTP.cfg
   • [YourSite].aud
   • All .bak and .update files
   • All certificates/keys/PGPkeys
2. STOP all sites so that user activity (such as folder creation) does not interfere with the migration process.
3. Run the eftVFSExport.vbs script to save permission configuration for the EFT Server Virtual File System (VFS).
4. Copy the current EFT Server Root to the new location. It is important that you copy and NOT move the file system, in case you encounter any errors in the root migration process.
5. Change the EFT Server root folder to the new location:
   1. In the administration interface, expand the Server node, then click the Site node.
   2. On the General tab, in the Site root folder box, specify the new path, then click Apply.

6. Run the eftVFSImport.vbs script to restore folder permissions.
7. Verify that permissions have been restored and all virtual folders exist.
8. Review and update Event Rules to point to the new path, if necessary.
9. Delete the previous root location, if necessary.
10. Start the sites to resume user activity.

Running the scripts

The import and export scripts are visual basic scripts designed for use with cscript.exe. They both take a basic set of command line parameters.

Usage: eftVFSExport.vbs <arguments>

Required Arguments:

Example: cscript.exe eftVFSExport.vbs -s localhost -port 1100 -u admin -p secret -site 0 -f output.txt

NOTE: Use of CScript over WScript is strongly recommended for these scripts, because the scripts are very verbose.

THE INFORMATION IN THIS ARTICLE APPLIES TO:

• CuteFTP Pro® (All Versions)
• CuteFTP® Home (All Versions)
• CuteFTP® Lite (All Versions)

QUESTION

Is CuteFTP compatible with Microsoft Windows 7 and Windows Vista?

ANSWER

CuteFTP 8.3 or later is compatible with all editions of Microsoft Windows 7 and Windows Vista (32 and 64 bit). We have performed limited testing using CuteFTP 5 XP, CuteFTP 6 (Home and Pro) and CuteFTP 7 (Home and Pro) and have found no problems that would keep them from running on Windows 7 or Windows Vista however in some cases, activation may be troublesome or even impossible. In such cases, some older versions of CuteFTP (such as CuteFTP 4.2) may not run on Windows 7 or Windows Vista beyond the 30-day trial period. (For details, please browse to KB Article ID Q10322 - FAQ: Activation and Registration on Windows Vista.)

Known issues that are specifically associated with Windows 7 and Windows Vista are listed below.

1. On 64-bit editions of Windows 7 or Windows Vista, right-click shell integration does not work. This issue will be fixed in a future release.

For activation (registration) instructions, please browse to KB Article ID Q10322 - FAQ: Activation and Registration on Windows Vista.

To find out which version of CuteFTP is installed on your computer, start CuteFTP and then open the Help menu and click About CuteFTP. The most recent version is available for download from the Replacement Software Downloads page.

THE INFORMATION IN THIS ARTICLE APPLIES TO:

• CuteFTP Pro®(All Versions)
• CuteFTP Home (All Versions) (Except ver. 8.0.0 - 8.0.4. See related article.)

SYMPTOM

When attempting a transfer, the following error is encountered:

ERROR:> Child transfer failed.

CAUSE

When transferring a folder that contains a number of files, this error may indicate that one or more of the items inside that folder failed to transfer. You can check your connection log to find a more detailed error describing why the item failed to transfer.

In some other cases, the transfer send and receive buffer size may be set too high for the conditions. This is particularly true in the case of a high-latency or lossy network connection such as what might be experienced when connected via dialup, satellite or legacy CDMA wireless connections. By default CuteFTP uses a transfer send and receive buffer size of 65,536 bytes which is the normal maximum window size of TCP but may be more than your particular network connection or remote FTP server can reliably process.

RESOLUTION

We recommend setting both send and receive buffers to 4096 bytes. For most users lowering the buffer size to 4096 bytes will have little or no noticeable effect on transfer speeds. Advanced users may want to experiment with different buffer settings to obtain the highest reliable speeds.

Follow these steps to change the transfer send and receive buffer sizes:

1. On the Tools menu click Global Options.
2. Click Transfer and then type 4096 for both the Receive buffer and Send buffer size.
3. Click OK and then restart CuteFTP.

If the error persists after changing the transfer send and receive buffer sizes, then it may be necessary to restrict CuteFTP further:

• In either CuteFTP Home or CuteFTP Pro, configure CuteFTP so that only one file is transferred at a time.
• If you are using CuteFTP Home, turn off Turbo Mode:
  1. On the Tools menu click Global Options and then click Transfer.
  2. Clear the Turbo Mode check box and then click OK.
  3. Restart CuteFTP and then retry the transfer. (Important: The change will not be effective until CuteFTP is restarted.)

THE INFORMATION IN THIS ARTICLE APPLIES TO:

• CuteFTP Home versions 7.2 and 8.0
• CuteFTP Pro® versions 7.2 and 8.0

SYMPTOMS

When using CuteFTP, and attempting to initiate a Passive mode data transfer, the following status error is encountered:

COMMAND:> PASV

227 Entering Passive Mode (xxx,xx,xxx,xxx,xx,xxx)

STATUS:> Port collision detected, retrying...

CAUSE

This issue is caused when an attempt is made to use a data port that is already in use. This problem most often occurs when attempting a connection to a server that is experiencing heavy usage.

FIX OR WORKAROUND

Usually, CuteFTP will retry on its own and recover. If the problem persists, try the applicable solution below.

IF YOU ARE USING CUTEFTP VERSION 7.2:

• Update to CuteFTP version 7.2.1 or higher. For most users, the changes made in CuteFTP 7.2.1 will fully address this issue.

IF YOU ARE USING CUTEFTP VERSIONS 8.0.0 OR 8.0.1:

• Update to CuteFTP version 8.0.2 or higher. This issue occurred more frequently in CuteFTP 7.2, 8.0.0 and 8.0.1. For most users, the changes made in CuteFTP 8.0.2 will fully address this issue.

IF YOU ARE USING CUTEFTP VERSION 7.2.1 OR 8.0.2 OR HIGHER:

• Option 1: Disconnect from the server, wait a few minutes and then retry.
• Option 2: Use Port mode. To switch from Passive mode to Port mode, follow the instructions below.
  • Using CuteFTP Home: In the Site Manager, click once on the name of the problem site. On the Type tab, change the Data Connection Type to Use Port.
  • Using CuteFTP Professional: In the Site Manager, right-click on the name of problem site and click Site Properties. On the Type tab, change the Data Connection Type to Use Port.
• Option 3: Configure CuteFTP so that only one file is transferred at a time. For instructions, see GlobalSCAPE Knowledgebase Article 10448.
• Option 4: If the error persists, please contact the GlobalSCAPE Technical Support Team. If it exists, please be prepared to provide a copy of the auto-generated port collision error log file located at C:\Documents and Settings\USERNAME\Application Data\GlobalSCAPE\CuteFTP(or CuteFTP Pro)\8.0\pasvmap.dat.

THE INFORMATION IN THIS ARTICLE APPLIES TO:

• CuteFTP Home (All Versions)
• CuteFTP Pro® (All Versions)

SYMPTOMS

When using AOL, and attempting to connect to an FTP site, the following error message is encountered:

Too many gateway sessions

CAUSE

This problem is not caused by CuteFTP, therefore, we cannot offer a solution.

The message "too many gateway sessions" means that a connection cannot be made to the AOL server and to try again. This often occurs when AOL is making software updates at the main US server (most often on Sunday).

RESOLUTION

Usually this error can be overcome by signing off of your AOL account and then signing back on during a time when their server is not as busy. If the message continues to appear, contact AOL support.

THE INFORMATION IN THIS ARTICLE APPLIES TO:

• CuteFTP 8 Home versions 8.0.0 thru 8.0.4

PROBLEM

When attempting a transfer, the following error is encountered:

ERROR:> Child transfer failed.

This error may also occur when navigating a remote FTP site and entering a folder that contains a Table of Contents (TOC) file (such as index.txt), in which case CuteFTP Home goes offline and becomes unresponsive. Under those circumstances, see KBase Article ID 10308.

CAUSE

CuteFTP 8 Home has a new feature named Turbo Mode which automatically uses compression and multi-part transfers for the fastest possible throughput.

This error has been found to occur only in circumstances in which either the transfer or the remote folder contains one or more files named *index*, which may be mis-interpreted as being a Table of Contents (TOC) file. CuteFTP may improperly attempt to use Turbo mode when loading or transferring the apparent TOC file, causing the behavior described above.

RESOLUTION

The preferred solution is to update CuteFTP to version 8.0.5 or greater. You can download the most recent release version of CuteFTP from the Replacement Software Download Page.

Alternatively, turn off Turbo Mode for connections to this remote server.

To turn off Turbo Mode:

1. On the Tools menu click Global Options and then click Transfer.
2. Clear the Turbo Mode check box and then click OK.
3. Restart CuteFTP and then retry the transfer. (Important: The change will not be effective until CuteFTP is restarted.)

Note: If the solution provided above does not resolve this problem then it is possible that the transfer send and receive buffer size may be set too high. See the resolution provided in KB Article ID 10293 for further instructions.

THE INFORMATION IN THIS ARTICLE APPLIES TO:

• CuteFTP Home7
• CuteFTP Pro® 7

SYMPTOMS

When starting CuteFTP 7, the following error is encountered:

Incompatible Site Manager format. Do you want to create a new Site Manager and backup the old one?

CAUSE

That error may be encountered if the user has installed CuteFTP 8.0.0 but then decides to return to using CuteFTP 7. The CuteFTP 8.0.0 installer has caused CuteFTP 7 to be incorrectly configured to use the CuteFTP 8 Site Manager data file.

The root cause of this problem has been fixed in CuteFTP 8.0.1 which was released August 17, 2006.

RESOLUTION

Configure CuteFTP 7 so that it uses the correct Site Manager data file as follows:

1. At the error prompt, press CTRL + ALT + DEL to start Windows Task Manager.
2. On the Applications tab, select the CuteFTP task and then click End Task.
3. Close Task Manager.
4. Remove CuteFTP.
   • In Control Panel, double-click Add or Remove Programs.
   • Select CuteFTP from the list and then click Remove and follow the onscreen instructions.

     Note: If both CuteFTP 7 and CuteFTP 8 are listed or if CuteFTP 8 is listed more than once, both should be removed.

5. When finished removing CuteFTP, follow these steps to delete the incompatible Site Manager data file(s):
   • Start Windows Explorer and navigate to C:\Documents and Settings\USERNAME\Application Data\GlobalSCAPE\CuteFTP(or CuteFTP Pro)\7.0\
     • If you cannot find the path specified, then your computer may be configured such that hidden and system folders and files are not shown. In that case, follow these steps to access the correct folder:
       1. Click Start, click Run, type %AppData% and then click OK.
       2. Open the GlobalSCAPE folder, open the CuteFTP Home (or Pro) folder and then open the folder named 7.0 or 8.0 as appropriate.
   • If it exists, move the file named sm.dat to another folder such as your desktop.
   • Navigate to C:\Documents and Settings\USERNAME\Application Data\GlobalSCAPE\CuteFTP(or CuteFTP Pro)\8.0\
   • If it exists, delete the file in that folder named sm.dat.
6. Install CuteFTP 7.
   • Browse to http://www.globalscape.com/support/reg.asp
   • Follow the onscreen instructions to download and install CuteFTP 7.
7. When finished installing CuteFTP 7, you can import a previously saved backup of the Site Manager data file (sm.dat) into the newly created CuteFTP 7 Site Manager as follows:
   • Locate a backup copy of sm.dat.
   • Start CuteFTP.
   • On the Tools menu click Site Manager, then click Import FTP Sites and follow the onscreen instructions. If you need help, press F1 for Help.

If no backup Site Manager data file exists, then your sites in the Site Manager will need to be recreated. If you do not have the login information needed to access your FTP sites then you will need to contact the administrator for the particular FTP site you wish to connect with.

THE INFORMATION IN THIS ARTICLE APPLIES TO:

• CuteFTP 8 Home versions 8.0.0 thru 8.0.4

PROBLEM

When attempting a transfer, the following error is encountered:

ERROR:> Can't merge transferred files.

CAUSE

CuteFTP 8 Home has a new feature named Turbo Mode which automatically uses compression and multi-part transfers for the fastest possible throughput.

This error has been found to occur only in circumstances in which either the transfer or the remote folder contains one or more files named *index*, which may be mis-interpreted as being a Table of Contents (TOC) file. CuteFTP may improperly attempt to use Turbo mode when loading or transferring the apparent TOC file, causing the behavior described above.

RESOLUTION

The preferred solution is to update CuteFTP to version 8.0.5 or greater. You can download the most recent release version of CuteFTP from the Replacement Software Download Page.

Alternatively, turn off Turbo Mode for connections to this remote server.

To turn off Turbo Mode:

1. On the Tools menu click Global Options and then click Transfer.
2. Clear the Turbo Mode check box and then click OK.
3. Restart CuteFTP and then retry the transfer. (Important: The change will not be effective until CuteFTP is restarted.)

Note: If the solution provided above does not resolve this problem then it is possible that the transfer send and receive buffer size may be set too high. See the resolution provided in KB Article ID 10293 for further instructions.

THE INFORMATION IN THIS ARTICLE APPLIES TO:

• CuteFTP Home version 8.0.0 when used on Microsoft Windows 2000
• CuteFTP Pro® version 8.0.0 when used on Microsoft Windows 2000

SYMPTOMS

When using Windows 2000, attempts to navigate local folders by double-clicking on a folder name results in the folder being transferred to the remote site.

CAUSE

CuteFTP 8.0.0 does not properly recognize Windows 2000 folders.

RESOLUTION

Download and install the latest version of CuteFTP. The cause of this problem has been fixed in CuteFTP 8.0.1 which was released August 17, 2006.

THE INFORMATION IN THIS ARTICLE APPLIES TO:

• CuteFTP Pro® (All versions)
• CuteFTP Home (All versions)
• CuteFTP Lite (All versions)

SYMPTOMS

After an unsuccessful upload attempt, files having a size of 0 KB are listed on the remote server.

DISCUSSION

When an FTP client such as CuteFTP attempts to upload a file using the FTP protocol, there are two commands issued: PASV, which asks the server to set up a listening socket on the server end (call this S), and STOR which tells the server the name of the file to be uploaded.

The client then attempts to make a socket connection to the server on the socket S established in the PASV command. Most servers, when they get the STOR command, allocate a filename on the folder system into which the contents of the file will be placed as it is uploaded. This allocation process creates a 0 KB file. When the data socket is connected from the client to S, data arrives and is placed into this file.

However, if the FTP client is not able to make the socket connection to S, which might be because of firewall configuration, network routing problems, server-side being too busy to listen to port S, or the server giving a wrong port number to the client, and so on -- then the end result will be that the client will ultimately TIME OUT on the STOR command. This means that the server will continue to have a 0 KB file reserved for incoming data since it has no real way of knowing when the client will do the data connection.

Some servers will maintain this file placeholder for a period of time (possibly until service restart), which locks the file. Others will time out and release the lock but still keep the file placeholder on the filesystem.

The client software can retry the upload, which CuteFTP does. Depending upon the server, this might or might not work.

Ultimately, the client is doing what it is designed to do. It is the server that controls how to deal with files created for UPLOADS in which the Data Socket cannot be established.

THE INFORMATION IN THIS ARTICLE APPLIES TO:

• CuteFTP Home (All Versions)
• CuteFTP Pro® (All Versions)

DISCUSSION

To return CuteFTP to its original default settings you will need to remove and then reinstall the program.

1. If you no longer have the original CuteFTP setup file, browse to http://www.globalscape.com/support/reg.aspx and download the applicable version of CuteFTP Home or Professional. Older versions of CuteFTP can be found in the list near the bottom of the page. Save the downloaded file to a convenient place such as your desktop.
2. Backup your existing Site Manager.

• Start CuteFTP.
• On the Help menu click Backup Personal & Registration data and then follow the onscreen instructions.
• Close CuteFTP.

When you start CuteFTP for the first time the setting under Global Options will have been reset to the factory defaults but your Site Manager entries and any site-specific options should be intact. If they are not, then you can import them from the backup saved in Step 2 above.

To import Site Manager data, on the Tools menu click Site Manager, then click Import FTP Sites and follow the instructions.

THE INFORMATION IN THIS ARTICLE APPLIES TO:

• CuteFTP Home (All versions)
• CuteFTP Pro® (All versions)

PROBLEM

I selected about 30,000 files and clicked the upload button. Now I've lost control of CuteFTP. When I display the transfer queue or the CuteFTP interface it just hangs and can't even paint the client area. No files are being transferred, but CPU is being used. All I want to do is reset the queue so I can get control back. How can I do this if the transfer queue hangs every time I try to display it?

CAUSE

This can happen if several thousand files are selected and then a transfer is initiated. Preparing that many files for transfer may take a very long time.

RESOLUTION

To clear the CuteFTP transfer queue:

1. Press CTRL + ALT + DEL and then click Task Manager.
2. On the Processes tab, click cuteftppro.exe (or cuteftp.exe) and then click End Process. You may be presented with a warning about stopping the process. Click Yes to end the process.
3. Click ftpte.exe and then click End Process. Again, if you receive a warning screen, click Yes to end the process.
4. Close the Task Manager.
5. Click Start, click Run, type %AppData% and then click OK. (See note below)
6. Open the GlobalSCAPE folder, open the CuteFTP Home (or Pro) folder and then open the folder named 7.0.
7. Rename CIS_Queue.dat to CIS_Queue.dat.broken
8. Restart CuteFTP.

Depending on your operating system, the path to the CuteFTP application data files may differ:

• In Windows XP Pro, the path is by default: %AppData%\GlobalSCAPE\CuteFTP Home (or Pro)\7.0
• In Windows 95 & 98 the path is: %WinDir%\Application Data\GlobalSCAPE\CuteFTP Home (or Pro)\7.0

THE INFORMATION IN THIS ARTICLE APPLIES TO:

• CuteFTP® Home (All Versions)
• CuteFTP Pro® (All Versions)

SYMPTOMS

When attempting to upload a file to the remote FTP site, a 552 error code is encountered, resulting in an error message similar to the following example:

COMMAND:> STOR yourfile.ext

STATUS:> Connecting FTP data socket... 192.168.0.1:21...

150 Opening ASCII mode data connection for yourfile.ext552

Transfer aborted. Disk quota exceeded.

ERROR:> Exceeded storage allocation.

CAUSE

This error is not caused by CuteFTP. The 552 error code is coming directly from the remote FTP server. There is not enough disk space available to you on the remote FTP server. The most common cause for this error is that the limited disk space allocated for your individual FTP account is already in use.

This error may also appear when disk space appears to be available but the file being uploaded is large enough so that if it were uploaded, it would cause your disk space quota to be exceeded.

RESOLUTION

More disk space is needed. You can increase the space available by deleting unnecessary files from the remote server or by making arrangements with your Web hosting provider or FTP account administrator for additional disk space.