When using Symantec Protection for SharePoint Servers 5.1, if a file cannot be saved to the document library. Scan engine found virus: "".


Article ID: 156161


Updated On:


Protection for SharePoint Servers


After uploading a file to Sharepoint Portal Services successfully, you immediately receive the following warning:

File cannot be saved to the document library. Scan engine found virus: "".

Sharepoint Portal Services shows the following error after uploading a file successfully: File cannot be saved to the document library. Scan engine found virus: "".

The Application Event Log may show the following errors:

Level: Error
Source: SideBySide
Event ID: 33

Activation context generation failed for "C:\Program Files\Symantec\SharePoint\SYMAVSPS.dll". Dependent Assembly Microsoft.VC80.CRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4053" could not be found. Please use sxstrace.exe for detailed diagnosis.


Level: Error
Source: WIndows Sharepoint Services 3
Event ID: 26424

"The description for Event ID 26424 from source Windows SharePoint Services 3 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
#960012: Finished loading antivirus scanner. Error -2147010895.
the message resource is present but the message is not found in the string/message table


It is possible there was a problem with the installation of Symantec Protection 5.1 for Sharepoint Services (SPSS), possibly due to a corrupt installation source.


Un-install and re-install Symantec Protection 5.1 for Sharepoint Services.

Please be sure to execute the single SPSS installation file to the actual server under a short path such as "C:\TEMP\SPSSINSTALL". If you choose to extract the installation file using a longer path then you may run into errors during the extraction if the path exceeds 255 characters.