Archive for the ‘Symantec’ Category

SharePoint File Upload Error Due to Symantec Protection Engine Service Failure

Friday, March 20th, 2015

Version: 1.0

Issue Summary

This has been a little tricky issue. Symantec Protection Engine (SPE) that is part of Symantec Protection for SharePoint Servers (SPSS) product has dependency on JAVA JRE component. A Java update caused the Symantec Protection Engine service on the SharePoint Server to fail. Service fails to start with Error 1053. That lead to file uploads in SharePoint to throw error.

Error Details

Symantec Protection Engine (SPE) component depends on Java JRE as you have to use the web browser to get to the Symantec Protection Engine Console. That web console is by default at this location on SharePoint Servers.

https://localhost:8004/

The issue started in this order:
a. A user was trying to upload a file to SharePoint and got the error
b. Symantec Protection Engine service on server was stopped and failed to start with Error 1053
c. Java update caused issue for the Symantec Protection Engine to fail

a. A user was trying to upload a file to SharePoint and got the error

The user received this error in browser.

Error Found
The installed virus scanner is currently unavailable. If the problem persists, contact your administrator.

SharePoint File Upload Error due to SharePoint Antivirus Failure
SharePoint File Upload Error due to SharePoint Antivirus Failure

b. Symantec Protection Engine service on server was stopped and failed to start with Error 1053

Looking at the Symantec Protection Engine (SPE) service under Windows Service console on SharePoint showed the service as stopped. When I tried to start the service, I got following error:

Error:
Windows could not start the Symantec Protection Engine service on local Computer.
Error 1053: The service did not respond to the start or control request in a timely fashion.

SharePoint Server - Symantec Protection engine service stopped and failed to start with error 1053
SharePoint Server – Symantec Protection engine service stopped and failed to start with error 1053

Following errors were logged in Event View log.

Error 1
Log Name:      System
Source:        Service Control Manager
Date:          2/05/2015 2:17:10 PM
Event ID:      7000
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SPAppServer01.svlab.com
Description:
The Symantec Protection Engine service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Service Control Manager” Guid=”{69908d1-a6d7-4795-8e1e-26931d2012f4}” EventSourceName=”Service Control Manager” />
    <EventID Qualifiers=”49152″>7000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime=”2015-02-26T15:17:10.310766100Z” />
    <EventRecordID>187359</EventRecordID>
    <Correlation />
    <Execution ProcessID=”580″ ThreadID=”5204″ />
    <Channel>System</Channel>
    <Computer>SPAppServer01.svlab.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name=”param1″>Symantec Protection Engine</Data>
    <Data Name=”param2″>%%1053</Data>
  </EventData>
</Event>

Error 2
Log Name:      Application
Source:        Application Error
Date:          2/05/2015 2:17:10 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SPAppServer01.svlab.com
Description:
Faulting application name: symcscan.exe, version: 7.0.2.4, time stamp: 0x5167b609
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0xf38
Faulting application start time: 0x01d051d7416d9dad
Faulting application path: C:Program Files (x86)SymantecScan Enginesymcscan.exe
Faulting module path: unknown
Report Id: 88260445-bdca-11e4-91bc-0050569300d1
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Application Error” />
    <EventID Qualifiers=”0″>1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime=”2015-02-26T15:17:10.000000000Z” />
    <EventRecordID>331301</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SPAppServer01.svlab.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>symcscan.exe</Data>
    <Data>7.0.2.4</Data>
    <Data>5167b609</Data>
    <Data>unknown</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>c0000005</Data>
    <Data>00000000</Data>
    <Data>f38</Data>
    <Data>01d051d7416d9dad</Data>
    <Data>C:Program Files (x86)SymantecScan Enginesymcscan.exe</Data>
    <Data>unknown</Data>
    <Data>88140445-bdca-11e4-91bc-0050569300d1</Data>
  </EventData>
</Event>

c. Java update caused issue for the Symantec Protection Engine to fail

It turned out to be that the last Java update that updated the Java JRE from some 7.x version to 8.x version caused the issue. After seeing the service failure error and reading Symantec KB articles, I removed and tried to redeploy Symantec Protection Engine component. I got the following error during SPE’s redeployment:

