Sign in
 
HomeProductsLibraryLearnDownloadsSupportForums
Microsoft Forefront TechCenter >
> 
> 
Forefront Security engine flagged some Sharepoint DB’s to VirusStatus=1 and was causing an Exception from HRESULT: 0x80041050 error.detects a virus in a SharePoint site when there really isn’t one.

Answered Forefront Security engine flagged some Sharepoint DB’s to VirusStatus=1 and was causing an Exception from HRESULT: 0x80041050 error.detects a virus in a SharePoint site when there really isn’t one.

  • Sunday, June 24, 2012 8:15 AM
     
     
    Sign In to Vote
    0

    Greetings!

    Hi All,

    There was an issue with one of the site which became unavailable due to a bug in Forefront that it detects a virus in a SharePoint site when there really isn’t one.  It flags the site as infected when it really isn’t and prevents further access to the site. Its tagging one of the application pages(default.master ) as having an issue (i.e containing virus or corrupted).

    My Query: Whats the cause for this problem. Is it SharePoint Level antivirus or Operating system level antiviurs?

    Is there any permanent solution or any hotfix. I am looking for your open suggestions. Please find below the server details.

    SERVER DETAILS

    • windows 2003 server
    • moss 2007 sp2 application
    • antivirus  sharpoint level : Forefront protection 2010 for SharePoint
    • Antivurs OS level - FEP - Forefront End proteciotn

    Error Message: MS Forefront Security engine flagged some Sharepoint DB’s to VirusStatus=1 and was causing an Exception from HRESULT: 0x80041050 error.

    There’s a fix explained in the following link: http://geekswithblogs.net/MOSSParadox/archive/2007/07/05/Forefront-Security-and-MOSS--Exception-from-HRESULT-0x80041050.aspx

    Thanks in Advance

    rohu

     

All Replies

  • Monday, June 25, 2012 7:22 AM
    Moderator
     
     Answered
    Sign In to Vote
    0

    Hi,

    Thank you for the post.

    Please navigate to http://<site>/_layouts/changesitemasterpage.aspx and select a new master page. Then select the checkbox to apply to all subsites. Do the same for the system master page and see if it works.

    Regards,

    Nick Gu - MSFT

     
  • Tuesday, June 26, 2012 10:08 AM
     
     Answered
    Sign In to Vote
    0

    Hi Rohu,

    The blog you linked to basically edits the sharepoint database, which is totally unsupported and, if you run this, you will leave yourself with an unsupported sharepoint database, which will require a full export and import or restore from backup to return you to a supported environment.

    Normally this issue occurs because FPSP has experienced an issue when scanning and this has left the document marked as infected within the Sharepoint database. The only supported method to address this is either, the procedure that Nick states above, or to perform a manual or scheduled scan of the Sharepoint database using FPSP.

    One of the most common causes of this issue is due to the file system AV execptions not being configured correctly. The following link has details of pre-configured templates to create exceptions for FEP for several typical MS Server configurations:-

    http://technet.microsoft.com/en-us/library/gg412475.aspx

    I hope this helps,

    Alex

    Alex

     
  • Thursday, August 02, 2012 8:57 AM
     
     
    Sign In to Vote
    0

    Thanks Alot Nick & Alex for your inputs. I am in the process of implenting the suggested changes. I will keep you updated.

    Rohu