Error "Exception from HRESULT: 0x80041054" is shown when accessing certain SharePoint site pages
search cancel

Error "Exception from HRESULT: 0x80041054" is shown when accessing certain SharePoint site pages

book

Article ID: 177620

calendar_today

Updated On:

Products

Protection for SharePoint Servers

Issue/Introduction

The Symantec Protection for Sharepoint Servers (SPSS) service has terminated and when accessing certain pages on your Sharepoint Site you'll receive the following error: "Exception from HRESULT: 0x80041054"

 

"Exception from HRESULT: 0x80041054" shown on the Web Browser when Sharepoint pages are accessed.
Please note: the above error is not displayed when you access the Sharepoint Central Administration.

The Protection for Sharepoint Servers connector "process" logs file will show the following warning:

2010-10-14 04:12:27,"Warning","Process","realtime://sharepoint_server//file_name.ext",".ext","Scan","RealTime","ALLSessionInuse","Block",3193,0,"All virus scanners are at maximum load. Virus scanning is not possible.",0,"",""

 

Furthermore, the Sharepoint Server Windows Event Log may show the following errors:

Event Type: Error
Event Source: Symantec Antivirus
Event Category: None
Event ID: 9999
Description:
An exception was present in the module: Symantec Antivirus
ErrorID = 9999
ErrorText = Object '/SymantecSharePointChannelObject.rem' has been disconnected or does not exist at the server.
ErrorStack = 
Server stack trace: 
   at System.Runtime.Remoting.Channels.ChannelServices.CheckDisconnectedOrCreateWellKnownObject(IMessage msg)
   at System.Runtime.Remoting.Channels.ChannelServices.DispatchMessage(IServerChannelSinkStack sinkStack, IMessage msg, IMessage& replyMsg)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.IConnection.IConnection.Init(String Key, ConnectionTypes ConnectionType)
   at a6.i()
ErrorSource = mscorlib
ErrorModule = Symantec Antivirus

and:

Event Type: Error
Event Source: Symantec Antivirus
Event Category: None
Event ID: 9999
Description:
An exception was present in the module: Symantec Antivirus
ErrorID = 9999
ErrorText = Failed to connect to an IPC Port: The system cannot find the file specified.
 
ErrorStack = 
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.IConnection.IConnection.Init(String Key, ConnectionTypes ConnectionType)
   at a6.i()
ErrorSource = mscorlib
ErrorModule = Symantec Antivirus 

 

 

 

 

Cause

This has been identified by Microsoft as being an issue with the Symantec Protection for SharePoint Servers setting the VirusStatus code in the database to a non-zero and non-null value.

Please refer to the document TECH145690 in the related articles section for more information on the above database fields.

Resolution

This problem can be resolved by upgrading Symantec Protection for Sharepoint Servers (SPSS) to either 5.1.7 for version 5.1.x or 6.0.5 for version 6.0.x, and by enabling exclusions based on file types through registry.

SPSS version 6.0.1 contains a fix to work with the exclusion settings however, version 6.0.5 contains another fix which automatically resets the VirusStatus flag to NULL.

Steps to set exclusions:

Once SPSS is upgraded on the system, based on the version you upgraded to please follow these steps to resolve this problem by excluding scan on specific file extensions.

For SPSS version 5.1.7 -

  1. Open the Registry Editor and browse to the path “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\AVScanner”.
  2. Check if the key "ByPassExtensionOnOffline" is already present at the path. If not perform the below steps.
  3. Create a new “String Value” with the following name: “ByPassExtensionOnOffline”.
  4. Set the value of the new key “ByPassExtensionOnOffline” to “.aspx;.asmx”.
  5. Restart IIS WebServices with command: “iisreset”.

For SPSS version 6.0.1 or higher -

  1. Open the Registry Editor and browse to the path “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\AVScanner”. 
  2. Check if the key “SkipExtensionsNoScanner” is already present at the path. If not perform the below steps. 
  3. Create a new “String Value” with the following name: “SkipExtensionsNoScanner”. 
  4. Set the value of the new key “SkipExtensionsNoScanner” to “.aspx;.asmx”.
  5. Restart IIS WebServices with command: “iisreset”.  

Note:  For Sharepoint to process and read the AVScanner registry key,  IIS will need to have the appropriate permission to the Key.  Network Service is the default account that IIS uses and it will need to have Full Contol to the AVScanner registry key. 

 

IIS and Built-in Accounts (IIS 6.0)
https://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/3648346f-e4f5-474b-86c7-5a86e85fa1ff.mspx?mfr=true

Clearing the VirusStatus flag

As described from above, SPSS 6.0.5 introduced a fix to automatically clear the VirusStatus flag. A few steps need to be followed in order to enable fix after upgrade to SPSS 6.0.5. For more details please refer to document TECH216472 - Cannot access SharePoint pages while Symantec Protection Engine server is shown offline on Symantec Protection for SharePoint console.

For version 5.1.x, please follow the workaround below. 

In order to work around this problem you should perform a full manual scan across your entire Sharepoint site (without any file exclusions) and ensure the realtime protection is enabled both on upload and download.

Please follow the steps below:

  1. Ensure the Symantec Protection for Sharepoint Servers services are all started
  2. Open the Sharepoint Central Administration console and browse to: "Operations > Antivirus"
  3. Ensure antivirus scanning is enabled for upload and download of documents
  4. Stiill in the Sharepoint Central Administration console, browse to: "Operations > Symantec Protection 5.1 for Sharepoint Servers"
  5. Ensure all Scan Engine scanners are connected and appear as "online"
  6. Enter the "Manual scan and scheduled scan" page
  7. Run a full scan across all your Sharepoint server and wait until it finishes
  8. Open again any other page on your Sharepoint site (not the CA) and the error now should have disappeared.

  NOTE: Microsoft states this is an issue only on Microsoft Office SharePoint Portal Server 2003, but has been seen on Windows SharePoint Services 3.0   

 

Additional steps

Another detail you should check is the number of antivirus threads set for your Sharepoint Server (Global Settings).
Should the value be much higher than "5" (default), we recommend you to lower it to "5" and monitor the server.


Applies To

This issue has been reported on specific SharePoint 2007 or 2010 Sites such as "Collaboration Portals".

Powered by Wolken Software