Dynamics Talk

In AX2012, while using the Excel add-in, you might receive the error: “The role that you are assigned does not have permission to access the selected data.”

Cause: A Full CIL or Incremental CIL might be running, causing this error.

Project managers and clients don’t really understand the complexities of upgrading an environment to a new Roll-up / CU version.  Well, how difficult can it be?  And why can’t it be done right now?

Well, usually it is not a problem.  As a developer you compare your code, if changes were made on existing objects and make sure you merge the new code with your code.  And everyone is happy.

However, what happens when you have other partner products on your AX Environment.  What if those products were build for a different Roll-up / CU version.  Now suddenly it becomes a whole lot more complicated to do the upgrades.

At some of our clients, we have had to merge code over 4 to 5 layers.  You can easily lose your head with a merge, especially with methods that are quite large.

Let me explain this with an example:

On the Class: \Classes\CustVendCreatePaymJournal we’ve create a new variable in the Class Declarations on the CUS Layer.  We’ve also installed a partner product (on the VAR layer), which  also created a new variable in the Class Declarations.  As part of the normal merging process, we made sure we merge the Variable back into the CUS Layer.  Microsoft also created some methods on the class both on the SYS and SYP layers.  All of these changes were done on AX2012 R3 CU8.  Everyone is happy…

We received a request from the client to upgrade to the latest CU version (CU10) ASAP.  We notified the client that not all of the partner products are available on CU10.  Our client told us to still continue with the upgrade.

With the upgrade, Microsoft made some changes the the SYP layer.  As part of the merging process, a developer usually compare the first layer in our case the CUS layer, and the layer just above it, i.e. VAR layer in this example.  However, by doing this we are missing out on any changes that might have occurred on the SYP layer, thus causing compile errors, because the variable for the SYP layer was never linked in the code.

Well, what is the problem then.  Well, in some environments we have code changes in methods that have 100s of lines of code.  You then have to compare your custom code with the changed layer (SYP), compare it with the changes on the ISV, ISP, VAR, VAP layers (and yes we do have clients with these setups).  And finally you have to apply the combined merge on your CUS Layer, which can get quite complicated, especially when the changes were not property commented in code.  remember now, the ISV, ISP, VAR and VAP layers also contain their own code custom code, which was created for an older CU version.  You can not easily identify the SYP changes, because it might actually changes on top of the SYP layer, which will not provide you will a clear indication of the change.

Lesson learned:

Wait for all products / to be upgraded before you try to upgrade your own code to the new Rol-up / CU version.  That way you will not have to try and figure our code changes over multiple layers.

Symptom:

In Microsoft Dynamics AX 2012 R3 CU8, we found 22 errors after running a full compile on the AOT, all related to the Summetry Namespace. After researching the web, and trying all of the solutions offered on other websites, we were still getting exactly the same compile errors.

You can read more about what we have tried on these websites:
https://community.dynamics.com/ax/f/33/t/126055.aspx
https://community.dynamics.com/ax/f/33/t/150222.aspx

Event Log:

The error we received in the event log was:

“The description for Event ID 110 from source Microsoft Dynamics AX cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Microsoft Dynamics AX Business Connector Session 7.
Failed loading assembly ste-net, Version=1.0.1.74, Culture=neutral, PublicKeyToken=5542884f620dbde5”

Compiler output:

Example Code containing error:

“Symmetry.TaxEngine.BenefitInfo benefitInfo401_403;”

“Symmetry.TaxEngine.STEPayrollCalculator             ste;”

“Symmetry.TaxEngine.STEPayrollCalculator             ste;”

Solution:

Finally we took the DLLs from an environment that worked and copied them to our environment. The Dlls were different, and in size and date.  this solved the problem.

By reinstalling the binaries again from AX2012 R3 CU8 installation file also solved the problem.

Symptom:

When a user tries to invoice a purchase order that is linked to a Project, the user might receive the following error:

SysDictTable object not initialised.

Stack trace

