Unfortunately that will not happen any time soon but I though I would make readers aware that some of my content has been translated by fellow App-V MVP Junxian (Tommy) Huang. Tommy was kind enough to select some of my content for translation so that it could reach a wider audience. For those of you that don’t know where Tommy blogs here is a list of links for you.
http://blogs.itecn.net/blogs/virtualtom
http://virtualtom.blog.51cto.com
http://bbs.winos.cn/thread-90753-1-1.html
Enjoy!
I a few weeks ago I was putting in a new SCCM environment and we decided to try out the App-V 4.6 client since it was released that week. What we didn't expect was an issue deploying our first virtual application to our test PC. It just wouldn't deliver the virtual application so we had to look into the first logical spot for this configuration, the SCCM client logs. What we were trying to see is if SCCM was passing the virtual application over to the App-V client so that the App-V client can import it into the client cache, configure shortcuts, etc... My first stop was the SCCM client log usually associated with application delivery known as the execmgr.log. We opened the log and we thought we might have found the issue but the log suggested something we didn't expect.
Requesting content from CAS for package INI00003 version 1 execmgr 14/03/2010 8:07:33 PM 3988 (0x0F94)
Policy arrived for parent package INI00003 program [Virtual application] execmgr 14/03/2010 8:07:33 PM 4088 (0x0FF8)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramOfferReceivedEvent
{
AdvertisementId = "INI20000";
ClientID = "GUID:7A4870CF-6F16-4E5C-9762-803620B7B3E8";
DateTime = "20100315020733.678000+000";
MachineName = "WIN7X32ENT-SEQ";
ProcessID = 280;
SiteCode = "INI";
ThreadID = 4088;
};
execmgr 14/03/2010 8:07:33 PM 4088 (0x0FF8)
Successfully created a content request handle {8FEDE91E-A80B-4506-BD8A-9A48E53C48F4} for the package INI00003 version 1 execmgr 14/03/2010 8:07:35 PM 3988 (0x0F94)
Program [Virtual application] change to state STATE_ADVANCED_DOWNLOAD content in progress execmgr 14/03/2010 8:07:35 PM 3988 (0x0F94)
Execution Request for package INI00003 program [Virtual application] state change from NotExist to AdvancedDownload execmgr 14/03/2010 8:07:35 PM 3988 (0x0F94)
Mandatory execution requested for program [Virtual application] and advertisement INI20000 execmgr 14/03/2010 8:07:35 PM 236 (0x00EC)
Creating mandatory request for advert INI20000, program [Virtual application], package INI00003 execmgr 14/03/2010 8:07:35 PM 236 (0x00EC)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistWaitingContentEvent
{
AdvertisementId = "INI20000";
ClientID = "GUID:7A4870CF-6F16-4E5C-9762-803620B7B3E8";
DateTime = "20100315020735.381000+000";
MachineName = "WIN7X32ENT-SEQ";
PackageName = "INI00003";
PackageVersion = "1";
ProcessID = 280;
ProgramName = "[Virtual application]";
SiteCode = "INI";
ThreadID = 236;
};
execmgr 14/03/2010 8:07:35 PM 236 (0x00EC)
Successfully raised SoftDistWaitingContentEvent event for program [Virtual application] execmgr 14/03/2010 8:07:35 PM 236 (0x00EC)
Execution Request for package INI00003 program [Virtual application] state change from WaitingDependency to WaitingContent execmgr 14/03/2010 8:07:35 PM 236 (0x00EC)
Content is available for program [Virtual application]. execmgr 14/03/2010 8:07:37 PM 2772 (0x0AD4)
CExecutionRequest::Service Windows Manager has allowed us to run. execmgr 14/03/2010 8:07:37 PM 2772 (0x0AD4)
Executing program {4E6A9B91-8BCA-4B06-A720-7485CE71BB9D} in Admin context execmgr 14/03/2010 8:07:37 PM 2772 (0x0AD4)
Execution Request for package INI00003 program [Virtual application] state change from WaitingContent to NotifyExecution execmgr 14/03/2010 8:07:37 PM 2772 (0x0AD4)
Execution Manager timer has been fired. execmgr 14/03/2010 8:07:37 PM 236 (0x00EC)
Checking content location C:\Windows\system32\CCM\Cache\INI00003.1.System for use execmgr 14/03/2010 8:07:37 PM 2772 (0x0AD4)
Successfully selected content location C:\Windows\system32\CCM\Cache\INI00003.1.System execmgr 14/03/2010 8:07:37 PM 2772 (0x0AD4)
Executing program as a virtual application registration. execmgr 14/03/2010 8:07:37 PM 2772 (0x0AD4)
SCCM package version number : 1. execmgr 14/03/2010 8:07:37 PM 2772 (0x0AD4)
CVirtualAppExecution::ExecuteProgram - The virtual application package was not registered because the SoftGrid client is not installed. execmgr 14/03/2010 8:07:37 PM 2772 (0x0AD4)
EnterRsRuningState failed to run script {4E6A9B91-8BCA-4B06-A720-7485CE71BB9D} 0x80008281 execmgr 14/03/2010 8:07:37 PM 2772 (0x0AD4)
Fatal error 0x80008281 enountered for program [Virtual application]. This program will not retry. execmgr 14/03/2010 8:07:37 PM 2772 (0x0AD4)
We didn't expect to see the message "The virtual application package was not registered because the SoftGrid client is not installed." in the execmgr.log because we knew the App-V 4.6 client was installed. Just for fun we opened another SCCM client log file that involves the installation of virtual applications the VirtualApp.log.
Could not open the registry key SOFTWARE\Microsoft\SoftGrid\4.5\Client\Configuration. (0x80070002) VAppRegistration 14/03/2010 7:44:01 PM 3476 (0x0D94)
The VirtAppMgmt client was not found on this system or is an unsupported version. VAppRegistration 14/03/2010 7:44:01 PM 3476 (0x0D94)
CVAppRegistration::ConfigureVappClient() failed. (0x80008281) VAppRegistration 14/03/2010 7:44:01 PM 3476 (0x0D94)
Registering the virtual application package [INI00003] with the AppVirtMgmt client. VAppRegistration 14/03/2010 8:07:37 PM 2772 (0x0AD4)
Loading package properties from the manifest file: C:\Windows\system32\CCM\Cache\INI00003.1.System\WinRAR-V3.91-WinRAR.001_manifest.xml. VAppRegistration 14/03/2010 8:07:37 PM 2772 (0x0AD4)
The installed AppVirtMgmt version [4.6] cannot be used with this version of SCCM. VAppRegistration 14/03/2010 8:07:37 PM 2772 (0x0AD4)
The VirtAppMgmt client was not found on this system or is an unsupported version. VAppRegistration 14/03/2010 8:07:37 PM 2772 (0x0AD4)
The package cannot be registered. The Application Virtualization Management client is not ready. VAppRegistration 14/03/2010 8:07:37 PM 2772 (0x0AD4)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of CLIMSG_VIRTUALAPP_ERROR_PACKAGEADD_FAILURE
{
AdvertisementId = "INI20000";
ClientID = "GUID:7A4870CF-6F16-4E5C-9762-803620B7B3E8";
DateTime = "20100315020737.850000+000";
ErrorCode = "";
ErrorMessage = "The Application Virtualization Management client is not installed or is an unsupported version.";
MachineName = "WIN7X32ENT-SEQ";
PackageID = "INI00003";
ProcessID = 280;
SiteCode = "INI";
ThreadID = 2772;
VirtualAppPackageGUID = "{4E6A9B91-8BCA-4B06-A720-7485CE71BB9D}";
VirtualAppPackageName = "WinRAR-V3.91-WinRAR.001";
};
VAppRegistration 14/03/2010 8:07:37 PM 2772 (0x0AD4)
Raised ADD PACKAGE Registration Failure event for Ad: INI20000, PackageID: INI00003, Name: WinRAR-V3.91-WinRAR.001, PackageGUID: {4E6A9B91-8BCA-4B06-A720-7485CE71BB9D} VAppRegistration 14/03/2010 8:07:37 PM 2772 (0x0AD4)
The key message from the VirtualApp.log was the "The installed AppVirtMgmt version [4.6] cannot be used with this version of SCCM.", obviously we needed to upgrade our SCCM infrastructure from version 2007 R2 to 2007 R2 SP2! Aside from not doing our homework when installing App-V 4.6 this was a good exercise to understand the SCCM client logs involved with delivering an App-V application. This however is not the complete picture when looking at all the logs involved with App-V application delivery when it is integrated with SCCM. The client application event log and another log file called sftlog.txt can be used to specifically look at App-V client events. I hope that this at least gives you a basic picture when trying to troubleshoot your App-V application delivery in a SCCM integrated configuration.