An error has occurred during report processing.
 Query execution failed for data set ‘dataset_0′.
  For more information about this error navigate to the report server on the local server machine, or enable remote errors

In order to see a better description of the error you can either RDP onto the server and run the report or…  

To enable remote errors in Reporting Services 2005 or 2008 run this statement in SQL Server Management Studio: 

Use ReportServer;
update ConfigurationInfo set Value = ‘True’ where Name = ‘EnableRemoteErrors’;

You then need to reset IIS

There are more options here: http://technet.microsoft.com/en-us/library/aa337165(SQL.90).aspx

And here: http://technet.microsoft.com/en-us/library/aa337165.aspx

So now if you re-run the report you can see it’s a data source error – a field name has been changed in the database:

An error has occurred during report processing.
 Query execution failed for data set ‘dataset_0′.
  Invalid column name ‘myNewField2′.

I also asked a question over at StackOverflow which I ended up answering myself. Yesterday follow up information was added, which may be of use if you have trouble with the fix.

EY Kalman says:

I have had the same problem (on several different servers). Applying SP3 and Report Viewer SP1 has helped on some of the servers, allowing the client machines to connect and download the control with no problem. However, I have had one server that, even after applying the updates, when accessing the report viewer using a client machine, it was still giving me the error. On looking into the exact URL GET request that is being sent, I discovered that it is possible to force the client machine to connect directly to the Report Server to download the control.

The user would need to enter the following url:

http://reportservername/Reports/Reserved.ReportViewerWebControl.axd?ReportSession=51bjqv45xydgos2wghu5ceza&ControlID=7617dedbf0234f89b80cad8e64431014&
Culture=2057&UICulture=9&ReportStack=1&OpType=PrintHtml

This should then pop up the required download/install prompt.

dotnettrio added (which is probably more relevant to RSinteract):

Hi,

I got this working with out removing any patches. The above patch was not working too. Finally what I did was on the IIS server install the following patch and reset / restart the IIS server. This is not for report manager application. This is for any ASP.NET Web application developed in .net3.5 using VS2008 http://www.microsoft.com/downloads/details.aspx?familyid=6AE0AA19-3E6C-474C-9D57-05B2347456B1&displaylang=en

I hope this helps anyone else with this problem.

The first problem I got was in the RSinteract installer (whoops, should have copied the error message) so we installed IIS and then RSinteract. When I hit the site I got this error:

The XML page cannot be displayed

Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.

---

A name was started with an invalid character. Error processing resource ‘http://myserver/RSinteract’. Line 1, Positio…

<%@ Page EnableViewState="false" Language="c#" ValidateRequest="false" AutoEventWireup="True" Codebehind="Main.aspx.cs" I…

I guess this is because IIS isn’t configured for ASPNET by default so I ran:

%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe –i

Which gave me the following error:

The error indicates that IIS is in 64 bit mode, while this application is a 32 bit application and thus not compatible.

So I made a slight change to point to the 64 bit .NET folder:

%windir%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i

After an iisreset I was now getting a 404 error from aspx pages, the final step was to open IIS (type inetmgr at the command prompt) and go to the “Web Service Extensions” node and enable ASP.NET v2.0.50727. Another iisreset for good measure and we’re now up and running:)

In the last week we’ve had three clients report a problem with our December release when running on Windows Server 2003 64 bit.

Server Error in ‘/RSinteract’ Application.

Could not load file or assembly ‘Microsoft.ReportingServices.Interfaces’ or one of its dependencies. An attempt was made to load a program with an incorrect format.
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.BadImageFormatException: Could not load file or assembly ‘Microsoft.ReportingServices.Interfaces’ or one of its dependencies. An attempt was made to load a program with an incorrect format.

One of the issues we have experienced time and again with RSinteract is a scenario where the ReportServer/Database or Analysis services is on a different machine from RSinteract as demonstrated in the following diagram. The problem manifests itself as an authentication issue when Reporting Services tries to retreive information from the Database or Analysis server because Active Directory credentials expire after the first hop, in this case from RSinteract to Reporting Services.

Microsoft are calling this the “Double Hop” problem. The reason for Reporting Services’ and Analysis Services’ lack of integration out of the box is “in the interest of security”. Active Directory uses Kerberos under the hood which can be configured to pass credentials between web apps or not. To get this working with RSinteract or indeed any ASP.NET application you need to correctly configure Kerberos delegation.

I’m having trouble tracking down the steps for Reporting Services, the link I had has gone dead since I began writing this post

So here’s the steps to configure your Analysis Services (from Business Intelligence and Agile Development Blog):

1. Download and install the SetSPN utility (Either from the Windows Resource kit, or from http://www.microsoft.com/downloads/details.aspx?FamilyID=5fd831fd-ab77-46a3-9cfe-ff01d29e5c46&DisplayLang=en)
2. SETSPN is used to configure a “Service Principal Name”, which is required by Kerberos
3. Create a Service Principal Name (SPN) for the Analysis Services Instance (on the AS server)
4. (If AS is running as a domain account) setspn.exe –A MSOLAPSvc.3/
5. Configure Active Directory Settings
6. All users that are connecting to Analysis Services through the intermediate host need to be allowed to use Kerberos Delegation (”Account is sensitive and cannot be delegated” must be unchecked)
7. The “Account is trusted for delegation” setting must be checked for each user and each service account used in the process.
8. The “Trust computer for delegation” setting must be checked for each computer used in the process
9. Configure IIS Settings for the Virtual Directory hosting the application (or SharePoint site)
10. The Authentication must be set to “Integrated Windows Authentication” or “Basic Authentication”
11. The application protection level must be set to “High (Isolated)”
12. The impersonation level for COM+ must be set to “Delegate”
13. The COM+ application identity must be set to an account where “Account is trusted for delegation” is checked.
14. Connection strings must include SSPI=Kerberos
15. Connection strings CANNOT use IP Addresses

Here’s some more information pertaining to the bug:

• http://social.msdn.microsoft.com/forums/en-US/sqlreportingservices/thread/b8ba8546-76e8-46dc-a96e-bc61e847521f/
• http://www.sharepointblogs.com/kwanl/archive/2007/01/23/double-hop-asp-net-developers-beware.aspx

I’ll update this post as soon as I find the information for configuring SSRS.

This new error has popped up since Microsoft released the update KB956391.

The update is for a vulnerability in the GDI+ DLL which allowed a malicious user to execute code on the client machine (good old! – ed). The fix uses ActiveX Killbits which is a setting that Internet Explorer checks for each ActiveX control. If the Killbits are set, IE refuses to load the control.

The update set the Killbits for the version of the RS Client Print ActiveX control which is used by the version 8.0.0.0 of the ReportViewer which is referenced by RSinteract (and Report Manager). Thus the printing will not work in either.

To fix Report Manager you need to apply the ReportViewer SP1 patch and the Security Update for SQL Server SP2 (KB954606). Once this is working again you can fix RSinteract.

To fix RSinteract you need to apply another Security Update for SQL Server SP2 (KB954607).

Let us know if this fix doesn’t work for you.