Turn On AOS Logging in AX 2012

(0) Share

Report

Posted on by BP-22040756-0

Hello,

I would like to turn on AOS logging in AX 2012. To be more specific, I would like to log every activity from the AOS in a trace-mode manner and dump the activity into a log file.

I'm facing an error where the AOS crashes unexpectedly and our system is not producing any logs. The crash happens when loading an SSRS report in Visual Studio.

Does anyone know how to accomplish this?

I have modified this config file and restarted the AOS:

C:\Program Files\Dynamics AX\Microsoft Dynamics AX\60\Server\<AOS_instance_name>\Bin\Ax32Serv.exe.config

<trace autoflush="true" indentsize="4">
  <listeners>
    <add name="TextWriterListener" type="System.Diagnostics.TextWriterTraceListener" initializeData="C:\Temp\trace.webinfo" />
  </listeners>
</trace>

I'm not seeing any logs in any log directory. For example, C:\Program Files\Dynamics AX\Microsoft Dynamics AX\60\Server\Log\ nor any logs in C:\Program Files\Dynamics AX\Microsoft Dynamics AX\60\Server\<AOS_instance_name>\bin\Application\log

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (3)

Verified answer

Bilal Issa 4,370 on at

Like (0)

Report

Hi,

please try the link below.

http://blogs.msdn.com/b/axsupport/archive/2010/10/18/aos-crash-hang-or-memory-leak-debugging-tools.aspx

Regards,

Bilal

Was this reply helpful? Yes No
Verified answer

Martin Dráb 237,880 Most Valuable Professional on at

Like (1)

Report

You could use tracing, but you mustn't forget to specify the trace source you're interested in.

Nevertheless if you want to analyze why the AOS crashed, you should create and analyze a memory dump. That's something else than tracing. Look at Possibilities to create Memory Dumps from crashing processes for more information. Also note that LCS now contain a tool for basic analysis of the dump.

Was this reply helpful? Yes No
BP-22040756-0 on at

Like (0)

Report

Martin, thank you for the hyperlinks. I like the idea of running a trace. The challenge I have with TraceParser is that since it's initiated from the AX Tracing Cockpit, once the AOS crashes during the trace, it fails to save the log to the .etl file. I have also tried ProcMon but I either get too much or too little activity.

I just thought of something. I have a feeling there is no such thing as "AOS logging," similar to the way AIF and SSRS logs data to a text file. It kind of makes sense because the AOS does so much that it's impossible to write every little detail. Is this correct?

Was this reply helpful? Yes No
Suggested answer

Martin Dráb 237,880 Most Valuable Professional on at

Like (0)

Report

The whole nature of process crash is that fails unexpectedly and doesn't have chance to write log files or anything. If the processes ended gracefully, it wouldn't be a crash. That's why tracing, unlike memory dump analysis, can't cover this situation.

I don't know what kind of logging you imagined to exist. AIF is an application framework, so it runs on AOS and if the AOS crashes, AIF obviously crashes too. You can implement any logging you like in the application layer, but it will always have the same problem.

Was this reply helpful? Yes No
Verified answer

syed baber 11,633 on at

Like (0)

Report

Hi Bobby,

There is a new feature recently introduced in LCS named "Crash and Hang Analysis". Below is the link to the official post:

blogs.msdn.com/.../crash-and-hang-analysis-on-lcs.aspx

This may help.

Thanks,

Baber.

Was this reply helpful? Yes No
BP-22040756-0 on at

Like (0)

Report

Thank you all for your responses. The links helped a lot. I'll give the LCS tool a try.

I see now that a crash dump is the way to go for debugging AOS issues.

Thanks again.

Was this reply helpful? Yes No