Does anyone know what this error message means:
 
"Cannot copy WORKOUT: Data error (cyclic redundancy check)."
 
When you click on OK, the copying process stops and that file and any files that were behind it, do not copy or backup.  Actually, that file is completely gone from the DEFAULT folder on the backup.
 
The file WORKOUT.B is 91,914 BK and was last accessed at 1:08 PM today.
 
Actually, I was working in DBA prior to the backup and did not experience anything unusual.  No errors, no hickups, no power flicker, etc.
 
I am on DBA V2004.1 with ISTECH Support Update 5/1/07.  My PC is Windows XP.  
 
Not had this before and don't know what to make of it, except that I know I'm not backup up and I feel naked!!
 
Thanks to anyone that has seen this and knows what the problem is.
 
Teresa Heran
Armature Coil Equipment, Inc
 
PS. Even tho my ID says that I am a browser, I am a member (Bronze)

Yup, I misspelled the file name.  I tried to copy a screen shot to this page, but I gave up.
 
Anywho,  if the file name was spelled correctly, would you know what that error means and what I should do about it?

I rebooted the PC and tried again.  Same error message.
I tried a fresh backup tape.  Same error message.
 
Is something wrong with that file?  I'm afraid to work in DBA until I get this figured out.

the DBAMFG folder is on the server (NT4).  So I should run a scan disk of the file server?  Should I close all programs running on the server when I do this?

Quote from Theran on 06/17/07 at 08:09:17:

 
Yes, you should run scandisk on the machine that the harddrive is located in. So the fileserver would be the place for that. Additionally, it is a good idea to close all other programs so that nothing else interferes.
 
You could try reindexing the file so long as that has no risk of destroying anything. I don't remember off hand whether it is risky or not. If it is then Evo/DBA is usually pretty good at warning you first so you can back out.
 
It's possible that the start of the file is corrupted and that it's still possible to add records because the end is not corrupted. I still think that it couldn't hurt to thoroughly (that is one of the scandisk options) run scandisk to make sure that the harddrive is in good shape.

Quote from Theran on 06/17/07 at 09:07:27:

 
Good deal!  It's always good when you can finally get to the bottom of a frusterating mess like that.

Make sure the server budget includes the Pervasive upgrade.  PSQL 2000 is not supported on WIN 2003 server.  Contact me for upgrade pricing.