Thread Info
  • State Not Answered
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 2 replies
  • Subscribers 5 subscribers
  • Views 17677 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

Problems with SAVOnAccess timeouts on RDS servers

Kevin_Beaumont

Hi,

We've run Sophos Endpoint Control for 15+ years without issue, however now.. we got issues.

 

On our Windows Server 2008 R2 RDS (thin client) farm, which has been in place since 2012 and not modified recently, our servers are starting to grind to a halt.

The cause is Sophos, during the issues the servers start logging hundreds of error 85 via SAVOnAccess in the System event log.  The error talks about a timeout/busy condition scanning files and registry entries.

The problem usually occurs across multiple servers, and the fix is to reboot the server.  We have 100+ users per server, so it's a bit of an issue for us.

Anybody else seen this?  Using the Recommended branch of Sophos Endpoint Control via Sophos Enterprise Console.



This thread was automatically locked due to age.
Parents
  • 0

    Hi Kevin

     

    We have seen a similar thing in 2008R2 and 2012R2 servers - these are not in an RDS farm but have all the same symptoms described above.


    Would be interested in knowing if others are having this issue.

     

    Stuart

Reply
  • 0

    Hi Kevin

     

    We have seen a similar thing in 2008R2 and 2012R2 servers - these are not in an RDS farm but have all the same symptoms described above.


    Would be interested in knowing if others are having this issue.

     

    Stuart

Children
  • 0 in reply to StuK

    Hello Kevin and Stuart,

    you are talking about scan succeeded following a timeout/busy condition, aren't you?
    Please contact Support directly - obviously it affects performance and availability. 

    Christian 

Unfiltered HTML