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 @:
       

"Visit the Dynamics AX Community Page today!"

AX 2012 Excel Add-in - RPC Issue

I hope everyone is doing well, and into the Dynamics World, on this fine Tuesday. We will continue our focus on EP tomorrow, but today, I wanted to spend a little time and write about a specific issue when using the Excel Add-in for Microsoft Dynamics AX 2012. What I'm talking about, can happen in a few different possibilities. Specifically however, and more to the direct error message. If you have Failed records when using the Excel add-in and the error message for each record is very generic, you should then move towards looking at the Application Event Log, where the Excel Add-in is being executed.



Within the Application Log, you will most likely see an RPC Exception 1702 or 1700 or 1704. Now the Excel Add-in is suppose to be connecting and communicating through WCF protocol for the Query Service, and other such services? Why RPC? Well there is a part of the .Net BC still used, from what I've found - needs clarification - with this process.

So how do we reach this error? Well most likely something has changed about a table your trying to access, or a Data, ie: Query or Service, that your trying to consume. For example you might have added a new import staging table to your instance, saw it fine in the Add Data, Add Tables list.



However now that you go to publish the data, from which you have built the excel table with - all records fail? This is a sign, that a Full CIL needs to be executed on the target instance in which the Excel Add-in is pointing to. This has been the fix for such issues, I've come across - every single time!

In short, running into errors with the Excel Add-in, specifically RPC errors in the Application Event log, then perform a full CIL compile on the target instance. Doing so should get you past such issues, and should allow you to proceed using Excel Add-in and your changed or new table - for loading data.

That's all for right now, I will leave you with a link to the past post I did about the Excel add-in.: AX 2012 - Excel Add-in Revisited. We will continue the EP and BI paths, as well as I have a slew of highlights, book reviews, and spotlight post coming soon. Along with a new interview from a Microsoft Executive, to help close out FY12 for Microsoft. So check back soon, and often. Till Next Time!
Follow Me @:
    

"Visit the Dynamics AX Community Page today!"

AX 2012 - Process Cubes Error: translations in Standard Edition

I hope everyone is having a great week so far. Like I said in a previous post, I love spring, and we got a cool reminder these past two days in the south that it is still spring. 37 Degrees at night is way to cold for my blood, this close to May. With that cool reminder of spring, let me jump right into today's post. You might get this error message: "Only dimension attributes and attribute relationships can have translations in Standard Edition" When you process cubes, after deploying them in AX 2012 on a SQL Server Analysis Services, Standard Edt.

If you happen to get such a message, and need help getting past it, make use of the following steps and you should be back on track for processing those out-of-the-box cubes.



What you see in the above image is the location of the Analysis Services Project. This is what you want to make sure and delete. This is what is used to actually build, or update the cube structures. It houses the Datasource, Dataview, and all cube, dimension, etc. setup and design. This project can be accessed, via highlighting it, after deleting it, and then right click, and left click on edit.

Moving beyond this project however, once you have deleted it, the next step is going to be update the cube designs. You can do this, through the Business Intelligence tools menu option, for the "SQL Server Analysis Services project wizard".



The next screen you should see is the 'select option' form, in which you need to select the Update option. This will take the Analysis Services Project, and use it to build out the cube structures in the Analysis database. Since we want out-of-the-box, then this is the option we want to take.







Now having a success on the verifying screen, we can move on to the confirmation of changes.



This, now will show changes across the board from the project. Seeing this means that all of the elements will be dropped and recreated. This is critical for changing the translations setup. In doing this, you should be able to move on to processing and not have any such issues moving forward.

Now that this is taking care of you should be able to process cubes without such issues. You will run into this, if you are trying to get your out-of-the-box AX 2012 cubes, deployed and then processed on a SQL Server Analysis Service's Standard Edt. Finally, I will leave you with, I have this now running on SQL Server 2012. More on that, and other topics later! Till Next Time!

Update: For those of you who run into any issues with the update choice, you can also go with Deploy. Doing so will take the Analysis Services Project, deploy and process it. This all assumes out-of-the-box, when talking about this issue.





Follow Me @:
    

"Visit the Dynamics AX Community Page today!"

Some blog spotlights: AX and the Cloud Example, AIF Error and AX 6.0 Xpp Editor Updates

I have been really busy, and I have some good post that I hope you will enjoy coming up soon, including a new article I will be writing for MSDynamicsWorld.com.

With that said, there have been some really great post over the past several weeks, and I wanted to make sure and highlight them.

The fist is DAXGuy's entry, on an AX example for working with the Cloud. As I wrote about early this year, What can the Cloud offer you in 2010?, 2010 for sure is going to be the year of the cloud. DAXGuy took this further with all the talking, and gave us a really good walk through example of how to get a service in the cloud up and running, and make use of it with Dynamics AX. That post can be found here.: AX on Cloud 9



