search cancel

During periods of heavy load documents become unavailable with Protection Engine for SharePoint Services scanning enabled.

book

Article ID: 164206

calendar_today

Updated On:

Products

Protection for SharePoint Servers

Issue/Introduction

When attempting to take actions that trigger Symantec Protection for SharePoint Services (SPSS) scans within Sharepoint 2010, and system load is heavy, items cannot be be accessed as long as SPSS scanning is enabled.

In the application event log of the Sharepoint server, multiple Event ID 0s from Source "Symantec Protection for SharePoint Services" with the following details are logged:

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)

 

During the periods of heaviest load multiple Event ID 0s from Source "Symantec Protection for SharePoint Services" with the following details may also be logged: 

Module=ScanObject.Scan | Exception message=Port is Busy: All pipe instances are busy.
| 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)

 

 

Cause

A defect in the underlying version of .NET framework causes Inter-Process communication (IPC) channel exhaustion during the heaviest load periods in the Sharepoint farm.

See A System.Runtime.Remoting.RemotingException exception is thrown when you deploy a SharePoint solution on a SharePoint Web server that is running the .NET Framework 2.0 SP2 for details.

Resolution

Apply the hotfix mentioned in A System.Runtime.Remoting.RemotingException exception is thrown when you deploy a SharePoint solution on a SharePoint Web server that is running the .NET Framework 2.0 SP2.

Microsoft support has confirmed that this hotfix is not included in version 2.0.727.5488 of the System.Runtime.Remoting.dll included in the standard General Distribution Release (GDR) of the .NET framework 2.0 rollups. In order to resolve this issue, the Limited Distribution Release (LDR) rollup must be installed. For assistance installing the LDR rollups, please contact Microsoft support.