@cumbia : Most of the McAfee-related references to Event Id 257 are for VirusScan Enterprise. Is that what you are running?
btw, that DAT version looks to be well out of date. The current DAT is 6626. I should update that asap.
Yes, VirusScan Enterprise is what's running.
When McAfee has taken too long to complete a scan and cancels the scan, does it also cancel the execution of the program?
This has been moved to the Business section (VSE) for attention.
@cumbia, see if the document to which Lakshmanan provided a link has the answer to your question. If not, this has been seen before so someone here should be able to tell you what you want to know.
Thank you for moving it to this section. The document at that link did not provide the answer.
the scan could have been triggered on a read access to that .DLL or a rename operation, etc. when scanning is cancelled it should merely "stand aside" and let the original file access go on without doing anything.
Please take a look at KB55869 in this respect.
Note that virusScan for Linux has an option for action to take on OAS timeout (where you can choose "deny access") whereas Virusscan for windows does not.
Thank you, your reply answers my question.