Error:
The Java Runtime Environment could not be found.
Please install the java runtime, 1.5 family, preferably build 13 or higher.

SharePoint File Upload Failure - Symantec Protection Engine re-installation error for Java JRE
SharePoint File Upload Failure – Symantec Protection Engine re-installation error for Java JRE

Keep reading the next section for the resolution.

Resolution

I removed the Java JRE version, rebooted the server and then installed a version from 7.x series 7u60. After that I was able to re-install Symantec Protection Engine. The re-installation fixed the service issue as well.

Make sure you review the Symantec KB resources listed below. In my case just removing version 8.x java and putting back the 7.x would have fixed the issue without re-installation of Symantec Protection Engine.

References

Keywords:

  • SharePoint File Upload error
  • SharePoint File Upload error due to antivirus failure
  • Symantec Protection engine service fails to start with error 1053
www.Softvative.com
Visit www.softvative.com for professional services.

SharePoint Excel Services Unable to Save Workbook

Friday, November 14th, 2014

SharePoint Excel Services Unable to Save Workbook

Version: 1.0

Scenario:

A user opens an Excel file for editing using ‘Edit in Browser’ option.

SharePoint Excel Web Services - Edit In Browser an Excel File
SharePoint Excel Web Services – Edit In Browser an Excel File

Error:

After sometime in the edit mode, the user gets the message

Unable to Save Workbook

We will try again automatically, but you should try to save your workbook to another location or click Open in Excel.

There will be an error dialog box that says:
Your changes could not be saved. It is recommended that you select Open in Excel or try to save your changes to a different location immediately. If your changes can still not be saved after a few more minutes, your session will be ended to prevent any more loss of data.

SharePoint Excel Web Services - Unable to Save Workbook Error
SharePoint Excel Web Services – Unable to Save Workbook Error

Event Viewer Errors on SharePoint Application Servers running Excel Services:

1. Error on App Server 1 Event ID 7935

Log Name:      Application
Source:        Microsoft-SharePoint Products-Excel Services Application
Date:          11/6/2014 1:53:25 PM
Event ID:      7935
Task Category: Excel Calculation Services
Level:         Information
Keywords:    
User:          domainSPFarmAct
Computer:      SPAppServer1.domain.com
Description:
Unable to save the following workbook: http://sharepoint.domain.com/sites/BizSegment/Dept1/Financial

Documents/MonthlyKPIReport2015.xlsx.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-SharePoint Products-Excel Services Application” Guid=”{278E40D0-FDAA-4EB4-AB6B-9E0AD6BDBE79}” />
    <EventID>7935</EventID>
    <Version>14</Version>
    <Level>4</Level>
    <Task>2</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime=”2014-11-06T19:53:25.232766900Z” />
    <EventRecordID>720780</EventRecordID>
    <Correlation ActivityID=”{00020DF6-D14B-13A9-0000-000050F7B00B}” />
    <Execution ProcessID=”5088″ ThreadID=”7456″ />
    <Channel>Application</Channel>
    <Computer>SPAppServer1.domain.com</Computer>
    <Security UserID=”S-1-5-21-1627688274-1190192956-3999157559-1223″ />
  </System>
  <EventData>
    <Data Name=”string0″>http://sharepoint.domain.com/sites/BizSegment/Dept1/DocumentLib/MonthlyKPIReport2015.xlsx</Data>
  </EventData>
</Event>

2. Error on App Server 1 with Event ID 0 – Symantec Protection for SharePoint Servers

Log Name:      Application
Source:        Symantec Protection for SharePoint Servers Service
Date:          11/6/2014 1:57:35 PM
Event ID:      0
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SPAppServer1.domain.com
Description:
Module=ScanObject.Scan | Exception message=Failed to connect to an IPC Port: The system cannot find the file specified.
  | Stack=
