Microsoft Dynamics CRM (Archived)

custom ssrs reports don't work in crm 2013

(0) Share

Report

Posted on by TseiTsei

4,585

We made a migration from crm2011 to crm2013 and now our cutom reports don't work. We are using IFD.

When I try to run a custom report I get only this error:

The report cannot be displayed. (rsProcessingAborted)

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (1)

Community Member on at

Like (0)

Report

The rsProcessingAborted error is the generic , something is wrong message so could be anything.

It is usually because there has been a change to the schema, so the first palce I would check are that all the fields used in the datasets of the report are still there in your CRM2013 environment.

Failing that you are on to general diagnosis , try importing the report manually etc.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I came across this article the other day that points to a number of possible things to help you troubleshoot this:
http://www.mohamedibrahim.net/blog/2014/05/03/msdyncrm-rsprocessingaborted-error-fix-setting-up-service-principal-names-spn-values-for-microsoft-dynamics-crm-crm2013-service-accounts-when-reports-created-by-report-wizard-fail-during-execution/

First thing to check is always that you have the Reporting Extensions for 2013 installed on the SSRS reporting Server (which might not be the CRM server or SQL database server)

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi TSei,

Please share your error log from event viewer and trace logs.

Please have a look at this post:

social.microsoft.com/.../crm-dynamics-2011-report-error

Saad

Was this reply helpful? Yes No
TseiTsei 4,585 on at

Like (0)

Report

Thanks, I think these answers point me to the correct path. I am quite sure that the problem is related to the spn names and user accounts.

Was this reply helpful? Yes No
Arpita Saini on at

Like (0)

Report

Is this issue resolved Tsei? Like you said yes it is can be because of the SPns missing on CRM App pool account ,. Please add both http/servername and http/servername.FQDN on crm app pool.

Also set UseAppPoolcredential setting to true in IIS. You can follow below steps:-

Set the IIS useAppPoolCredentials value to True

1. Open an elevated command prompt window. To open an elevated Command Prompt window, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

2. Navigate to %windir%\system32\inetsrv.

3. Type appcmd.exe set config -section:system.webServer/security/authentication/windowsAuthentication -useAppPoolCredentials:true

technet.microsoft.com/.../dd759186.aspx

Was this reply helpful? Yes No
JonEvans 245 on at

Like (0)

Report

We used to get this a lot. Go onto the reporting server and load up Event Viewer. In Application, you should be able to see what the problem is.

It could be any number of things but it's generally an issue between the report and the database - our usual one was permissions although sometimes it was down to a data/SQL issue.

There's too many things that it could be though just from your message but Event Viewer will help to narrow it down.

Was this reply helpful? Yes No
Suggested answer

Andre Margono 2,602 on at

Like (0)

Report

I just got this error yesterday on one of the brand new IFD deployment.

Try to get the error log to see whether it's related to specific error.

In my case, I got the SQL Reporting Logs that contain the error message similar to:

Microsoft.Crm.CrmException: An unexpected error occurred.

System.ServiceModel.Security.SecurityNegotiationException: A call to SSPI failed, see inner exception.

System.Security.Authentication.AuthenticationException: A call to SSPI failed, see inner exception.

System.ComponentModel.Win32Exception: The target principal name is incorrect

In this case the resolution is to add SPN to on CRM web application:

setspn -a HTTP/<ServerName> <ServiceAccount>, where <ServiceAccount> is the account used by the CRMAppPool.

setspn -a HTTP/<ServerFQDN> <ServiceAccountDomain>\<ServiceAccount>, where <ServerFQDN> is the fully qualified domain name (FQDN) of the server and <ServiceAccount> is the account used by the CRMAppPool.

E.g.:

setspn -a HTTP/CRM01 CrmAppPoolUser

setspn -a HTTP/CRM01.OrganisationName.local OrganisationName\CrmAppPoolUser

Was this reply helpful? Yes No
Verified answer

TseiTsei 4,585 on at

Like (0)

Report

Hi

Thanks for all.

Our guy in the datacenter where our servers are located managed to solve this. Unfortunately I have not get any answer what was the problem.

Was this reply helpful? Yes No