Fetch XML Reports not working

(0) Share

Report

Posted on by Community Member

Hi All,

We are currently working with CRM 2011 UR 13.

We are facing the issue with reports. We developed some reports using SSRS and used SQL Server filtered views to create reports, the reports working perfectly. However, whenever we create any report through report wizard, it creates the report successfully. However, it does not run and end up with rsprocessingaborted error.

No error messages generated in the vent viewer as well. Basically this is the issue with all Fetch XML reports. Are we missing any specific installation. Since, the other custom SSRS reports are working, so it proves that SRS Data connector is working correctly.

Any help on this is appreciated.

*This post is locked for comments

I have the same question (0)

All responses (11)

Answers (0)

Dave Ireland on at

Like (0)

Report

Maybe an SPN issue? Here's a post I wrote a while back that might help:

www.salentica.com/crm-2011-when-crm-custom-reports-dont-work

Dave

Was this reply helpful? Yes No
Joe Woltering 12,163 on at

Like (0)

Report

Hey guys, I'm having a very similar issue which I started a post about here as well https://community.dynamics.com/crm/f/117/p/105583/205715.aspx#205715

Very frustrating as they make it seem so simple and the functionality that it could provide is invaluable.

What I did:

-Created Shared Data Source in VS 2008 using Windows Integrated Authentication and plugged in my CRM URL. This all worked fine and I was able to create a report using the FetchXML query I pulled from an Advanced Find.

-Deployed the report and data source to my report server and tried to launch the report and got the rsprocessing error like the OP mentioned. Mine stated that the organization didn't exist. Did some research and changed the data source credentials to use the systeusrid and organizationid as pulled from the SQL table. Got a different error this time stating that the user did not have the privilege to run the report on behalf of the report user. Did some more digging and changed the Reporting Service account to the same user as the CRM service account. This still did not work but then I changed it back to NETWORK SERVICE and miraculously the report pulled up. Great.

-Now, back to VS, created a new report trying to use the data source w/ the updated credentials and got an error in VS (ID3242) stating that 'ID3242: The security token could not be authenticated or authorized.'

And that's where I'm at. Completely befuddled.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Any answer for this...

Was this reply helpful? Yes No
Suggested answer

Joe Woltering 12,163 on at

Like (0)

Report

What is the exact rsProcessingAbort error you are getting? I resolved my issue by using the unique systemuserid (GUID) and OrgID (GUID) of the user you want to use as the username and password for the DataSource credentials-- You can get this by running the query against the CRM database:SELECT fullname, systemuserid, organizationid FROM FilteredSystemUser--and then making sure whichever user is actually viewing the report is added to the PrivUserGroup in AD.

Was this reply helpful? Yes No
Muhammad Adeel Javaid 5,580 on at

Like (0)

Report

This could be of help for you:

social.microsoft.com/.../1fe671ed-ec4e-4773-9029-29120f2872b4

Was this reply helpful? Yes No
Raksheet Koradia 45 on at

Like (0)

Report

Hi Amit,

Recently we have came across a issue where reports created by report wizard may fail when executing. While browsing and seraching throught I came across a micorsoft KB article which says this could be issue with all the fetch Xml reports. Check this link :

support.microsoft.com/.../2590774

We have tested the workaround mentioned in the link and it was working fine!!!

Hope this will help you too!!!

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

the SETSPN - a HTTP/CRMservername domain\account where account = sql reporting service logged on account name worked for me . Bit surprised Microsoft doesn't just get 2 of its products to simply talk to each other.

Was this reply helpful? Yes No
Shahid H Shaikh 495 on at

Like (0)

Report

Hello Amit,

Most of the times, the reason for issues with fetch based reports is Incorrect/Non Existent service principal names because The FetchXML query needs to be able to resolve to a HTTP SPN in order to fully communicate between the server. In a scenario where the Microsoft Dynamics CRM application pool is being run by a domain account the query will be looking for a HTTP SPN that does not exist by default.

You can either verify the Service Principal for the service account running the reporting service by following the KB article support.microsoft.com/.../2590774 or you can use the workaround provided in the article, however the work around should be used in short term scenarios where there is a more extensive process in place to get SPNs approved.

Was this reply helpful? Yes No
SunilR 5 on at

Like (0)

Report

For us it was happening on CRM online 2011, the same error. However in our case the user (or the security role) did not have permission to one of the entities that the report was trying to pull.

Was this reply helpful? Yes No
suresh maurya 630 on at

Like (0)

Report

For testing of FetchXML, you can test here online http://msxrmtools.com

Was this reply helpful? Yes No