From the post.:
"Lately there has been a lot of activity related to cloud computing with introduction of Windows AZURE. It truly is an interesting technology providing businesses wider opportunities. Well I decided to explore AZURE a bit and did a small POC on AX integration with AZURE... ... I was consuming a AZURE WCF Service from Dynamics AX. There is a lot of potential in this. Maybe in next generation AIF , developers will be able to generate Cloud AIF directly from AX."

Next in line, we have Dianne Siebold's weblog about AIF. Recently, she posted about the discovery of a very unintuitive error message that you might get and how to start troubleshooting it. That post can be found here.: “Request Failed” Error in AIF

The request failed with the following error: The element 'SalesTable' in namespace 'http://schemas.microsoft.com/dynamics/2008/01/documents/SalesOrder' has invalid child element 'LanguageId' in namespace 'http://schemas.microsoft.com/dynamics/2008/01/documents/SalesOrder'.

List of possible elements expected: 'QuotationId, ReceiptDateConfirmed, ReceiptDateRequested, RecId, RecVersion, Reservation, ReturnDeadline, ReturnItemNum, ReturnReasonCodeId, ReturnReplacementCreated, ReturnReplacementId, ReturnStatus, SalesGroup, SalesId, SalesName, SalesOriginId, SalesPoolId, SalesResponsible, SalesStatus, SalesTaker, SalesType, SalesUnitId, SettleVoucher, ShipCarrierAccount, ShipCarrierAccountCode, ShipCarrierBlindShipment, ShipCarrierDeliveryContact, ShipCarrierDlvType, ShipCarrierExpeditedShipment, ShipCarrierFuelSurcharge, ShipCarrierID, ShipCarrierResidential, ShippingDateConfirmed, ShippingDateRequested, smmCampaignId, smmSalesAmountTotal, StatProcId, TaxGroup, totalBalance, TotalCashDiscount, TotalInvoice, TotalMiscCharges, TotalSalesTax, TransactionCode, Transport, URL, VATNum, SalesLine, DocuRefHeader, MarkupTransHeader' in namespace 'http://schemas.microsoft.com/dynamics/2008/01/documents/SalesOrder'


This is actually a very helpful tip and post when working with AIF and you start getting some strange error messages that's hard to discern what is really going on.

Finally, Vicent, who posted last October about some update highlights to the X++ editor in Dynamics has some new material up, for a part II on what's new in the X++ editor. I wrote about part I, here.: Dynamics AX 6.0 - aka 2011 - X++ Editor

Well you can find his latest entries, by going to the following link.: Dynamics AX6 – The new X++ editor (part 2)

"In a completion session, holding the ctrl key will make the drop-down dialog transparent, so you can see the code underneath:"





I want to say thanks to each of these fine bloggers for sharing their information with the rest of the Dynamics Community. It's because of such efforts that the Dynamics Community continues to grow, and is able to help those looking for solutions.

That's all for now, but as I pointed out in the start of this post, I have some really nice entries coming. Check back soon, and see you then!




"Visit the Dynamics AX Community Page today!"

e-Con 4.0 Error - MSXML 4.0

Alright, if your setting up e-Con 4.0 and get the following error:


"Retrieveing the COM Class factory for component with CLSID {88D969C1-F192-11D4-A65F-0040963251E5} failed due to the following error: 80040154"

This error, when seen from going into the e-Con Studio, means that the MS-XML Parser 4.0 or greater is not installed on the e-Con Server machine or client.

I ran into this again today, and wanted to make sure this was posted out here on the web. Check back soon!




"Visit the Dynamics AX Community Page today!"

SysDictClass and some CAS

I ran into an issue when working with the SysDictClass. I am using this to do some 'smart' coding and make use of reflection, in order to speed up my development and not have to manually write code over and over again for the same type of thing. In doing so, I found out that this is considered a protected API now in DAX 4.0, and so you need to make use of an 'ExecutePermission' CAS Permission object, and assert that level of permission.

The error message looked similar to this:

"Request for the permission of type 'ExecutePermission' failed.
(S)\Classes\ExecutePermission\demand
(S)\Classes\DictClass\callObject
..."

So if you see this type of error, then make sure you perform an ExecutePermission Object. assert() before the code, and revert that assertion after the code block. In doing so, you will have gotten rid of this little issue.

This is the first time I had to make use of this code in a while, and so first time I ran into this being a protected API. I hope this helps someone out, as I did not find anything on the web, when searching.

Check back soon!


Find a job at: www.DynamicsAXJobs.com