Microsoft Dynamics AX

Axapta

CIL execution to be disabled for all AX users

Recently we have faced an error during SSRS report printouts, where the quick fix was to temporarily disable CIL execution for all regular AX user accounts.

The error message was as per below, and this MSDN blog post has pointed us in the right direction of resolving the problem:

Failed to create a session; confirm that the user has the proper privileges to log on to Microsoft Dynamics.

The following job can be used to disable CLR operations. It essentially changes the Execute business operations in CIL setting under Options > Development tab based on the flag defined:

(more…)

By |2015-11-23T17:36:22+01:00November 23rd, 2015|Categories: AX 2012|Tags: , , , , |0 Comments

AX clients with an outdated kernel executable version (SCOM, Blocking)

There are AX installations that do not fully rely on Remote Desktop Services technology, but rich clients are used which may connect to the AX AOS with a potentially outdated Ax32.exe kernel binary version. If a new kernel binary hotfix is installed on the AOS, then the clients must also be patched up, since the communication protocol could have been changed. It is absolutely crucial to get the kernel hotfix applied to the AX clients, but it is not always that convenient to find whom to patch.

If someone connects with an old kernel version, the AX AOS creates an event log entry, that we can get notifications for if we use System Center Operations Manager (SCOM): Application warning: Object Server 01: Internal version mismatch. Microsoft Dynamics AX client from COMPUTER (6.0.1108.3733) tried to attach with 6.0.1108.7309 revision of kernel

In SCOM 2012 AX management pack the alert is generated as “Internal AOCP revision mismatch”, and the actual computer name can be seen under View additional knowledge > Alert context > Event data.

The next step is to block access for these clients.

(more…)

By |2015-11-23T17:40:40+01:00November 11th, 2015|Categories: AX 2012|Tags: , , , , |0 Comments

Find missing objects behind menu items

As part of our code cleanup exercise we have discovered that there were menu items pointing to objects which no longer exists in our environments, ie. legacy reports which were upgraded to SSRS but their menu items were never removed.

The following job could be used to identify such missing objects for any of your menu items. I would also recommend to double-check the xRef references to find connected objects, like security privileges/roles, to completely remove whatever you do not need.

(more…)

By |2015-11-23T17:42:08+01:00October 27th, 2015|Categories: AX 2012|Tags: , , , , , |0 Comments

AIF port changes without deactivating

For troubleshooting the Application Integration Framework in AX sometimes we have to enable logging of all XML document messages. However the AIF inbound ports cannot be edited by default without deactivating them first. It is a common misbelief that you need to do this.

If you deactivate and reactivate a port, in the background it just regenerates the server-side WCF settings in table AIFWCFConfiguration, that stores the XML string in a container field. Most of the values in there does not actually relate to a lot of fields that you should be able to change. In our case the LoggingMode field was in the scSC parent table of AIFPort.

What we could do instead of deactivating and reactivating our service in question to switch the logging on and off was to simply edit the record in the table browser, which does in fact take immediate effect and the logging will commence or get suspended once you save the row. Please keep in mind that for other fields such as user restrictions or service operations you should do your own research in a Test environment first to decide if it is safe to go ahead with the modification.

By |2015-11-23T17:43:17+01:00October 15th, 2015|Categories: AX 2012|Tags: , , |0 Comments
Go to Top