Skip to main content

Posts

Showing posts from August, 2010

Legacy troubleshooting: SQL Server Reporting Services (SSRS) and SharePoint

While working with reports deployed to an older SharePoint environment using Business Intelligence Development Studio (BIDS) 2005, we encountered an authentication error when opening reports. The error included: An error has occurred during report processing.  Cannot impersonate user for data source 'datasource'. Logon failed This article documents the troubleshooting experience and resolution in that environment. Applicability: This guidance relates to legacy SSRS and SharePoint installations. It should not be treated as current guidance for Power BI, SharePoint Online or modern SQL Server Reporting Services deployments. I tried many things but nothing worked. I did some research and found many blog posts which suggested 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...

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...