My lab has 5 networked computers which are running XP Pro (all configured identically). I am able to transfer any type of file back and forth between four of the computers, but if I try to copy/move to one particular computer, I get an error message saying "cannot copy [file name]: the I/O operation has been aborted because of either a thread exit or an application request." The odd thing is that I can transfer a 30-40Mb folder and everything will move over smoothly until it gets to an .rtf file created in MS Word 97. If I take the .rtf file out of the folder and try moveing the folder again - no problem. I tried changing the delinquent file's extension to .doc with no luck. Any suggestions would be greatly appreciated.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
file transfer problem over network
- Thread starter spindle
- Start date
The problem may have to do with an embedded binary image in the document.
Two avenues of research for you:
1. Try it without anti-virus sofware running, particularly on the destination computer for the copy.
2. Try the copy from a DOS session explicitly stating a binary transfer mode (copy /b <folder source> <folder destination>
Two avenues of research for you:
1. Try it without anti-virus sofware running, particularly on the destination computer for the copy.
2. Try the copy from a DOS session explicitly stating a binary transfer mode (copy /b <folder source> <folder destination>
- Thread starter
- #3
Dear bcastner,
Thank you for your response.
1) These are 1 week old systems and we have not installed anti-viurs software as yet, so that should not be an issue.
2) I tried copying from DOS, as suggested, but got the same error message as I indicated in my original posting.
Thank you for your response.
1) These are 1 week old systems and we have not installed anti-viurs software as yet, so that should not be an issue.
2) I tried copying from DOS, as suggested, but got the same error message as I indicated in my original posting.
- Thread starter
- #6
Dear bcastner,
SP1 is not on any of the computers. Unfortunately, none of the stations have internet access, which will present some difficulties in getting SP1. However, if an update to XP was the problem, I would expect the same difficulties transferring Word files on all the stations. If I put the .rtf file on a CD or floppy, I can copy it onto the "trouble" computer and view the document with no problem.
SP1 is not on any of the computers. Unfortunately, none of the stations have internet access, which will present some difficulties in getting SP1. However, if an update to XP was the problem, I would expect the same difficulties transferring Word files on all the stations. If I put the .rtf file on a CD or floppy, I can copy it onto the "trouble" computer and view the document with no problem.
- Thread starter
- #7
I just tried to xcopy the file. I got the same error message as befor with one exception: it began with "file creation error" instead of "cannot copy [file name]". It sitll lists a thread exit or an application request as the souce of the problem.
It is too bad about the Internet Access.
My "gut" feeling is that one of three possibilities for the error exist on the troublesome box:
1. A DMA error on the hard drive. I would love to see that box have the "Intel Application Accelerator" software patch applied if appropriate.
2. Paged pool memory exhaustion. SP1 would apply in this case, aided perhaps by more RAM in the box.
3. Least likely, but possible: an Ethernet NIC driver problem. If the NIC is ADMTek or Realtek chip-based this driver issue jumps from least likely to very highly possible as the source of the problem. But you would need to go to their Web Sites to get the newer driver.
My "gut" feeling is that one of three possibilities for the error exist on the troublesome box:
1. A DMA error on the hard drive. I would love to see that box have the "Intel Application Accelerator" software patch applied if appropriate.
2. Paged pool memory exhaustion. SP1 would apply in this case, aided perhaps by more RAM in the box.
3. Least likely, but possible: an Ethernet NIC driver problem. If the NIC is ADMTek or Realtek chip-based this driver issue jumps from least likely to very highly possible as the source of the problem. But you would need to go to their Web Sites to get the newer driver.
- Thread starter
- #9
Dear bcastner,
Thank you for your time and effort. I've spent a lot of time on this and in the end, as usual, the simplest approach worked; I reinstalled MS Office on all 5 stations and this, for whatever reason, resolved the problem. Once again - thank you.
Spindle
Thank you for your time and effort. I've spent a lot of time on this and in the end, as usual, the simplest approach worked; I reinstalled MS Office on all 5 stations and this, for whatever reason, resolved the problem. Once again - thank you.
Spindle
I am happy you got it to work.
But it baffles me as to why Office was in play at all. I can understand why it could possibly effect a transfer under Windows Explorer, as XP takes its File Association business very seriously and the .rtf handler, whatever it may be, could have been involved.
But from DOS, even with a binary switch?
Baffling. I will definately keep that in mind as a workaround/fix to explore for file transfer problems.
Best.
But it baffles me as to why Office was in play at all. I can understand why it could possibly effect a transfer under Windows Explorer, as XP takes its File Association business very seriously and the .rtf handler, whatever it may be, could have been involved.
But from DOS, even with a binary switch?
Baffling. I will definately keep that in mind as a workaround/fix to explore for file transfer problems.
Best.
- Thread starter
- #11
Hi again bcastner.
I spoke too soon the last time. After initially solving the problem, the file transfer bogged down again on the one box, with the same error message. What I tried next was reinstalling the reports that generate the .rtf files on each of the stations. These reports summarize data on sleep studies which we run at my lab. The reports consist of dozens of individual components (each with it's own string of programming code). I think that one of these components may not have installed properly the first time. I say this because after reinstalling the components from the original disk, I was able to generate the .rtf files and move them back and forth without problems (that sounds familiar). Reinstalling MS Office was a temporary fix because this probably just "reset" things which only got bunged up again once I generated the faulty reports. How everything interacted here to create the problem in the first place, I don't know - baffling is right!
Spindle
P.S. It's nice to see people taking the time to help out novices like us, even when we don't give you much to go on. Cheers.
I spoke too soon the last time. After initially solving the problem, the file transfer bogged down again on the one box, with the same error message. What I tried next was reinstalling the reports that generate the .rtf files on each of the stations. These reports summarize data on sleep studies which we run at my lab. The reports consist of dozens of individual components (each with it's own string of programming code). I think that one of these components may not have installed properly the first time. I say this because after reinstalling the components from the original disk, I was able to generate the .rtf files and move them back and forth without problems (that sounds familiar). Reinstalling MS Office was a temporary fix because this probably just "reset" things which only got bunged up again once I generated the faulty reports. How everything interacted here to create the problem in the first place, I don't know - baffling is right!
Spindle
P.S. It's nice to see people taking the time to help out novices like us, even when we don't give you much to go on. Cheers.
- Status
Similar threads
