locked
Always getting "Unable to start ETW session MMA-ETW-Livecapture <guid> Host Name: Localhost. Error in application RRS feed

  • Question

  • Clicking "Start Local Trace"

    MMA is up to date, running as admin on Win10. What am I missing?

    thanks!

    Wednesday, March 9, 2016 1:36 PM

All replies

  • I'm not sure, but we can check somethings.

    1. If you go to an admin PowerShell prompt and type "get-neteventsession", does it return anything?

    2. Have you tried netsh in the past?  Did it work?

    3. Can you use PowerShell to capture with these commands and tell me if it's capture and ETL that displays network traffic when you load in Message Analyzer?

    New-NetEventSession  xxx

    Add-NetEventPacketCaptureProvider –SessionName xxx

    ping something, or create network traffic.

    Start-NetEventSession  xxx

    Stop-NetEventSession xxx

    Wednesday, March 9, 2016 7:04 PM
  • get-neteventsession says the cmdlet does not exist

    if i type new-neteventsession it prompts me for a param. if i enter anything, a number, xxx, etc i get

    PS C:\Windows\system32> New-NetEventSession xxx
    New-NetEventSession : A general error occurred that is not covered by a more specific error code.
    At line:1 char:1
    + New-NetEventSession xxx
    + ~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (MSFT_NetEventSession:root/StandardCimv2/MSFT_NetEventSession) [New-NetEventSession], Cim
        + FullyQualifiedErrorId : MI RESULT 1,New-NetEventSession

    Wednesday, March 9, 2016 9:24 PM
  • Hmm, that's strange, I've not seen that error before on Windows 10.  What does help New-NetEventSession show you? BTW, are you running as Admin? Another idea is to try update-help, to see if that changes the problem.

    Another option is to use "NetSh traces start capture=yes".  and see if that produces an ETL that can be read by Message Analyzer and has network traffic, then at least we know it works.

    Let me know what you find.

    Paul

    Thursday, March 10, 2016 8:49 PM
  • On my Machine with the same error i've got the following Outputs:

    PS C:\WINDOWS\system32> Get-NetEventSession

    Get-NetEventSession : Es ist ein allgemeiner Fehler aufgetreten, für den kein
    spezifischerer Fehlercode verfügbar ist.
    In Zeile:1 Zeichen:1
    + Get-NetEventSession
    + ~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (MSFT_NetEventSession:root/Standar
       dCimv2/MSFT_NetEventSession) [Get-NetEventSession], CimException
        + FullyQualifiedErrorId : MI RESULT 1,Get-NetEventSession

    It means that there is no specific error with no errorcode.

    The other cmdlet Returns simular Errors:

    PS C:\WINDOWS\system32> new-NetEventSession xxx
    Add-NetEventPacketCaptureProvider -SessionName xxx

    new-NetEventSession : Es ist ein allgemeiner Fehler aufgetreten, für den kein
    spezifischerer Fehlercode verfügbar ist.
    In Zeile:1 Zeichen:1
    + new-NetEventSession xxx
    + ~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (MSFT_NetEventSession:root/Standar
       dCimv2/MSFT_NetEventSession) [New-NetEventSession], CimException
        + FullyQualifiedErrorId : MI RESULT 1,New-NetEventSession
     
    Add-NetEventPacketCaptureProvider : Es ist ein allgemeiner Fehler aufgetreten,
    für den kein spezifischerer Fehlercode verfügbar ist.
    In Zeile:2 Zeichen:1
    + Add-NetEventPacketCaptureProvider -SessionName xxx
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (MSFT_NetEventPacketCaptureProvide
       r:root/StandardCi...CaptureProvider) [Add-NetEventPacketCaptureProvider],  
      CimException
        + FullyQualifiedErrorId : MI RESULT 1,Add-NetEventPacketCaptureProvider

    The Netsh Returns something like that, but i don' know it's good or not. But it does something:

    C:\WINDOWS\system32>netsh trace start capture=yes

    Ablaufverfolgungskonfiguration:
    -------------------------------------------------------------------
    Status:             Wird ausgeführt
    Ablaufverfolgungsdatei:         C:\Users\m\AppData\Local\Temp\NetTraces\NetTrace.etl
    Anfügen:             Aus
    Kreisförmig:           Ein
    Maximale Größe:           250 MB
    Bericht:             Aus

    Any further ideas?



    Monday, April 18, 2016 8:34 PM
  • Yes, it looks like netsh is working. Are you on Windows 10?  What does help net-eventsession return?
    Friday, April 22, 2016 9:14 PM