Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
When Things go Wrong How to effectively and Efficiently Troubleshoot Application Virtualization (App-V) Deployments
Justin Zarb Senior Premier Field Engineer Microsoft Corporation http://appvguy.com http://blogs.technet.com/virtualworld @justinzarb
Agenda
App-V Management Server troubleshooting
App-V Server architecture Troubleshooting scenarios
Deployment Application Provisioning Care and feeding
Client troubleshooting
App-V Client architecture Troubleshooting scenarios
Deployment Publishing virtual applications to users Delivering virtual applications to users Ongoing use of virtual applications (runtime)
4
ASP.NET (and dependencies) Windows Authentication IIS Management scripts and tools
Deployment
Considerations for setup of:
Secure Server (RTSPS)
Request and install certificate Make sure Management Server service account has access to private key
SQL Server
Confirm your IT admin has admin rights to the database (required by the installer) If no admin rights to DB - Creating a New Application Virtualization 4.5 Database Using SQL Scripting
Deployment
Configure Windows Firewall
If using RTSPS, allow connection port 322 If using RTSP, allow connection to program files
sghwdsptr.exe, sghwsvr.exe Configuring port 554 not sufficient
Deployment
Set up for streaming virtual apps or .osd
Launch IIS Manager
Configure MIME type for .osd , .sft In Default Web site, add Virtual Directory, set physical path to path of shared content directory
Advantages
Streaming easily integrates with existing IIS infrastructure Can stream to remote clients in the cloud Better performance in high latency, low bandwidth networks
Limitation
Clients need to be configured to point to new .sft, perform publishing refresh to get new package versions
Deployment
Verify App-V Management Server service is started
10
Deployment
Additional check for Management Service
URL check:
Launch URL http://webserver_name/SoftGridManagement/Authorization.r em?wsdl You get System.NullreferenceException: Object reference not set to an instance of an object.
Deployment Issue #1
Issue: When installing Management Service, Error 25120 unable to create the required IIS virtual directory
12
Deployment Issue #2
Issue: Error 25122 when installing Management Service Root Cause: Attempted to install Management Service on a machine where Default web site (in IIS) was renamed
Deployment Issue #3
Issue: Error connecting to Management Service in management console Error code: 0000C824 Investigation: Error message to user, error message in install log
14
Agenda
App-V Management Server troubleshooting
App-V Server architecture Troubleshooting scenarios
Deployment Application Provisioning Care and feeding
Client troubleshooting
App-V Client architecture Troubleshooting scenarios
Deployment Publishing virtual applications to users Delivering virtual applications to users Ongoing use of virtual applications (runtime)
15
Verify HREF in .osd points to .sft in package folder (unless ASR/Policy/envt. variable is set on client)
16
Application Provisioning
Ensure at least one app is imported on the server
17
Root cause(s): Content folder is not shared, OS Tag mismatch, user not added to correct group entitlement
Resolution(s): Share content folder, add OS to OSD, add user to correct group
18
20
21
Root cause: SQL Server service stopped Resolution: Restart the SQL Server service and restart the management server service
22
23
3. Edit database info in Default Server Group properties Logging tab->Edit SQL Database 4. Restart the management server service
25
Agenda
Management server troubleshooting
App-V server architecture Troubleshooting scenarios
Deployment Adding package, importing virtual applications Care and feeding
Client troubleshooting
App-V client architecture Troubleshooting scenarios
Deployment Publishing virtual applications to user Delivering virtual applications to user Ongoing use of virtual applications (runtime)
27
System-Guard
File System
Transport
28
Client Logging
MSI Installation Log
Similar to App-V Server Installation
29
30
Deployment
For successful install:
Find string 1603 or value 3 should give no results
Deployment Issue #1
Issue: Error 25010. A prerequisite for installation is missing. Installation cannot continue
http://blogs.technet.com/softgrid/archive/2009/02/17/a-story-of-apublishing-refresh-request.aspx
Publishing Issue #1
Issue: Publishing refresh fails
Investigation:
Verify server is accessible (ping it) Telnet to server If still no issue found, RDP to the server box and verify Management Server service is running
Root cause: Management Server service has stopped Resolution: Restart the service and do publishing refresh again
34
22 characters 4605F5-19D0810A-10000004
Characters:
1-6 7-12 13-14 15-22 Version and build File and line info where error occurred Error category code Problem code (error text in sfterr.xml)
Note: Characters 1-12 vary with each build, but 13-22 are constant across builds.
35
4605F5-19D0810A-10000004
Minimum of last 10 characters required for root cause analysis
460 5F5 19D081 0A 10000004
00 01 02 03 04 05 06 07 08 09 UNK FEC SVR LST COR XML USR FSL FSI FSD Unknown Front-End Component Server Listener Client Core XML Library User Library Core FS Interface FS Interface FS Driver
Release number Hex for Build number 1525 File ID and line where error occurred Error category: Net Transport Agent Problem ID: info from sfterr.xml
0D 0E 0F 10 11 12 13 14 15* 16* SGD INT VSM SEQ SYN DCC RPC PFM DDE MDE SystemGuard Driver Client Interface Visual Service Manager Sequencer Synchronization Manager Desktop Config Controller Remote Procedure Call Platform Library DDE Launcher Minidump Exception
0A
0B 0C
NTA
CDC SGL
17*
18* 19-1F
MAPI
SCR
MAPI
Script Reserved
Delivery Issue #1
Issue: App launch fails with error 4604EE819D07F2A-0000274D Investigation: Review sftnta.txt Root Cause:
Cannot contact server Management Server Service Stopped
Resolution:
Restart Management Server Service
38
Delivery Issue #2
Issue: Application launch fails with error 4604EE81690140A-20000194 Investigation: Check sftlog.txt (client log), sftserver.log, Management Server Console
Root Cause(s):
o The .sft file path or the .sft file name is invalid. o App no longer exists but shortcut still present o The Provider Policy does not exist
Resolution:
o Set the correct path to SFT file o Delete the shortcut o Set correct Provider Policy in .osd
39
42
Tools
App-V Application Listing Tool App-V SFT Parser Tool App-V Client Log Parser Utility App-V Cache Resizing Tool App-V Dynamic Suite Composition Tool
Troubleshooting
App-V Client Log Files Client
Client Installation Log, in %temp% starts with msi SFTLOG.TXT, log levels
Critical Error Warning Information Verbose
46
47
48
49
ETL Tracing
All Filesystem Information will be logged here %Allusersprofile%\documents\Softgrid Client There are two Files
SFTFS.ETL SFTFS.ETL.OLD
50
Client Dumps
When the App-V Client crashes , it write a Dump File Location: %Alluserprofile%\Documents\Softgrid Client\Dumps Can be configured via Registry
51
Change logging
In the Start Parameter box for the Service add the d switch with the Loglevel you want to use
0: Transactions 1: Fatal Errors
2: Errors
3: Warnings 4: Informational
5: Debug (Verbose) 6: Trace
52
53
SFTCallBack.txt
Logs all Process starts and stops as seen by Systemguard
54
SFTrpc.txt
Created by SFTRPC.EXE Contains Process starup and shutdown Verbose diag Info about each monitored shortcut
55
VAppLauncher.log
Tracks virtual application launch by user.
56
Examples:
01 App-VClientLogParser.exe /P:c:\logs /O:c:\temp\errors.txt /LF /N:5 02 App-VClientLogParser /P:C:\logs /N:5 /M:2 /R /O:C:\results\error.txt
57
Pivot Tables
With the Parsed Log Files you can create Pivot Tables Examples:
58
Virtual Services
Three ways to disable virtual Services
On the Sequencer, Tools Options uncheck Allow Virtualization of Service Machine Wide (debugging only) set DisableVirtualServices dword 00000042 under HKLM\...Softgrid\4.5\Systemguard\Overrides Per Virtual Environment add the following Tag to the OSD:
<VIRTUALENV> <POLICIES> <VIRTUAL_SERVICES_DISABLED>TRUE</VIRTUAL_SERVICES_DISABLED> </POLICIES>
59
60
61
Virtual Registry
Two Ways to disable it
Machine Wide set DisableVREG dword to 1 under HKLM\...Softgrid\4.5\Systemguard\Overrides OSD
<POLICIES> <VIRTUAL_REGISTRY_DISABLED>TRUE </VIRTUAL_REGISTRY_DISABLED> </POLICIES>
62
Local Interaction
Set in the OSD
<POLICIES> <LOCAL_INTERACTION_ALLOWED>TRUE</LOCAL_INTERACTION_ALLOWED> </POLICIES>
Places COM Objects out of the Bubble into the OS Its active for the whole Package You see a not in the SFTLDR.log if its enabled
63
Additional Resources
66
Virtualworld Blog
http://blogs.technet.com/virtualworld/
67
68
Whitepapers
http://technet.microsoft.com/enus/appvirtualization/cc843994.aspx
69
Appendix
Log Files:
Which to use
Where to find
When to use How to enable and change log level
70
How:
Generated by default (error logging only) For debugging, enable MSI logging (more MSI*.txt)
71
Log level range is 0-5 for Transactions, Fatal Errors, Errors, Warnings, Informational, and Verbose Restart the Management Server service for the new log level to take effect Reset to default after troubleshooting to avoid overhead
72
73
Information on product version, name, and install outcome at very end of log
74
How:
Default log level: informational Log location can be configured in registry Log level can be reset in Client MMC
75
Deployment
Default MSI log v/s log with MSI logging enabled
76
Event log
77
Where:
Not generated by default, need to enable Generated in client install path Log file location cannot be changed
When: For errors/messages after launch starts and before it completes 100%
78
Restart the Application Virtualization Client Service (sftlist) for changes (enable/update) to take effect
79
Deployment Issue #4
Issue: Error connecting to Management Service in management console Error code: 0000C800 and 0000C824 Investigation: Error message to user
Root Cause: Management Service we are attempting to connect to is not installed on the host machine; more info on root causes for C800 error at http://go.microsoft.com/fwlink/?LinkId=114648 Resolution: Install management service on host machine
81
82
83
If you add a package first, then you also need to import apps If you import apps first, then package is added automatically
84
Resolution: Ensure .osd path set in server system options correctly represents the location of .osd files
86
Root Cause: Server file cache may have exceeded the maximum memory set Resolution: Increase the Maximum Memory Allocation, restart service
87
Note: The Microsoft application error reporting pre-req can be found in Support\watson directory of media.
88
89
Delivery Issue #4
Issue: Unloading a package does not reduce the used cache size Investigation (example):
Current cache size (reserved cache size in client) 5 GB Unload a package 3 GB in size Check Reserved cache size same as 5 GB, will not reduce Load a package 1 GB in size Check Reserved cache size same as 5 GB, will not increase
Root Cause:
Cache size cannot be reduced if you unload package, available cache can be reused by other virtual packages but it cannot be reclaimed by the client
Delivery Issue #5
Issue: Error when changing (reducing) maximum cache size
91
Delivery Issue #6
Issue: Could not connect to stream URL error to user Investigation: Error message in sftlog need to update log level to verbose
The package could not be locked in cache due to lack of unallocated space Could not set lock status to TRUE, could not load app Not enough space in the Application Virtualization cache Report the following error code to your System Administrator error code 4504B4-16D10E0A-0000E029
Root cause:
Could not load app, as client cache is full Incorrect error message to user, correct error code in sftlog
Resolution:
Remove apps from cache unload in client MMC Increase cache size properties of 'Application Virtualization in client MMC
92
Delivery Issue #7
Issue: Cannot find/see available space in App-V client cache Resolution: 2 options:
1. (Max size Reserved Cache size) 2. In Performance Monitor tool, add performance counter App Virt Client Cache
Create new data collector set Add perf counters Select log format comma separated
93
Resolution: For an app that fails to launch, ensure Package URL and Source are accurate in app properties
Resources
www.msteched.com/Australia
Sessions On-Demand & Community
www.microsoft.com/australia/learning
Microsoft Certification & Training Resources
http:// technet.microsoft.com/en-au
Resources for IT Professionals
http://msdn.microsoft.com/en-au
95
2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.