Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 3 subscribers
  • Views 8579 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

The on-access driver failed to determine the name for a file

ZaneDonaldson

I am seeing hundreds of these errors in the client's windows event viewer under the System category:

 Event ID 84: The on-access driver failed to determine the name for a file.

 

I am seeing about 30 of these per MINUTE!

 

any help to stop these would be greatly appreciated.

 



This thread was automatically locked due to age.
  • 0

    Hello ZaneDonaldson,

    this is from just a single endpoint, not a conflagration? Couldn't reproduce Polygon-tre's findings in relation to the cause, Jak's post in the same thread shows how to suppress recording in the database, and you can also suppress sending of the alert.

    This isn't normal though. I get it that it is going on for extended periods and maybe across reboots?

    Christian

  • 0 in reply to QC

    we have found that its happening during working hours, so its not happening when the user isn't logged in.  but I haven't found any other relevant information pointing us to the cause of this.

  • 0 in reply to ZaneDonaldson

    Hello ZaneDonaldson,

    so it's confined to the users's (just one user?) session - all the time with a high frequency, just at certain times, or starting some time after logon and then continuing until logoff? Any reports from the user?
    Process Monitor with boot logging enabled filtering to include just process events (Create, Start, Exit) and correlating this with the errors might help to identify the application involved. 

    Christian

Unfiltered HTML