Wanted to post something here; just in case some one has some ideas. I have a case open with technical support, but we're still waiting on resolution at this point.
SQL 2012 (Hosted on Windows 2012 - Seperate System)
The On-Access scanner for MSMS 3.0 is either crashing or timing out when users are requesting content. This content can be web pages, pictures, documents, scripts, etc... The content it crashes on is inconsistant--meaning it's completely random--some time it works and sometimes it doesn't. The result to the end user depends on which files the scanner crashes on--if it's a picture, they get a "red X"; if it's a master page or *.css file, the page is completely hosed. Using a fiddler trace, the HTTP header for the requested/failed content contains a 409 Conflict Header.
When the issue is experienced, the SharePoint WFE logs an event 8330: "Failed to scan file /_catalogs/masterpage/<someTypeOfFile.xxx> due to scanner crashed."
The ULS logs at the same time log a number of events that point to a scanner crash, timeout, or both. Some examples are as follows:
w3wp.exe (0x40F8) 0x05EC SharePoint Foundation Files 8330 Critical Failed to scan file /_catalogs/masterpage/<someTypeOfFile.xxx> due to scanner crashed. 507c4f9c-bd20-1038-cd7f-c52ef5473130
w3wp.exe (0x40F8) 0x05EC SharePoint Foundation Files ajpma Medium Completed virus scan. HR=0x80041053, Status=0 507c4f9c-bd20-1038-cd7f-c52ef5473130
w3wp.exe (0x40F8) 0x05EC SharePoint Foundation Files ajpmb Medium Virus status for Download: 9830412 - scanner timeout - <CLAIMSUSERHERE> - /_catalogs/masterpage/<someTypeOfFile.xxx> 507c4f9c-bd20-1038-cd7f-c52ef5473130
w3wp.exe (0x40F8) 0x05EC SharePoint Foundation Files aiv4w Medium Spent 140 ms to bind 78689 byte file stream 507c4f9c-bd20-1038-cd7f-c52ef5473130
w3wp.exe (0x40F8) 0x05EC SharePoint Foundation Files aise3 Medium Failure when fetching document. 0x80041054 507c4f9c-bd20-1038-cd7f-c52ef5473130
There is also a unhandled exception / stack trace that references the STS2VsapiX64.dll. I'm not including it at this point since it is a lengthly trace...
My feeling on the matter is that it has something to do with a timeout setting for the on-access scanner, but I don't see any way to modify that. The only timeout setting I see is the one in SharePoint CA/Anti Virus Settings that defaults to 300 seconds. The ULS logs above are referenced time periods in milliseconds, so that setting doesn't seem to apply here.
Any help / insight that you guys may have would be greatly appreciated. If/when I get a possitive resolution I share here to make sure everyone can benefit.
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.