W2K3 SP1 ftp client - file get can't use share or UNC path

Got a ftp process that's been using either a share path or UNC.
"get filename \\servername\share" or "get filename \\servername\d$\dir"
This will not work with SP1; get Rename "calloc: file exists" error. OK
using local drive letters but the process can't use it without a significant
code change.

Anyone seen this & worked around it?

I had nearly the same problem, except in my case it was failing because I
executed the FTP script from the C: drive and the destination path was on the
F: drive. There is a Hotfix to address this problem, but you need to contact
Microsoft Support to obtain it (see this KB article:
http://support.microsoft.com/default...;en-us;899679).

However, we were able to work around the problem by using "lcd
<target_path>" prior to executing the "Get" statement. Hope this helps.


"gew" wrote:

> Got a ftp process that's been using either a share path or UNC.
> "get filename \\servername\share" or "get filename \\servername\d$\dir"
> This will not work with SP1; get Rename "calloc: file exists" error. OK
> using local drive letters but the process can't use it without a significant
> code change.
>
> Anyone seen this & worked around it?

Thx Michael, yea this hotfix was a result . Good stuff huh?

"Michael Walleisa" wrote:

> I had nearly the same problem, except in my case it was failing because I
> executed the FTP script from the C: drive and the destination path was on the
> F: drive. There is a Hotfix to address this problem, but you need to contact
> Microsoft Support to obtain it (see this KB article:
> http://support.microsoft.com/default...;en-us;899679).
>
> However, we were able to work around the problem by using "lcd
> <target_path>" prior to executing the "Get" statement. Hope this helps.
>
>
> "gew" wrote:
>
> > Got a ftp process that's been using either a share path or UNC.
> > "get filename \\servername\share" or "get filename \\servername\d$\dir"
> > This will not work with SP1; get Rename "calloc: file exists" error. OK
> > using local drive letters but the process can't use it without a significant
> > code change.
> >
> > Anyone seen this & worked around it?