Server stack trace:
   at System.Runtime.Remoting.Channels.Ipc.IpcPort.Connect(String portName, Boolean secure, TokenImpersonationLevel impersonationLevel,

Int32 timeout)
   at System.Runtime.Remoting.Channels.Ipc.ConnectionCache.GetConnection(String portName, Boolean secure, TokenImpersonationLevel

level, Int32 timeout)
   at System.Runtime.Remoting.Channels.Ipc.IpcClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream

requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
   at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Symantec.Sharepoint.Shared.InterfaceLibrary.ILoadBalancingService.GetAvailableScanEngine(ScanEngine& oScanEngine)
   at Symantec.Sharepoint.RTCommandClient.RTCommand.GetAvailableScanEngine(ScanEngine& oScanEngine)
   at Symantec.Sharepoint.ScanLibrary.ScanObject. (IntPtr inILockBytes, Int32& pdwStatus, String& wzVirusInfo)
Event Xml:
<Event xmlns=’http://schemas.microsoft.com/win/2004/08/events/event’><System><Provider Name=’Symantec Protection for SharePoint Servers

Service’/><EventID Qualifiers=’0′>0</EventID><Level>2</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated

SystemTime=’2014-11-

06T19:57:35.000000000Z’/><EventRecordID>720783</EventRecordID><Channel>Application</Channel><Computer>SPAppServer1.domain.com</Computer

><Security/></System><EventData><Data>Module=ScanObject.Scan | Exception message=Failed to connect to an IPC Port: The system cannot

find the file specified.
  | Stack=
Server stack trace:
   at System.Runtime.Remoting.Channels.Ipc.IpcPort.Connect(String portName, Boolean secure, TokenImpersonationLevel impersonationLevel,

Int32 timeout)
   at System.Runtime.Remoting.Channels.Ipc.ConnectionCache.GetConnection(String portName, Boolean secure, TokenImpersonationLevel

level, Int32 timeout)
   at System.Runtime.Remoting.Channels.Ipc.IpcClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream

requestStream, ITransportHeaders&amp; responseHeaders, Stream&amp; responseStream)
   at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&amp; msgData, Int32 type)
   at Symantec.Sharepoint.Shared.InterfaceLibrary.ILoadBalancingService.GetAvailableScanEngine(ScanEngine&amp; oScanEngine)
   at Symantec.Sharepoint.RTCommandClient.RTCommand.GetAvailableScanEngine(ScanEngine&amp; oScanEngine)
   at Symantec.Sharepoint.ScanLibrary.ScanObject. (IntPtr inILockBytes, Int32&amp; pdwStatus, String&amp; wzVirusInfo)

</Data></EventData></Event>

3. Error on App Server 2 – Event ID 8031

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          11/6/2014 2:15:01 PM
Event ID:      8031
Task Category: Topology
Level:         Error
Keywords:    
User:          domainSPFarmAct
Computer:      SPAppServer2.domain.com
Description:
An exception occurred while updating addresses for connected app {6457c0c9-76ff-4fb6-a94e-4ca7928efa06_65529aa3-7640-40b8-b262-

e557c37f87e9}. The uri endpoint information may be stale. System.InvalidOperationException: The requested application could not be found.
   at Microsoft.SharePoint.SPTopologyWebServiceApplicationProxy.ProcessCommonExceptions(Uri endpointAddress, String operationName,

Exception ex, SPServiceLoadBalancerContext context)
   at Microsoft.SharePoint.SPTopologyWebServiceApplicationProxy.ExecuteOnChannel(String operationName, CodeBlock codeBlock)
   at Microsoft.SharePoint.SPTopologyWebServiceApplicationProxy.GetEndPoints(Guid serviceId)
   at Microsoft.SharePoint.SPConnectedServiceApplicationAddressesRefreshJob.Execute(Guid targetInstanceId)
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-SharePoint Products-SharePoint Foundation” Guid=”{6FB7E0CD-52E7-47DD-997A-241563931FC2}” />
    <EventID>8031</EventID>
    <Version>14</Version>
    <Level>2</Level>
    <Task>13</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime=”2014-11-06T20:15:01.064016600Z” />
    <EventRecordID>864875</EventRecordID>
    <Correlation ActivityID=”{7C78DFF9-926C-43B6-AEEF-60EDDB502CA2}” />
    <Execution ProcessID=”13816″ ThreadID=”18532″ />
    <Channel>Application</Channel>
    <Computer>SPAppServer2.domain.com</Computer>
    <Security UserID=”S-1-5-21-1627688274-1190192956-3999157559-1223″ />
  </System>
  <EventData>
    <Data Name=”string0″>6457c0c9-76ff-4fb6-a94e-4ca7928efa06_65529aa3-7640-40b8-b262-e557c37f87e9</Data>
    <Data Name=”string1″>System.InvalidOperationException: The requested application could not be found.
   at Microsoft.SharePoint.SPTopologyWebServiceApplicationProxy.ProcessCommonExceptions(Uri endpointAddress, String operationName,

Exception ex, SPServiceLoadBalancerContext context)
   at Microsoft.SharePoint.SPTopologyWebServiceApplicationProxy.ExecuteOnChannel(String operationName, CodeBlock codeBlock)
   at Microsoft.SharePoint.SPTopologyWebServiceApplicationProxy.GetEndPoints(Guid serviceId)
   at Microsoft.SharePoint.SPConnectedServiceApplicationAddressesRefreshJob.Execute(Guid targetInstanceId)</Data>
  </EventData>