(S)\Data Dictionary\Tables\SourceDocumentHeader\Methods\getSourceDocumentImplementation – line 5
(S)\Classes\SourceDocumentLineItem\parmSourceDocument – line 8
(S)\Classes\ProjectSourceDocumentLineItemHelper\projTransType – line 21
(S)\Data Dictionary\Tables\ProjectAccountingDistribution\Methods\transactionCurrencySalesAmt – line 31
(S)\Classes\ProjFundingLimitTrackingManager\createProjTransFromProjDist – line 43
(S)\Classes\ProjFundingLimitTrackingManager\updateUsingProjAccountingDistribution – line 45
(S)\Classes\ProjFundingLimitTrackingManager\updateUsingAccDistribution – line 30
(S)\Data Dictionary\Tables\AccountingDistribution\Methods\Update – line 9
(S)\Classes\PurchFormletterParmDataInvoice\updateSourceDocumentLines – line 47
(S)\Classes\PurchFormletterParmDataInvoice\reArrangeUpdateParmLine – line 19
(S)\Classes\PurchFormletterParmData\reArrangeLines – line 152
(S)\Classes\formletterParmData\doReArrange – line 15
(S)\Classes\formletterParmData\reArrange – line 8
(S)\Classes\PurchFormletterParmData\reArrangeServer – line 7
(C)\Classes\PurchFormLetter\reArrange – line 21
(C)\Classes\PurchFormLetter\run – line 11
(C)\Classes\PurchFormLetter\main – line 62
(C)\Classes\FormFunctionButtonControl\Clicked

Error Message (03:26:41 pm) Removal of suspension of recId allocation for table VendInvoiceInfoTable has failed.

Solution:

Download and install hotfix 2909584.

http://support2.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2909584

Important!!!

Install and recompile for all class changes to take effect.  Also do a Full CIL compile.  The code is executed within via the CIL.  There is also some upgrade script that need to be executing, so make sure you complete the checklist.

When exporting certain reports from Microsoft Dynamics AX 2012 to Excel, the values are exported as string instead of numbers.

To replicate the issue:
1. Menu: General ledger > Reports > Reconciliation > Vendor > Vendor
2. Click Ok on the dialog window.
3. Once the report has been deployed, click on the Export > Excel button
4. Specify a filename and click save.
5. Open the Excel report
6. Try some math functions with some of the fields, e.g. “=E1+1”
7. Excel will display: #VALUE!

Reason:
The report is exporting the field as a string. Within the SSRS Report, you will find the code:
=Microsoft.Dynamics.Framework.Reports.BuiltInMethods.ToDisplayStringAmount(Parameters!AX_RenderingCulture.Value, sum(Fields!LedgerAmountMST.Value), true)

This is causing our values to be returned with a space as a thousand separator, but this is not a normal space (Ascii 32). It is a non-breaking space (Ascii 160).

I assume our localisation settings is causing this. We are using a space for our thousand separator.

Solutions:
1. Firstly you can remove the “Microsoft.Dynamics.Framework.Reports.BuiltInMethods.ToDisplayStringAmount(Parameters!AX_RenderingCulture.Value, ” from the report, leaving you with: sum(Fields!LedgerAmountMST.Value). Remember to redeploy the report.
2. The second option is to do a find and replace within Excel. But the trick is to not replace the normal space (ascii 32), but replace 0160. Use ALT 0160 as the find string.
3. Copy this if you can’t use your Alt and number pad: ” “.

Reports causing this error:
I was able to find only one report with this issue, the Vendor / Ledger Reconciliation report.
Menu: General ledger > Reports > Reconciliation > Vendor > Vendor

We will list a number of Errors that you can receive within Microsoft Dynamics AX 2012, and the solutions to get AX to work again:

1. “No connection could be made because the target machine actively refused it xxx.xxx.xxx.xxx:8201”

When printing a report, that is using SSRS to produce the report, you might receive the following error:

“No connection could be made because the target machine actively refused it xxx.xxx.xxx.xxx:8201”

There can be a number of reasons why this is happening:
1. The quickest solution is to do a Full CIL Compile. See if that does not resolve the error. Please note, any service that is dependent on the CIL will no longer work, which includes SSRS, Workflow and AIF.

2. Check that the WCF confirmation is correct and you are able to refresh it. I have found the following sitsuation at one of our clients. They are using 2 IP addresses for each server. The IP address we RDP with works fine, but for some reason another machine on the network grabbed the IP address. When I tried to refresh the WCF configuration, the gave me any error.

3. Check that the Proxy settings within internet explorer is not set, or setup correctly – to bypass local addresses.

I hope this gives you a starting point.