(Applies to Microsoft Dynamics AX 2009, Microsoft Dynamics AX 2012, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 R3 )
Normally we need to Plan our Microsoft Dynamics AX (TEST, UAT and Training Environments)
Make sure your AX environment is properly configured for a production environment.
Some specific notes:
If you are not yet live, and have some Visual Studio experience on staff, I highly recommend using the Benchmark Toolkit - http://www.microsoft.com/en-us/download/details.aspx?id=39082 to simulate a full load on your system. Additionally, make sure to test your Terminal/Citrix servers at full load.
If any of your infrastructure is Virtualized pay close attention to CPU load, I/O, RAM and Network.
Is the issue being seen by one user or multiple users?
1.Check SQL for Blocking/Locking, RAM, CPU, Disk Space and Disk utilization.
Lastly, check to make sure that any users have access to the SQL server are not running expensive queries. As a general rule, make sure that no one have ODBC access to your production database.
2.Check the AOS server(s). Look at RAM, CPU and Disk Space. You should regularly be monitoring the RAM usage of the AOS service to determine what is normal for your environment. If overloaded, an AOS restart will fix the problem but Root Cause Analysis (RCA) analysis will be required. If you are regularly seeing Memory issues, check your buffer settings are appropriate, check to make sure that a table caching is appropriate for the number of records in the tables. It is possible the settings from go-live are no longer appropriate based on record growth.
3.Terminal/Citrix - Look for CPU/RAM/Hard Disk issues. Check the number of users or maybe other applications on the servers are eating up the system resources.
4.SSRS - Check CPU/RAM/Hard Disk. The service restarts regularly and can slow report processing down. Here is a tool to make sure they keep running fast - http://blogs.msdn.com/b/axsupport/archive/2014/03/11/ax-content-warm-up-those-ssrs-servers.aspx
5.Check batch processing in AX - are there new batch processes which are using a lot of resources?
6.Check infrastructure - Network, Switches, etc.
7.Client issues - Are patches being applied or recently applied? Is a weekly virus scan running?
8.Is it month end or year end? The month end process involves a lot of intensive reports and processes. Can you move any of these to low activity times via batch processing?
2.Like above, check the Terminal Server, Infrastructure, Patching and AV scans.
Code can cause many issues from too many database calls, poor use of indexes, over complexity.