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

Scheduled scan issue with SQL 2008R2

We are see interuptions with our web applications due to a Sophos scheduled scan on a SQL 2008R2 server. Here is one of the many errors of the same that is in the event log and SQL error log when the scheduled scan begins. On access does not appear to be an issue.

"The client was unable to reuse a session with SPID 337, which had been reset for connection pooling. The failure ID is 29. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message."

I have moved the scheduled time and the problem moves with the scheduled scan time. I have disabled the schduled scan and have no issues. I have about 8 SQL clusters with this being the only one exhibiting this behaviour. I have setup the best practice for exclustions for SQL servers for the policy. Reinstall didn't help.

Any ideas or suggestions welcomed.

:43907


This thread was automatically locked due to age.
Parents
  • The scan lasts about 1.5 hours but this interuption seems to be about the first 2-5 mins of the scan starting then stops being and issue. All of the scanning options are check EXCEPT inside archived files. There are no failed operations before this going on.

    Yes the scan is scheduled from the colsole. No I have not tried scheduling it locally or each option. This will take some time given its a production server and their are specific times that i can try this given that its a known issue.

    :43925
Reply
  • The scan lasts about 1.5 hours but this interuption seems to be about the first 2-5 mins of the scan starting then stops being and issue. All of the scanning options are check EXCEPT inside archived files. There are no failed operations before this going on.

    Yes the scan is scheduled from the colsole. No I have not tried scheduling it locally or each option. This will take some time given its a production server and their are specific times that i can try this given that its a known issue.

    :43925
Children
No Data