Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 1 subscriber
  • Views 3799 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

Sophos error re folder doesn't exist

ClaireJoanne

Hi there

I keep being notified on the Enterprise Console regarding errors on workstations - these errors tell me about folders users have tried to access that don't exist.

I have the option then to acknowledge the error - is this all I have to do?

Many thanks

:10553


This thread was automatically locked due to age.
  • 0

    Hello ClaireJoanne,

    this might be normal in which case you simply acknowledge these errors. Just to make sure, could you post one or two of these messages here?

    Christian

    :10579
  • 0

    Hi Christian

    These are the types of message I am seeing:

    The folder "C:\Documents and Settings\dparker\ApplicationData" doesn't exist

    Sometimes they refer to specific apps eg: Adobe.

    They are in different users folders as well.

    Do you think I can just acknowledge them?

    Thanks

    Claire

    :11119
  • 0

    Hello Claire,

    The folder "C:\Documents and Settings\dparker\ApplicationData" doesn't exist

    Seems somewhat strange. Now - do these folders exist? And can you determine which kind of scan (locally set up, scheduled from SEC, ...) is reporting these errors?

    Christian

    :11131
  • 0

    These folders don't seem to exist.  I have an error today that says 'The on access driver failed to read from file' and then there is a path to a Tux Paint file

    I think I may just have to acknowledge these errors as they don't seem to be causing any other problems.

    Claire

    :11171
  • 0

    Hello Claire,

    The on access driver failed to read from file

    This happens from time to time and can be considered normal if it's not too frequent.

    It's probably the best choice to set a "baseline" by acknowledging all these errors. When you get new ones you should perhaps investigate one or two in detail (is there additional information in SAV.txt, what kind of scan is involved, does the file/folder exist, could it be locked exclusively). You'll quickly get more confident dealing with these errors - and yes, this is usually to simply acknowledge them.

    Christian

    :11179
  • 0

    Hi Christian

    I think you're right.

    I managed to speak to one othe user's after an error was reported and she said that she'd tried to open a pdf file she'd created on one pc, on another that didn't have Adobe on and this was what had caused the error.

    At least now I can see why this is happening.

    Many thanks for all your help.   :-)

    Claire

    :11225