Environment versions
Network:
Windows 2003 Server
Thanks Craig. I'll pass this message along to our hardware guys but they maintain there is nothing wrong with the network or the cabling. The strange thing is that the other program that also uses the mapped drive never has these errors (except right after the transfer program errors out).
I was just reading on another thread that it's suggested to put "tmpfiles='c:\temp'" into the config.fpw to force the program to create temp files on the local drive to get rid of these errors. Worth a try. This is making me nuts ;-).
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only