Skip to main content

Exception from HRESULT: 0x80041050

We were receiving this error on the home page of root site collection of our SharePoint test farm and also on some inner site collections.

Server Error in '/' Application.
--------------------------------------------------------------------------------

Exception from HRESULT: 0x80041050
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x80041050

I had no clues as to why this happens because googling returned many results and confused me more. It turned out that the issue was related to Forefront for SharePoint. I had installed ForeFront for SharePoint evaluation and that had scanned and marked some pages as virus. I couldn't get Forefront to work properly and uninstalled it. May be this caused some jobs to get stuck or something; I'm not sure why ForeFront marks SharePoint masterpages as virus.

If ForeFront is still installed, we'll have to remove these pages from scanned results. Navigate to Forefront Admin console:

1.Please disable scanning on a correctly flagged pages as a virus in Forefront.
2.Open Forefront Admin console.
3.Go to filtering.
4.Click on File.
5.Add a new item as *.aspx select “Detect only”
6.Make the filter enable and click save.
7.Remove your pages from the pages library located at”View all Site Content”->Pages.
8.Add your Custom.aspx pages back into the pages library

I had already uninstalled Forefront, so I had to do this the hard way :) editing from backend:

1. Ran the sql command “select * from AllDocs where (VirusStatus>0) and (VirusStatus IS NOT NULL)”
2. It returned results. I backuped the database and performed “Update AllDocs set VirusStatus= null where (VirusStatus>0) and (VirusStatus IS NOT NULL)” on this database
3. I repeated these steps on all content databases

Note: If you update SharePoint tables using SQL query, the support might become void. I did this since this was our testing environment.
Labels:

Comments

Post a Comment

Popular posts from this blog

"Cannot impersonate user for data source" - SSRS reports

We were getting this strange error while viewing our reports in SharePoint that was deployed using BIDS 2005: An error has occurred during report processing. Cannot impersonate user for data source 'datasource' Logon failed I tried many things but nothing worked. I did some research and found many blog posts which suggested me to reapply the password on the datasource file specified in the error message and save it again. That didn't work for me. I saw some check boxes in the data source file that read "Use as Windows Credentials" and "Set Execution Context to this report" and I didn't know what they meant. I unchecked those in my data source and then when the refreshed the page the report started displaying.
2 comments
Read more

Users do not show up in SharePoint People Search or People Picker

I had this issue with people picker in a classic mode web application in SharePoint 2013 and this site is in 2010 mode - users in certain sub-domains would not show up in People Picker. I was aware of stsadm commands to fix this and we ran the stsadm command to hook up people picker with another domain some time back. The latest issue was that people picker was not returning users from the root domain and few sub domains. After researching on the internet I found (contrary to my thoughts) that we could use PowerShell and not just stsadm to map People Picker to domains. It is a good idea to first check what domains are added/mapped to the web application using the following commands: $wa = Get-SPWebApplication -Identity http://mywebapp.com #List the Domains $wa.PeoplePickerSettings.SearchActiveDirectoryDomains This will list the domains currently People Picker is looking up for that web application. I used the following script to map our AD forest to People Picker:
Post a Comment
Read more

Report Server has encountered a SharePoint error. ( rsSharePointError)

I was receiving this error on the "Report Server Web Service URL" on our SharePoint farm: Report Server has encountered a SharePoint error. ( rsSharePointError) Access to this Web Site has been blocked. Please contact the administrator to resolve this problem. This site URL is configured via Central Administration > Configure Reporting Services Integration > Reporting Services Integration if Reporting Server feature/Add-in is installed on the farm. After doing some research I found out that this page somehow enumerates through entire site collections before it throws this error. As part of troubleshooting step I checked if the domain user configured for reporting service is has sufficient privileges in the farm and also as local admin of the sql box, but this did not solve the issue. We raised this issue with the vendor and they made us update our SQL Server 2005 to latest SP and CU; still we had the error. The reason was nobody was sure if this er
3 comments
Read more