Debugging Error: 'The X++ debugger work only for users who are in the 'Microsoft Dynamics AX Debugging Users' local group of the Windows.'

In the following sections, you determine which AOS service account to debug the RDP class in and add the account to the Microsoft Dynamics AX Debugging Users group. You create a server configuration with debug enabled and then you can add breakpoints in your code.

To determine the AOS service account 

1. From the Start menu, point to All Programs, click Administrative Tools, and then click Services. 
2. In Services, right-click the Microsoft Dynamics AX Object Server service and then click Properties. 
3. In the Properties window, on the Log On tab, the AOS service account is specified in the This account field. 

To add the AOS service account to the debug group 

1. From the Start menu, point to All Programs, click Administrative Tools, click Computer Management, and then click Local Users and Groups. 
2. In Local Users and Groups, double-click Groups, right-click Microsoft Dynamics AX Debugging Users and click Add to Group. 
3. In the Properties window, click Add and add the AOS service account to the group. 
4. Restart the machine.

Usefull debugging tip.

Useful debugging tip for tracking down the point where an exception is thrown.

Some times it can be difficult to determine where an exception is thrown.
Is it e.g. the validatefield method on a data source field on a form that throws the exception,
or is it the validatewrite method on the data source or even the validatewrite method on the table it self.

A useful trick to establish the point in the code where the exception is thrown, is to set a break point in line 11 in
the method add in the class Info.



You can find the Info class at the bottom at the class subtree in the AOT.

This will stop execution and activate the debugger each time something is added to the infolog which is normally done when an exception is thrown.