Report render failure. Error: An error has occurred during report processing. (rsProcessingAborted)

Posted in: Blog, MS CRM, MS CRM 2011, MS CRM 2013 | Mar 17, 2014 at 2:31 PM

No comments

INTRODUCTION

Seems that the rsProcessingAborted CRM SQL report (SRS) is one of the most common errors we are getting with the MS CRM system. There are few things that cause the error and I hope that through this article it helps you resolving it.

In a nutshell, the error means nothing else than “there is an error in rendering the report”. It does not denote any particular cause behind it. This article would tackle all of possible causes of the issue and if you apply all of them, it should resolve the issue for good.

NOTE: I’m using CRM 2011 for this article but the resolution should also apply for CRM 2013. This article is only based on my experience only. If you know some other causes of the error that are not yet detailed on this article please let me know. Thanks so much in advance.

CAUSE + RESOLUTION 1: KERBEROS and SETSPN for Custom Reports

The most common cause for this error is the SETSPN command that you need to execute. This is applicable to any custom reports you develop. Out of the box reports are normally working OK but custom reports are not. Therefore, to resolve this issue please follow the following:

1. Go to Active Directory Users and Computers and go to the domain account that you are using as the CRM App Pool. In my case is DOMAIN\crmapppool. Right click then Properties.
2. Go to Delegation tab and select “Trust this user for delegation to any service (Kerberos only)”.

3. Go to your CRM server, open IIS and go to your Microsoft Dynamics CRM website node. Then click on Authentication. Ensure the following are enabled:
– Anonymous Authentication
– ASP.NET Impersonation
– Windows Authentication
4. Select Windows Authentication then Advanced Settings. Ensure Enable Kernel-mode authentication is checked. Set Extended Protection to Off.
5. Click Providers. Ensure the following are in the correct order:
– NTLM
– Negotiate:Kerberos
6. Then run the following commands from the CRM server:

setspn -s HTTP/<servername> <app pool account>

setspn -s HTTP/<servername in full qualified domain name> <app pool account>

for example:

setspn -s HTTP/CRM01 DOMAIN\crmapppool

setspn -s HTTP/CRM01.dev.local DOMAIN\crmapppool

CAUSE + RESOLUTION 2: CRM App Pool accounts do not have correct permission in Reporting Service

Go to your /Reports URL and ensure the CRM service accounts (eg. CRM app, sandbox, async, deployment) have correct permission in Reporting Service.

Two areas you need to look for:
– In Site Settings (top right hand corner). Ensure those accounts have roles defined. To be safe I gave them System Administrator.
– In Folder Settings (homepage of /Reports). I gave them all roles eg. Browser, Content Manager, My Reports, Publisher, Report Builder.

CAUSE + RESOLUTION 3: Incorrect SRS Data Connector version

In my scenario I have 2 CRM server running: one is using CRM 2011 and another one is CRM 2013. Both are connected to the same SQL server but running 2 instances. One instance is dedicated for 2011 and another one for 2013 respectively.

I tried to use the SQL Server to host the report server. The problem is, you can only install one SRS Data Connector per server. Meaning that you can’t install both 2011 and 2013 SRS Data Connector all at the same time.

I installed CRM 2013 (with SRS Data Connector) first then CRM 2011. When I tried to install SRS Data Connector 2011 it prompted me with “Repair, Uninstall” window which I did not want. Then I realise you can only install 1 instance of SRS Data Connector per server. Therefore, I now point my CRM 2011 to use 2013’s SRS Data Connector.

The CRM 2011 install went perfectly except when it comes to loading the reports. Both custom and OOTB reports don’t work even though I’ve done Resolution 1 and 2 (as above).

I then realise that it’s caused by the incorrect version of SRS Data Connector.

Therefore, the only way for me to fix this is to install SSRS on the CRM Server because the instance in the SQL Server is already occupied by the 2013’s.

This now fixes the error.

I hope this helps,

Tommy

No Comments Yet.