Dynamics AX
  RSS Feed  LinkedIn  Twitter
Want to turn you're data into a true asset? Ready to break free from the report factory?
Ready to gain true insights that are action focused for truly data informed decisions?
Want to do all of this across mutliple companies, instances of Dynamics and your other investments?
Hillstar Business Intelligence is the answer then! (www.HillstarBI.com)

Hillstar Business Intelligence for Microsoft Dynamics AX and NAV on Mobile, Desktop, Tablet

Let us prove to you how we can take the complexity out of the schema and truly enable users to answer the needed questions to run your business! Visit Hillstar Business Solutions at: www.HillstarBI.com

Sunday, March 03, 2013

AX 2012 - Fatal AXRDCE Exception Error Addressed

Today, I wanted to spend a little time writing about an error that some people using AX-SSRS reports have started to run into. This is specifically related to an error that might sound something as the following.: "Fatal exception performing AXRDCE transformation step. The report cannot be rendered. Please contact your system administrator."

This error message may appear for out-of-the-box reports as well as custom development report elements. Further, this can occur even after said reports have been executing fine for a little while. There is a number of ways to get past this related to the removal of AUC files from the SSRS server, and refreshing the WCF configuration tied to the AX config file for the SSRS instance. However what I want to talk with you about on this topic today, is the ultimate fix for such issues.

For starters, you will need to launch Dynamics AX 2012, and go to the System Administrators > Setup > Business Intelligence > Reporting Services > Report Deployment Settings. This form is shown, loaded in the below image.

What we see highlighted is a form that contains a report element, one of it's design's and a check mark in a field called static. If you have a report listed in this form, as set as such with static as being applied, then AXRDCE is not used with those targeted report elements. You see the purpose of AXRDCE is to render as run-time, the needed language translations as well as contextual security. So keep these two points in mind, when you make use of the Report Deployment Settings Form.

That stated, if you list a troublesome report element as well as design within this form, having mark static. Then you deploy that specific report element to SSRS, your AXRDCE woes will be gone for good. This will tell Dynamics AX to deploy the report & it's report cultures so that the Dynamic generation of language translation does not take place.

Well that is all for this post, I hope that someone finds this useful in your Dynamics filled projects! Till Next Time!
Follow Me @:
   RSS Feed  LinkedIn  Twitter

"Visit the Dynamics AX Community Page today!"

Labels: , , , , , , , ,


Blogger fattung said...

Seen that error before and solved with deleting AUC files.

Nice to know there is a better way. Thanks!

11:38 PM  
Anonymous Yev said...

Encountered this error today and was unable to solve using this approach - after adding report to the "Report Deployment Settings" the same error was thrown when deploying the report.
SSRS restart, deleting AUC and regenerating WCF config didn't help either.
Solved by restarting all AOS and SSRS at once.

3:10 AM  
Anonymous Anonymous said...

You saved my sanity today, thank you!

10:19 AM  

Post a Comment

<< Home

Copyright 2005-2011, J. Brandon George - All rights Reserved