You receive a "Rename Temp File calloc:File exists" error message when you try to download a file by using the FTP GET command in Windows Server 2003

Consider the following scenario:

• A computer is running Microsoft Windows Server 2003 with Service Pack 1.
• You try to download a file by using the FTP GET command on this computer.
• You specify the destination drive and the directory in the FTP GET command.
• The destination drive that you specify is a different drive than the drive from which you run the FTP GET command.

In this scenario, you receive the following error message:Note You receive this error message after the file appears to be successfully downloaded.

The temporary file that is created during the download process is deleted. Therefore, you cannot successfully download the file by using the FTP GET command.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

Windows Server 2003 Service Pack 1 (SP1) is required to install this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Windows Server 2003, x86-based versions

Windows Server 2003, Itanium-based versions

Windows Server 2003, x64-based versions

To work around this problem, use the FTP LCD command in the FTP session to change the working directory to the destination directory before you run the GET command. For example, to successfully download the file by using FTP, follow these steps:

1. At a command prompt, type ftp URL, and then press ENTER.
   
   URL is the URL of your FTP site.
2. Type lcd d:\, and then press ENTER.
   
   D:\ is the destination directory where you want to copy the file.
3. Type get FileName, and then press ENTER.
   
   FileName is the name of the file that you want to download from the FTP site.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: