Forefront Security and MOSS ( Exception from HRESULT: 0x80041050)

This one took some time to weed out, but found that the Forefront Scan Engine had incorrectly flagged my welcome page in my Site Directory to VirusStatus=1 and was causing an Exception from HRESULT: 0x80041050 error.

Solution:

  1. Open your SQL Server Management Studio and go to the Content Database where your default welcome page is returing the error (Usually WSS_Content_[someguid]).
  2. Create a new query and run:
    select *
    from AllDocs
    where (VirusStatus > 0) and (VirusStatus is not null)
  3. If you get any results this is your issue!  (Given that you don't actually have some virus in that file.)
  4. Run the next query:
    update AllDocs 
    set VirusStatus = null
    where (VirusStatus > 0) and (VirusStatus is not null)


kick it on SharePointKicks.com

posted @ Thursday, July 05, 2007 5:39 PM

Print

Comments on this entry:

# re: Forefront Security and MOSS ( Exception from HRESULT: 0x80041050)

Left by John Chan at 7/12/2007 8:50 AM
Gravatar
Hi, I recieved this problem as well and working on fixing it at the moment. I found 9 files that had the VirusStatus set to 1, which I reseted and am now able to access the files. However, there is one account so far that I noticed that still gets the error message when logging into the main page (default.aspx). I've test 5 accounts and 4 can login at the moment, while 1 can't. I'm not sure what is wrong. It keeps giving "Exception from HRESULT: 0x80041050" whenever I try to login to the default.aspx page even though it is cleared of viruses. Please advise. Thank you.

# re: Forefront Security and MOSS ( Exception from HRESULT: 0x80041050)

Left by Will Pritchard at 7/12/2007 9:49 AM
Gravatar
Sounds like you might have something in cache. Try logging in with the user from another machine or dumping your IE cache before accessing the page. This should not be a user specific error.

# re: Forefront Security and MOSS ( Exception from HRESULT: 0x80041050)

Left by John Chan at 7/12/2007 10:12 AM
Gravatar
That's what I thought at first as well. I deleting all the cache and browsing history from the current computer and had the same error. Then I went to 2 different computers and got the same error with that specific user account.

# re: Forefront Security and MOSS ( Exception from HRESULT: 0x80041050)

Left by John Chan at 7/12/2007 10:31 AM
Gravatar
Ok, I just went with the last resort cause I was out of ideas. I rebooted the MOSS server and the SQL Server. Got massive phone calls as expected from users, but it fixed the problem I was having with that user account. I really hate not knowing exactly what the problem was. I'm glad it works after a reboot, but would still like to know why. Very wierd and definitely not reassuring.

I'm using Microsoft ForeFront for SharePoint Server 2007 and after this glitch/error/mistake I'm hesistant to keep using it. But problem is that it seems ForeFront is the only available antivirus for MOSS2007 at the moment. Do you have any suggestions or do you think ForeFront is good?

Thank you.

# re: Forefront Security and MOSS ( Exception from HRESULT: 0x80041050)

Left by Will Pritchard at 7/12/2007 11:28 AM
Gravatar
I have my misgivings about using Forefront as well as it seems to be the source of many strange and random issues, however there is not any other supported product for virus scanning with MOSS 2007 as you mentioned. For now it seems this is what we are stuck with. I would hope that future versions of Forefront improve.

# re: Forefront Security and MOSS ( Exception from HRESULT: 0x80041050)

Left by Robin at 8/21/2007 5:29 AM
Gravatar
Thanks mate for sorting this out.. this helped me!
Executed the query, rebooted the servers (because a different error suddenly appeared) and everything was working again.

Blogged you at : http://glorix.blogspot.com/2007/08/exception-from-hresult-0x80041050.html

# re: Forefront Security and MOSS ( Exception from HRESULT: 0x80041050)

Left by A.T. at 11/19/2007 10:01 AM
Gravatar
Thanks man... It worked for me like magic.

# re: Forefront Security and MOSS ( Exception from HRESULT: 0x80041050)

Left by Will Pritchard at 11/19/2007 1:14 PM
Gravatar
Cheers! Glad it worked out for you.

# re: Forefront Security and MOSS ( Exception from HRESULT: 0x80041050)

Left by Fernando Gomez at 11/20/2007 11:13 AM
Gravatar
Why dont microsoft has fixed this yet?

# re: Forefront Security and MOSS ( Exception from HRESULT: 0x80041050)

Left by Dave Coleman at 7/11/2008 12:37 AM
Gravatar
Many Many thanks worked a treat and you saved my life

# re: Forefront Security and MOSS ( Exception from HRESULT: 0x80041050)

Left by CL at 8/8/2008 2:34 PM
Gravatar
It's a timeout issue forefront has encountered - with the website itself. It can sometimes happen during a JIT compile of your website. You can help avoid this error by - unchecking the option that the 'SharePoint Realtime scan job' scans documents on download

We are relying on the desktops to scan on download and Forefront to scan on upload.

I found this post helpful.

http://glorix.blogspot.com/2007/08/exception-from-hresult-0x80041050.html

# re: Forefront Security and MOSS ( Exception from HRESULT: 0x80041050)

Left by Deepa at 12/15/2009 11:08 PM
Gravatar
Thanks frnd..it helped to rectify my issue :)

Your comment:



 (will not be displayed)


 
 
 
 
 

Live Comment Preview:

 
«February»
SunMonTueWedThuFriSat
31123456
78910111213
14151617181920
21222324252627
28123456
78910111213