Hello,
Whenever I am trying to start trace from Tracing cockpit it gives following error:
Error starting server trace
Please guide how to resolve this issue.
Regards,
Pankaj Srivastava
*This post is locked for comments
If you get the error message "Access is denied." or "Error starting server trace." the following steps could help you:
Check the application event log for errors. Error code 5 indicates an access denied issue.
You ahve to right-click and select "Run as Administrator" in order for the trace collection to start just like you did when opening the AX client utility.
The account running the AOS instance must belong to the 'Performance Log Users' local group on the AOS if it is running on Windows Server 2003 or 2008. The WMI event tracing subsystem requires that tracing can be started only from a user belonging to this local group or to the local Administrators group.
After this change you have to restart the AOS-Server
The client trace is initiated by the currently logged on user, so verify that that user has access to the log path defined in the client configuration utility. You can adjust the location of the log in the client configuration utility if necessary for testing.
The server trace is initiated by the account running the AOS instance, so verify that that user has access to the log path defined in the server configuration utility. The log path cannot be changed in the server configuration utility, but it can be changed directly in the registry if necessary. Here is the registry path where the log directory is defined for a Dynamics AX 2009 instance using the Original installed configuration: HKEY_CURRENT_USER\Software\Microsoft\Dynamics\5.0\Configuration\Original (installed configuration)\logdir
User Account Control (UAC) has prevented traces from starting from time to time. When opening the client utility, try right-clicking and selecting "Run as Administrator." If that doesn't help, try tracing with UAC disabled on the server.
Hello Paul,
Thanks for your guidance however it didnt worked for my issue.
I tried all the suggested way but no change.
Hi,
Here is a few things to try.
When starting the client use "Run as administrator".
Run the trace from the AOS-server.
Use an valid UNC - not a normal drive letter - for the trace result.
.søren
I Paul thank for this post, this worked for me...... simple approach was to use "Run As Administrator".
Thanks Paul. 'Run as Administrator' worked for me.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Martin Tocauer 4
Community Member 2
Nayyar Siddiqi 2
