Freigeben über


MOSS and Microsoft Forefront Security for SharePoint

After you uninstall Microsoft Forefront Security for SharePoint, you may experience the following symptoms:

  • The following events are logged in the Application log:

Event Id: 2268
Event Type: Error
Event Source: w3svcwp
Description: Could not load all ISAPI filters for site/service. Therefore startup aborted

Event Id: 2214
Event Type: Error
Event Source: w3svcwp
Description: The HTTP Filter DLL C:\Program Files\Microsoft Forefront Security\SharePoint\FSSPUsernameFilter.dll failed to load. The data is the error.

  • The SharePoint Central Administration page is unavailable.

And we have a KB article for the same - KB # 943621

 

But what if Forefront is not uninstalled and when we browse the SharePoint site we receive HTTP 500 and the following events are logged in the Application log:

Event Id: 2268
Event Type: Error
Event Source: w3svcwp
Description: Could not load all ISAPI filters for site/service. Therefore startup aborted

Event Id: 2214
Event Type: Error
Event Source: w3svcwp
Description: The HTTP Filter DLL C:\Program Files\Microsoft Forefront Security\SharePoint\FSSPUsernameFilter.dll failed to load. The data is the error.

To resolve the above error:

Add the user under which the Application Pool identity for the problematic SharePoint Site runs to the following folders as Full Control:

C:\Program Files (x86)\Microsoft Forefront Security\SharePoint

C:\Program Files (x86)\Microsoft Forefront Security\SharePoint\FSSPUsernameFilter.dll

Also there may be some instances when we browse any SharePoint Site we receive an error:

"Accessor is invalid"

 

or

 

 

 

Exception from HRESULT: 0x80041050

In such cases follow the below steps:

 

Run the below query on problematic SharePoint site Content DB:

 

SELECT * FROM AllDocs WHERE (VirusStatus > 0) AND (VirusStatus IS NOT NULL)

 

If it returns results, which means the VirusStatus column has been changed to a non-zero and non-null value.

Rerun the Antivirus scan and re-query the above SQL.

 

If issue still exists then you may need to get in touch with your security team for more information.

 

Note: Do not modify the SharePoint Table manually as it may lead to an unsupported environment.

 

References:

https://support.microsoft.com/kb/943621/en-us

https://support.microsoft.com/?id=928169

https://support.microsoft.com/kb/841057/en-us