locked
App-V debug logs in event viewer RRS feed

  • Question

  • While I understand how to enable the debug logs in event viewer for the App-V client and that they have been consolidated, what I need to know is which one needs to be enabled for catching VFS issues?

    Thursday, June 14, 2018 1:00 PM

All replies

  • if this is appv 5.1, the service log in event viewer is as below:

    if it is windows 10 AppV, the most service log has been redirected to telemetory channel, but can be captured by the following ETW GUID

    271aebf7-e83b-580f-7525-5e9563fe161a

    using Microsoft Message Analyzer can help on the capturing:

    https://www.microsoft.com/en-us/download/details.aspx?id=44226


    Thursday, June 14, 2018 4:03 PM
  • Thank you! I will give this a try and follow up.
    Thursday, June 14, 2018 4:36 PM
  • The App-V debug event logs are not likely to help diagnose a VFS issue.  Procmon is likely to be a better choice.

    Tim


    App-V MVP & CTP Fellow. Author of AppV books: PowerShell with App-V 5, The Application Book, & Window Caching (http://www.tmurgent.com/Books)

    Friday, June 15, 2018 4:45 PM
    Moderator
  • Hi Tim,

    Unfortunately, I am not any good with procmon.

    Wednesday, June 20, 2018 6:49 PM
  • This video might help:

    https://www.brianmadden.com/video/BriForum-2014-London-Tim-Mangan-Patrick-Mangan-In-Depth-Debugging-in-App-V 


    App-V MVP & CTP Fellow. Author of AppV books: PowerShell with App-V 5, The Application Book, & Window Caching (http://www.tmurgent.com/Books)

    Wednesday, June 20, 2018 7:24 PM
    Moderator
  • if this is appv 5.1, the service log in event viewer is as below:

    if it is windows 10 AppV, the most service log has been redirected to telemetory channel, but can be captured by the following ETW GUID

    271aebf7-e83b-580f-7525-5e9563fe161a

    using Microsoft Message Analyzer can help on the capturing:

    https://www.microsoft.com/en-us/download/details.aspx?id=44226


    Sorry to derail, but can you send any links you have on the change, and /or more info on how to read the logs now?  I noticed the logs weren't being generated the same under Win 10 but this is the first time I've heard this.  I haven't used the message analyzer, but this seems a lot harder.  Thanks! 
    Tuesday, July 10, 2018 8:13 PM
  • Yes, this is the new change in windows 10 since 1709 if my memory serves me correctly. A lot of verbose debugging logs has been moved to telemetry channel - 271aebf7-e83b-580f-7525-5e9563fe161a and no show from regular event viewer logs. You can use the following command to get all the logs in win10:

    logman /create Trace AppV -p {9CC69D1C-7917-4ACD-8066-6BF8B63E551B} -o c:\Temp\AppVAll.etl
    logman /update Trace AppV -p {E4F68870-5AE8-4E5B-9CE7-CA9ED75B0245}
    logman /update Trace AppV -p {271aebf7-e83b-580f-7525-5e9563fe161a}
    
    

    Wednesday, July 11, 2018 9:18 PM
  • These are not pre-created but left disabled?  Very odd.

    App-V MVP & CTP Fellow. Author of AppV books: PowerShell with App-V 5, The Application Book, & Window Caching (http://www.tmurgent.com/Books)

    Wednesday, July 11, 2018 9:39 PM
    Moderator