App-V 5 – Reporting and TargetInPackage

Hi all, Following on from my previous post about scripting and TargetInPackage, the inbuilt reporting functionality of the App-V Client is also interesting when a package has TargetInPackage set to False. To enable the reporting functionality the “ReportingEnabled” client configuration needs to be set to 1, so that the client collects launch information. Once…


App-V 5 – Scripting and TargetInPackage

Hi all, The following post with go into detail about why an App-V script doesn’t run when launching an application, its related to how the App-V Sequencer captures an application. The first thing to note is that what I’m sequencing is an HTA Application which customers use and deliver to their users. A description of…


App-V 5 – Virtual Service subsystem failure 2A-00000436

Hi all, An error I came across recently was the following error message that’s presented to the user after launching an application. App-V 5.1 Client – 0x84000D2A-0x00000436 / 0x84000D2A-00000436 If you look in the event log you will see the following message: Process 68 failed to start due to Virtual Services subsystem failure. Package ID {3AAC90AC-7517-496E-A137-60301CB41ADC}….


App-V 5 – Publishing Server Global Refresh Enabled

Hi all, Have you ever wondered how the App-V Client functions when adding a publishing server to the App-V client? This post should help you understand what happens behind the scenes and I need to be clear there is a difference between versions of the client and this is explained below. When you add a…


App-V 5 – Troubleshooting the Client using the Event Logs

Hi all, The App-V event log holds lots of great information but the challenge you my face is you have to jump between logs to figure out what actually happened on the client if errors occur. There are 3 default logs that you can use when troubleshooting, they are the Admin, Operational and Virtual Applications…


App-V 5 – Virtual Shell subsystem failure 2A-00000002

Hi all, I came across a really interesting error code recently and thought it was worth sharing why it occurs, the error message that’s presented to the user looks like this when launching an application. App-V 5.0 SP3 Client – 0x9B50172A-0x2 / 0x9B50172A-0x00000002 App-V 5.1 Client – 0x9B501A2A-0x2 / 0x9B501A2A-0x00000002 You can see that the…


App-V 5 – All Packages COM / Objects Check

Hi all, Following on from my post about how COM mode functionality actually works, I was asked if there is a way to check all package COM and Objects settings on an App-V Client? As I’m posting about it there is obviously a way to do this but you have to read multiple XML…


App-V 5.0 – ETW Tracing Automation [Update]

Hi all, I’ve had some feedback on a post that I did on VirtualWorld stating it took along time to convert the ETL output into a readable format so its time to share the updated script to address this. When you collect the trace you will see a lot of “SharedPerformance” entries as shown below. The…


App-V 5 – COM Mode Functionality

Hi all, Following on from my colleagues post about COM Mode it would be good to understand how COM Mode actually works when you deploy an App-V 5 package with COM Mode set to “Integrated” or “Isolated”. I’m going to be using an application called Microsoft MapPoint 2004 to show how this works on the client. The first…


App-V 5 – Service failed to complete requested operation – 06-00000011

Hi all, I’ve worked with a few customers and they were receiving the following error code when running the “Get-AppvClientPackage” PowerShell cmdlet. Get-AppvClientPackage : Application Virtualization Service failed to complete requested operation. Operation attempted: Get Packages. AppV Error Code: 0600000011. Error module: Catalog. Internal error detail: 86B09F0600000011. Please consult AppV Client Event Log for more details….