Udostępnij za pośrednictwem

Troubleshooting App-V with log files

  • Artykuł

If you've ever found yourself having to troubleshoot some sort of software related issue then you know that being able to get a log file can be incredibly helpful.  With Microsoft Application Virtualization it's no different.  There are two primary logs that you'll probably end up working with:

1. Sftlog.txt
Description: The main log used for troubleshooting on the SoftGrid client.
Location and details: See https://technet.microsoft.com/en-us/library/cc817103.aspx.

The details on the various logging levels and how to implement them are documented in KB931803 - Log options for SoftGrid Client 4.x.

2. SFT-Server.log

Description: Stores messages from the SoftGrid Virtual Application Server.
Path: %ProgramFiles%\Softricity\SoftGrid Server\logs 

Note: In App-V 4.5 the directory is now called "Microsoft System Center App Virt Management Server\App Virt Management Server", not Softricity\SoftGrid Server. For more information see 930871.

The logging level for the Application Virtualization Management Server can be changed in the registry at:

HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\SOFTGRID\4.5\SERVER\SOFTGRID_LOG_LEVEL

The logging levels range in values from 1-5 as outlined below:

• 0: Transactions 
• 1: Fatal Errors 
• 2: Errors 
• 3: Warnings 
• 4: Informational 
• 5: Debug (Verbose) 

The default is 3:

image

When the logging level is changed for the Application Virtualization Management Server, a restart of the service is required to pick up the change. To do this follow the steps below:

1.    Click on START>RUN and type "Services.msc"
2.    Scroll down and select "Application Virtualization Management Server"
3.    In the column to the left, click on "Restart the service"

image

Once you restart the service you should be good to go.  You must restart the service for the new log level to take effect.   One last thing I'll also mention is to be sure you set the value back to it's default once you're done troubleshooting.  Some of these options can generate a ton of output and you don't want that overhead weighing you down unless absolutely necessary.

J.C. Hornbeck | Manageability Knowledge Engineer

Comments

  • Anonymous
    January 30, 2009
    Hi all, This is my first comment here and therefore I hope it is appropriate to post it as I am. I am involved on a large App-V design and implementation that forms part of a managed solution. With specific regard to logs and troubleshooting I URGENTLY need to have a list of ALL possible error codes and their associated messages that get logged in sft-server.log, sftlog.txt and in the Event log. This is so the largely automated solution monitoring capability can have a set of rules on how to react if any particular error happens. I know I can find answers to specific errors on the internet but is there a location that lists all possible errors? Any reples are most gratefully received. Regards, Jonathan

  • Anonymous
    March 24, 2009
    The first thing you’ll probably want to do in preparation for your callback is gather up any relevant

  • Anonymous
    April 10, 2009
    Now I have been chatting with Aaron Parker about doing this blog entry for weeks and just never found

  • Anonymous
    September 23, 2011
    hai all.i have one doubt.How to create log file in APP-V.How to troubleshoot by using log.

  • Anonymous
    November 24, 2011
    Error codes for all possible errors are available in the tool called "A failure to launch" which is found here www.tmurgent.com/Tools.aspx Great site for app-v resorces .