Aggressive anti-virus scan can cause that.

>I have batch jobs running at night, that have begun to abort several times week, with Error 41 - memo file missing or invalid. When the offending table is opened from the Fox command line, the error does not show. As a precaution, I have issued PACK MEMO on each table as they come up. The same table will not cause the next error occurrence after a PACK MEMO. The issue came up in the last few months. I'm not aware of any changes to the file server during this time, although there will have been a number of Microsoft patches and updates applied routinely.
>
>We're running under Win2008 R2 since last May. At that time, I made the server changes to take care of the SMB2 corruption issue, as well as disabled Opportunistic file locking, which seemed to stabilize things.
>
>A little UT research on error 41 suggests I need to disable write-caching? If so, can somebody give me an idea of the impact, and point me to a procedure for making the change?