</Event>

Remedy:

During the issue the users impacted can use the Save As option in Excel Web Viewer to save the file locally if they want to edit the file and upload it later after issue is fixed.
Excel Web Services - Save As option
Excel Web Services – Save As option
The user will loose the changes they will do during this issue if they will not save a copy and then edit the saved copy.
If you continue making changes in Excel file within Excel Web Viewer, you will get a prompt with following message. At this point you have lost the changes you would have made during this session.
Either due to communication issues or a server problem, you need to be rejoined to your editing session. You may have lost changes that you made recently.
Excel Web Viewer - Session Lost and Lost recent changes Message
Excel Web Viewer – Session Lost and Lost recent changes Message
At this point go to your document library location where your Excel file is located and review the Modified date. You will notice that the modified date will not reflect that it was modified. Same will be true for version number if versioning was enabled for that library.
Excel Web Services issue - File changes not Saved
Excel Web Services issue – File changes not Saved
At this point the user will feel angry, frustrated or a lost soul based no their work. Don’t loose hope. There is some green light. Its coming in next section.

Resolution:

The above issue with Excel Web View not able to save could happen due to number of reasons. In this case when I started reviewing the SharePoint Farm for the application servers running Excel Services, I found that whenever there was error in Excel web viewer for this issue, around the same time there was an error log for Symantec Protection for SharePoint Servers. Now you know why I listed the Symantec error in the Errors section. 
I went to SharePoint Central Admin website and looked at the Symantec settings. I noticed the service was showing as stopped on one application server.
SharePoint Central Admin - Symantec Protection Service Stopped on one App Server
SharePoint Central Admin – Symantec Protection Service Stopped on one App Server
Next I looked into the Windows Services console and found the service ‘Symantec Protection 6.0 for SharePoint Servers’ in STOPPING status. In that state you can not start, stop or restart that service.
Windows Services Console - Symantec Protection Service in STOPPING State
Windows Services Console – Symantec Protection Service in STOPPING State
I terminated the Symantec Protection SPSS process using Windows Task Manager on the server. Then I started that service successfully. Later I went to SharePoint Central Admin website > Symantec Protection section and looked at that server and it was showing as Started.
SharePoint Central Admin - Symantec Protection Service in Started state on an App Server
SharePoint Central Admin – Symantec Protection Service in Started state on an App Server
Next I opened the Excel file from SharePoint location in Excel Web services in edit mode. I was able to edit the file and Excel Web Services saved the changes back to the file. I then reviewed the Modified date and it was showing the file was modified at recent time with my name under Modified Bu field. 
Excel Web Services - File changes Saved
Excel Web Services – File changes Saved
Finally the Excel Services came back on track.
Keywords:
  • Excel can not save changes
  • Excel services can not save changes
  • Excel web services can not save changes
  • Excel services lost changes
  • SharePoint Excel services lost changes
  • SharePoint Excel services not saving changes
  • SharePoint Excel services not able to edit files
  • SharePoint Excel services not able to update file
  • SharePoint Excel services oddies
  • SharePoint Excel services issues
  • Can not modify Excel in SharePoint
  • Can not modify Excel in Excel Web Services

