locked
location of log files for nap client RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    the nap help refers to log trace files available for the nap client. i have used napclcfg to enable tracing at the debug level and 'netsh nap show config' confirms this:

    Client tracing:
    ----------------------------------------------------
    State = Enabled
    Level = Verbose

    where do these log files reside? i can't find anything except the usual events in the event viewer.


    Sunday, December 24, 2006 10:54 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Is this the final Vista release?

    If not, you can find the trace file qagentrt.etl in %windir%\system32

    If yes, the tracing that you enabled will not generate trace files. You will have to use a workaround:

    1. Type:   logman start QAgentRt -p {b0278a28-76f1-4e15-b1df-14b209a12613} 0xFFFFFFFF 9 -o %systemroot%\tracing\nap\QAgentRt.etl -ets

    2.       run through the scenario

    3.  Type: logman stop QAgentRt -ets

    The trace file qagentrt.etl will be generated in %systemroot%\tracing\nap

    Note that these trace files are not human readable, you will need access to private symbol files to decode them.

    Thanks

    Ram

    Thursday, December 28, 2006 6:22 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    NAP logs reside under:

    %systemroot%\tracing\nap

    Thursday, December 28, 2006 1:16 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Is this the final Vista release?

    If not, you can find the trace file qagentrt.etl in %windir%\system32

    If yes, the tracing that you enabled will not generate trace files. You will have to use a workaround:

    1. Type:   logman start QAgentRt -p {b0278a28-76f1-4e15-b1df-14b209a12613} 0xFFFFFFFF 9 -o %systemroot%\tracing\nap\QAgentRt.etl -ets

    2.       run through the scenario

    3.  Type: logman stop QAgentRt -ets

    The trace file qagentrt.etl will be generated in %systemroot%\tracing\nap

    Note that these trace files are not human readable, you will need access to private symbol files to decode them.

    Thanks

    Ram

    Thursday, December 28, 2006 6:22 PM