locked
ETW: Auto logger session not started after a hard reboot. RRS feed

  • Question

  • Hello,

    We are using ETW auto logger to start the trace session. When the file mode is EVENT_TRACE_FILE_MODE_APPEND in a regular reboot, session is started and new trace messages are appended to the existing trace log file.

    But in case of hard reboot, session is not started. Auto logger entry "Status" showing 0 which means session is started. Even by calling the StartTrace API with proper parameters session throwing invalid parameters exception (these are working in case of normal reboot). We are passing same value for append all the times (expected by append mode).

    Only way we can start the session is by removing corrupted etl file (new file is created by session). We can still read the data from the corrupted etl file. Apart from not able to append to that file all other operations like tracerpt is working fine.

    What is happening to the file in this hard reboot case? How we can use same file to append?

    Any suggestions are appreciated..



    Friday, August 10, 2012 12:06 PM