Recover Symantec Protection Engine Lost Password

Wednesday, October 15th, 2014

Recover Symantec Protection Engine Lost Password

Version: 1.2

Symantec Protection for SharePoint Servers (SPSS) is an antivirus solution for SharePoint. SPSS uses Symantec Protection Engine (SPE) as the underlining solution to provide the security framework to SPSS.

On each SharePoint Server running SPSS, usually you also have Symantec Protection Engine (SPE) there as well running under https://localhost:8004. SPE portal is usually password protected.

I came across a scenario where the password for the Symantec Protection Engine (SPE) portal was lost. We were using the right password but somehow SPE was not accepting it. On top of that the Symantec license was about to expire in few days. It was a race against the time!

Error Message

Login failed or Symantec Protection Engine server is not running.

SPE and SPSS services in Windows services console were running.

Symantec Protection Engine Portal Password Failure
Symantec Protection Engine Portal Password Failure

Method 1

I looked at the Symantec Protection for SharePoint Servers implementation guide and under chapter-7 found the section titled ‘Unable to remember the console password’. That is the one method to recover lost password for Symantec Protection Engine (SPE). It didn’t work in my case.

If you forget the console password, you can reset the password. The command line tool CmdSymScan lets you remove the password. It is located at the location
<installdir>:Program FilesSymantecSharePoint.

Type the following command in the command prompt:
cmdsymscan clearconsolepassword

You are not prompted for a password again.

Time was ticking….

Method 2

I went to the Symantec Scan Engine folder location and opened the configuration.xml file.
C:Program Files (x86)SymantecScan Engine

I then searched for the password parameter. Guess what, I found the encrypted password there. I cleared the value and saved the file. The password parameter should look like this.

<password value=””/>

After that I restarted the Symantec Protection Engine (SPE) services under Windows Services console.

Symantec Protection for SharePoint - Windows Services
Symantec Protection for SharePoint – Windows Services 

I closed and relaunched the Symantec Protection Engine (SPE) portal and I was able to successfully log in without the password. From there, I saved the new password, updated the license file and SPSS time clock stopped ticking.

Symantec Antivirus for SharePoint Blocked Linked Excel Files

Wednesday, October 8th, 2014

Symantec Protection for SharePoint Blocked Linked Excel Files

Issue Summary

Symantec Protection for SharePoint Servers (SPSS) 6.0 was deployed in the SharePoint farm. After deployment, certain files are getting blocked by it even though Symantec Antivirus on desktop had cleared those as clean files.

In one of my previous post Linked Excel Files and SharePoint, I covered the details on how linked files work in SharePoint.

Error:

2 – The file: FileNameByFM.xlsx -contains Unscannable Content. Reason: Container Size Violation | Container Size Violation -Status: Blocked

This file cannot be saved to the document library. If you want to save this file to the document library, clean the file using alternative virus scanning software and try saving it again.

Troubleshoot issues with Microsoft SharePoint Foundation.

File can not be uploaded to SharePoint dueto Symantec Antivirus for SharePoint SPSS
File can not be uploaded to SharePoint dueto Symantec Antivirus for SharePoint SPSS

If you are trying to upload a new file, the file is not uploaded. If you are trying to save after edit / checking out, file, it doesn’t work either.

Cause:

The issue is due to the linked MS Excel files that were on user desktop. Only container file was uploaded to the SharePoint. The file was 25 MB in size.

How to find linked files in MS Excel

Follow the steps listed below to find the linked files:
1. Open the Microsoft Excel file from SharePoint
2. Go to Data ribbon tab and then click Edit Links under Connections group
3. Review the linked file(s) for Location. Update / remove as it applies to your container file
4. Save and close the file

Microsoft Excel - Edit Linked Files
Microsoft Excel – Edit Linked Files

You might have to do these step by downloading a copy of that file on your desktop and then make above changes.

