Problem / Symptom: When publishing a journal you receive a generic “Microsoft.Dynamics.Ax.Xpp.InfoException” was thrown error. Or you receive an error “Account number for transaction type Bank does not exist.”
Description: We received this error reported by the client when trying to post a general journal recently. They received the generic type of XPP error as shown above and were not able to diagnose the problem correctly
Solution: The first step to resolving this issue was to receive better error messages so that the problem can be diagnosed. By disabling the “Execute business operations in CIL” option for the user for the duration of debugging. To do this:
1. Navigate to System Administration -> Users -> Options -> Development.
2. Untick the “Execute business operations in CIL” option.
After performing the above we were able to get a better description of our problem. “Account number for transaction type Bank does not exist.”
We were then able to diagnose that the bank account used as the offset account did not have a “main account” number setup for it. This may have been due to faulty importing. To resolve:
1. Navigate to Bank -> Cash & Bank Management -> Bank Accounts
2. Select bank account in question, click edit
3. Expand currency management and select a main account.
Problem / Symptom: You want to ensure that all your users’ Dynamics AX clients are updated to the correct rollup.
Description: You may have recently upgraded your Dynamics AX Kernel or Application to the latest Cumulative Rollup (CU), you’ve applied it to all of your AX Client installations that you are aware of but you would still like to make sure that nobody is logging into AX on an old version and potentially causing some problems. You may also be receiving an error in your AOS event log that goes something like this
Object Server 01: Internal version mismatch. Microsoft Dynamics AX client from [MACHINENAME] (126.96.36.199) tried to attach with 6.2.1000.4051 revision of kernel.
Solution: (Applies to AX 2009 & AX2012) There is quite a simple solution to this issue.
- Open up any Dynamics AX client connected to the AOS in question.
- Navigate to System Administration -> Enquiries -> Users -> User log
- Right click anywhere in the grid, click personalise
- Click “add fields”
- Expand “User log”
- Select “Build number”, Click Add
- Close the Select Fields form
- Close “Personalise Form”
Your User log form will now show all sessions and their build number. You can now browse and field all sessions that don’t have the same build number as your kernel. You can also further filter this form to only show the non matching records by right clicking on the Build number field and entering “![buildnumber]” (see screenshot below)
Click on the “General” tab to find out which computer/workstation the invalid session was coming from. You can now go and run the updates.
Problem / Symptoms: Users need to test Dynamics AX setups as different users.
Description: Quite frequently we are finding the need to test/run Dynamics AX as a different user from our default login user but do not want to run multiple remote desktop sessions or have to log in and out of our current session. We may need to do this for a number of reasons e.g. Testing a workflow approval process i.e. login to approver as the relevant user, Testing security permissions, Testing SSRS permissions, getting screenshots of AX for documentation with a different profile etc…
Solution: There are a number of ways to do this, I have been using CMD/DOS scripts to do this for years (more on this below). But I just found the simplest trick in the book:
1. Locate a shortcut (won’t work for config files) to Dynamics AX,
2. Right click, if you’re lucky (depending on operating system) you will see a “run as a different user”. Select this option, enter your user details and AX will run as this alternative user
3. If there isn’t a “run as different user” option, simply hold in shift and then right click, you should now see the “Run as different user option”
If you are running via config files this solution will not work, you will need to first create an AX32.exe shortcut that takes the config file as a parameter E.G.
C:\Program Files\Microsoft Dynamics AX\60\Client\Bin\Ax32.exe" -regconfig=C:\myconfig.axc
You can also create a .bat file with the following code:
runas /user:user1@mydomain "\"c:\Program Files (x86)\Microsoft Dynamics AX\60\Client\Bin\Ax32.exe\" \"C:\myconfig.axc\""
Problem / Symptoms: SSRS Reports executed from code under limited security permissions are not displaying in AX2012 R2 or above.
Description: When running an SSRS Report that is being kicked off via code from a user role with limited security permissions, neither the report nor the report viewer is displayed. No error messages are presented. Under elevated (admin) permissions the reports are displayed. The same user is able to execute normal reports via menu-items.
The debugger will fail in class: SRSReportRun.constructReportSettings on the line settings.SetWebServiceUrl(serverConfig.serverId(), serverConfig.reportServerURL());
Solution: I wasn’t able to find any specific security permissions linked to this error that would fix the security role, however I did discover that AX seems to have deprecated the use of the SRSReportRun class in favour of the SRSReportRunController class.
srsReportRun = new SrsReportRun (‘MyReport.ReportDesign1′);
controller = new SrsReportRunController();
Welcome to my new blog Explore AX.com. With the advent of AX2012 and all its nifty new tools I decided that it was time to find a spot to collect all my little scripts, coding techniques and general notes to remember. Most things here will be related to development and technical issues, however you may find a few functional things as well.
For those of you who may have read my blog workflowax.wordpress.com, I have decided to keep that blog separate and dedicated to all things workflow and not pollute it with general AX stuff.
Most blog posts will be written in a typical Knowledge base approach i.e.
- Problem Statement,
- Steps to replicate
- Resolution / Howto
Anyway, I hope you enjoy the blog!
Feel free to leave comments or questions.