ChatterBank2 mins ago
Corrupt Word Documents
We moved a number of documents to a new server and some appear to have been corrupted in the process. We still have files on the old server to copy again but we don't know how many files that were copied were corrupted without openeing every document. Anyone know of any software that we can run over the transferred files to find the corrupt ones?
Thanks
Thanks
Answers
Best Answer
No best answer has yet been selected by nickpalk. Once a best answer has been selected, it will be shown here.
For more on marking an answer as the "Best Answer", please visit our FAQ.Your only options are:
Do what snadsidney suggests and do the file move again.
or
Move another copy of the old files onto the new server into a different folder (Don't let everyone have access, so you can control who uses them). Then as and when you find a file that is corrupt you can replace it with the old version.
Do you not have an IT Department that can assist with this? Who installed your new server and did the file copy?
Do what snadsidney suggests and do the file move again.
or
Move another copy of the old files onto the new server into a different folder (Don't let everyone have access, so you can control who uses them). Then as and when you find a file that is corrupt you can replace it with the old version.
Do you not have an IT Department that can assist with this? Who installed your new server and did the file copy?
I've seen this happen before when copying lots of files across a Windows network. I suspect (but don't know) that it's a bug in the network redirector.
One way of of overcoming it is to zip all the files on the source machine, copy the zip file to the destination, then (whilst physically sitting at the destination machine) unzip them.
One way of of overcoming it is to zip all the files on the source machine, copy the zip file to the destination, then (whilst physically sitting at the destination machine) unzip them.
Thanks for this, we do have a small IT Dept but it went through some staff changes which will not have helped the problem. At the moment they are waiting until someone complains and then going back to the old server but it would be good to know the extent of the problem (and lose the old server). The Zip solution is one to remember but what we have noticed is that the file size of the corrupted version appear to be different from the original - usually smaller. Accordingly some form of file size comparator might be the answer.
-- answer removed --
-- answer removed --