Microsoft Excel - Edit Linked Files - Review Location
Microsoft Excel – Edit Linked Files – Review Location

Resolution:

Even removing the linked file didn’t help in this case. The linked file was unnecessary in this scenario. Symantec Protection for SharePoint was still treating that file as a container file. Make sure you review the data in container Excel file that might be coming from the linked file.

I found that Symantec Protection Engine portal on the SharePoint server (http://localhost:8004) has a default filter policy for container handling. Symantec Protection Engine is a separate component of Symantec Protection for SharePoint Servers.

Container File Processing Limits:
Following filter policies were defined by default.

Stop processing a container file when any of the following limits is met or exceeded.
a. Time to extract file meets or exceeds: 180 seconds
b. Maximum extract size of the file meets or exceeds: 100 MB
c. Maximum extract depth of the file meets or exceeds: 10 levels

When processor limit is met or exceeded: Deny access to the file and generate a log entry.

Symantec Protection for SharePoint Servers - Filtering Policies on Container Handling
Symantec Protection for SharePoint Servers – Filtering Policies on Container Handling

I changed the container file  policy to: Allow access to the file and generate a log entry.

That seemed to resolve the issue.

Risk Assessment:

In this scenario, due to internal only SharePoint, the decision was made to allow access to files in case of container file processing limits are reached or exceeded. The decision was in favor of application availability rather strict security.

Keywords:

  • Symantec Antivirus for SharePoint
  • Symantec Protection for SharePoint
  • Symantec Protection for SharePoint blocks file
  • Symantec Protection for SharePoint does not allow file upload
  • Symantec Protection blocks file upload in SharePoint
  • File upload blocked by Symantec antivirus
  • File upload blocked in SharePoint
  • Unscannable Contents in SharePoint
  • Container Size violation in SharePoint
  • SharePoint File upload blocked by antivirus

Symantec Antivirus for SharePoint Doesn’t Allow File Upload

Friday, May 16th, 2014

Scenario:

A user tries to upload a file to a SharePoint document library and get the following error message:
The installed virus scanner is currently unavailable. If the problem persists, contact your administrator.
Symantec Antivirus for SharePoint causing Upload Error – The installed virus scanner is currently unavailable

Cause:

Symantec Antivirus for SharePoint has two components. Console and Protection Engine. Symantec Protection Engine if disabled or not running, can prevent users from uploading files to SharePoint. That behavior is triggered by the default configuration settings of the Symantec Antivirus for SharePoint. Notably under ‘Real-Time scan Settings‘ area within SharePoint Central Administration site.
Symantec Antivirus for SharePoint – Real-Time Scan Settings – Default

Resolution:

Make sure to allow the Bypass configurations in cases where Protection Engine is disabled / offline.
Steps:
1. Go to Central Administration home
2. Click on ‘Real-time Scan Settings’ under ‘Symantec Protection 6.0 for SharePoint Servers’ section.
Symantec Antivirus for SharePoint – On Central Admin Site Home
3. Enable these settings by configuring the check boxes:
   a. Bypass scanning when all Symantec Protection Engines are busy or offline 
   b. Bypass scanning when all Symantec Protection Engines are disabled
   c. Scan all content that was bypassed when all Symantec Protection Engines were offline or busy
The first two (a and b) settings will allow the users to upload files even when Symantec Protection Engines are busy, Offline or disabled. The third c setting will scan the files that were bypassed when Protection engine was offline or busy.
Symantec Antivirus for SharePoint – Real-Time Scan Settings – Revised
4. Click Save button at the bottom
After saving these configuration changes, the users should be able to upload files.
Symantec Antivirus for SharePoint – Allowed the File Upload after Revised Settings

Security Risk:

There is security risk there though. Doing so will allow users without Antivirus to upload infected files to SharePoint. That will be a major risk for internet facing deployments. In my case it was a non-production SharePoint. Always weigh-in the pros and cons of productivity loss versus the security issue in some of these situations.
Few Related Search Terms:
Symantec Antivirus for SharePoint Doesn’t Allow File Upload
Upload failed when antivirus scanner is unavailable
Symantec Protection Engine failure stops the file upload in SharePoint