Debugging App-V 5.0 Error Code - 0x45500D27-0x80190191

November 21, 2013, 7:58 am

≫ Next: How to Automate the Creation of App-V 5.0 Debug Command Prompts

≪ Previous: Now Available: Hotfix Package 3 for Microsoft Application Virtualization 4.6 Service Pack 2

Hi all,

We’ve seen this error a few times in App-V 5.0 deployments and thought it was time to show you why this error can occur.

Problem

This error code occurs when completing a global refresh on the client, but interestingly a user sync works correctly.

Debug

Looking into why it occurs we need to understand what the error code actually means. The Gladiator@MSFT has discussed this on his blog - http://blogs.technet.com/b/gladiatormsft/archive/2013/11/13/app-v-on-operational-troubleshooting-of-the-v5-client.aspx

If we convert the error to the short code we are presented with:

27-80190191

So that means its a publishing error with the hex code 7 and the 2 states that its a windows error. The error description from Powershell provides this also.

Hex Code	Category	Where you might further Info
07	Publishing	Client-Publishing Log, Client-PackageConfig Log, or FileSystemmetadataLibrary Log

So if we decode the 0x80190191 HRESULT, the return description is:

HTTP_STATUS_DENIED
Unauthorized (401).

To confirm this on the App-V Publishing Server we enabled failed request logging, an unauthorized 401.2 error is returned which states an Access denied to the server.

“Typically, HTTP 401.1 and 401.2 errors are encountered when the authentication process fails in some way — either because the mechanism that IIS used to obtain the credentials has failed or because the credentials themselves are invalid. This is an important distinction that is a critical to the problem isolation process. These errors tell you that, before performing any other function, IIS has failed to authenticate the user.”

http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/8feeaa51-c634-4de3-bfdc-e922d195a45e.mspx?mfr=true

Note: The following article is a great reference to using failed request logging - http://www.iis.net/learn/troubleshoot/using-failed-request-tracing/troubleshooting-failed-requests-using-tracing-in-iis

Resolution

The resolution for this case was due to user permissions. If you check the “Users” group on the publishing server:

The member of “Users” should be similar to the below:

In this case the “NT AUTHORITY\Authenticated Users” had been removed which caused the 0x45500D27-0x80190191 for a global refresh.

Fix

Ensure that the “NT AUTHORITY\Authenticated Users” group is a member of the local users group otherwise the refresh will fail.

Conclusion

This may not be the cause in your environment but worth checking if you start receiving this error on a global refresh.

Hope this helps.

David Falkus | Premier Field Engineer | Application Virtualization

↧

How to Automate the Creation of App-V 5.0 Debug Command Prompts

November 21, 2013, 9:21 am

≫ Next: How to Automate the creation of App-V 5.0 Connection Group Debug Commands

≪ Previous: Debugging App-V 5.0 Error Code - 0x45500D27-0x80190191

Hi all,

I’ve been meaning to write this for a while now and finally have found some time to write it.

Steve Thomas has written a great blog post that describes the new debug mode with the /appvve command shell switch but as described its not a easy process to create those commands.

http://blogs.technet.com/b/gladiatormsft/archive/2013/04/24/app-v-5-0-launching-native-local-processes-within-the-virtual-environment.aspx

Firstly you need to get the package you require using get-appvclientpackage.

If you have a long list then you need to filter that list by using something like:

get-appvclientpackage RDCMan.001

Now we have the packageID and VersionID we then need to create the command, I’ve been using notepad to create mine.

But I have 38 packages on my machine alone, I don’t want to do this 38 times…..

You may have guessed…… POWERSHELL to the rescue.

The first thing we need to do is create a directory to create the debug command prompts in, so the snippet below is creating that directory on my desktop.

# Directory to create App-V Debug shortcuts
$Directory = "c:\users\davidfa\Desktop\AppVDebugCMDs"

# Creating Directory Folder
New-Item -ItemType directory -Path $Directory

Now we have the folder we need to create the debug command prompts and what were going to do is create shortcuts.

The snippet below is simply filtering for RDCMan.001 using the Get-AppVClientPackage, its then creating variables for different components required for the debug command prompt.

# Getting all client packages registered in the Client Catalog
$Package = Get-AppVClientPackage RDCMan.001

# Variables
$PName = $Package.Name
$PI = [string]$Package.PackageID
$VI = [string]$Package.VersionID
$PD = $PI + "_" + $VI

Now we have everything to create the shortcut. The following code creates the shortcut in the directory, it then specifies the TargetPath and WorkingDirectory and finally creates and saves the shortcut. (Note: These can be customized to whatever path you wish)

$WshShell = New-Object -comObject WScript.Shell
$Shortcut = $WshShell.CreateShortcut("$Directory\$PName DebugCMD.lnk")
$Shortcut.TargetPath = "c:\windows\system32\cmd.exe"
$Shortcut.WorkingDirectory = "C:\windows\System32"
$Shortcut.Arguments = "/appvve:$PD"
$Shortcut.Save()

Once complete and ran in Powershell the debug command prompt is created and ready to use.

So that's great a single debug command has been created but we haven’t thought about having multiple versions of packages or multiple packages. Heres the answer…..

# Directory to create App-V Debug shortcuts
$Directory = "c:\users\davidfa\Desktop\AppVDebugCMDs"

# Creating Directory Folder
New-Item -ItemType directory -Path $Directory

# Getting all client packages registered in the Client Catalog
$Packages = Get-AppVClientPackage -all

# Looping through each Package and creating a cmd shortcut

foreach($entry in $Packages){

$PName = $entry.Name
$PI = [string]$entry.PackageID
$VI = [string]$entry.VersionID
$Ver = [string]$entry.Version
$PD = $PI + "_" + $VI

$WshShell = New-Object -comObject WScript.Shell
$Shortcut = $WshShell.CreateShortcut("$Directory\$PName $Ver DebugCMD.lnk")
$Shortcut.TargetPath = "c:\windows\system32\cmd.exe"
$Shortcut.WorkingDirectory = "C:\windows\System32"
$Shortcut.Arguments = "/appvve:$PD"
$Shortcut.Save()

}

And there we go, 38 package debug shortcuts created, with the version of the package specified in the name automatically.

Disclaimer

The sample scripts are not supported under any Microsoft standard support program or service. The sample scripts are provided AS IS without warranty of any kind. Microsoft further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample scripts and documentation remains with you. In no event shall Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample scripts or documentation, even if Microsoft has been advised of the possibility of such damages.

Conclusion

A simple way to automate the creation of your debug command prompts.

Enjoy and hope it helps.

David Falkus | Premier Field Engineer | Application Virtualization

↧

How to Automate the creation of App-V 5.0 Connection Group Debug Commands

November 21, 2013, 12:59 pm

≫ Next: App-V 5.0 R2 and UE-V 2.0 are now available

≪ Previous: How to Automate the Creation of App-V 5.0 Debug Command Prompts

Hi all,

Following on from http://blogs.technet.com/b/virtualworld/archive/2013/11/21/how-to-automate-the-creation-of-app-v-5-0-debug-command-prompts.aspx post, how do we automate the creation of connection group debug commands????

Firstly you need to get the connection groups you require using Get-AppvClientConnectionGroup.

The first thing we need to do is create a directory to create the debug command prompts in, so the snippet below is creating that directory on my desktop.

# Directory to create App-V Debug shortcuts
$Directory = "c:\users\davidfa\Desktop\AppV_Debug_Cmds_CG"

# Creating Directory Folder
New-Item -ItemType directory -Path $Directory

Now we have the folder we need to create the debug command prompts and what were going to do is create shortcuts.

And here it is single script that creates all connection groups debug command prompts which are registered on the machine. (Note: I’ve used the –all switch which will get all connection groups registered whether they are enabled or not)

# Directory to create App-V Debug shortcuts
$Directory = "c:\users\davidfa\Desktop\AppV_Debug_Cmds_CG"

# Creating Directory Folder
New-Item -ItemType directory -Path $Directory

$Packages = Get-AppVClientConnectionGroup -all

foreach($entry in $Packages){

$PacName = $entry.Name
$Ver = $entry.version
$PName = $PacName
$PI = [string]$entry.GroupID
$VI = [string]$entry.VersionID
$PD = $PI + "_" + $VI

}

And there we go, connection group shortcuts created and ready to use.

Disclaimer

Conclusion

A simple way to automate the creation of your connection group debug command prompts.

Enjoy and hope it helps.

David Falkus | Premier Field Engineer | Application Virtualization

↧

App-V 5.0 R2 and UE-V 2.0 are now available

December 2, 2013, 3:51 pm

≫ Next: Hotfix Package 2 for Microsoft Application Virtualization 5.0 Service Pack 1 now available

≪ Previous: How to Automate the creation of App-V 5.0 Connection Group Debug Commands

We are excited to announce the broad availability of Microsoft Desktop Optimization Pack (MDOP) 2013 R2 for download . MDOP is a suite of virtualization, management and security technologies available as a subscription for Software Assurance customers...(read more)

↧

Hotfix Package 2 for Microsoft Application Virtualization 5.0 Service Pack 1 now available

December 5, 2013, 11:57 am

≫ Next: Important notes regarding the App-V 5.0 SP2 update

≪ Previous: App-V 5.0 R2 and UE-V 2.0 are now available

This Knowledge Base article describes a hotfix package that contains the latest hotfixes for Microsoft Application Virtualization 5.0 (App-V 5.0) Service Pack 1 (SP1). This hotfix package is applicable only to the server that is running App-V 5.0 SP1...(read more)

↧

Important notes regarding the App-V 5.0 SP2 update

December 5, 2013, 1:14 pm

≫ Next: More details on some interesting updates we made to App-V 5.0 SP2

≪ Previous: Hotfix Package 2 for Microsoft Application Virtualization 5.0 Service Pack 1 now available

Please be aware that Microsoft Application Virtualization 5.0 Service Pack 2 (App-V 5.0 SP2) does not include a new version of the App-V Server. This means that currently the most recent version of the App-V 5.0 Server component is App-V 5.0 SP1. In addition...(read more)

↧

More details on some interesting updates we made to App-V 5.0 SP2

December 10, 2013, 1:06 pm

≫ Next: KB: How to deploy and manage Office 2013 on App-V 5.0

≪ Previous: Important notes regarding the App-V 5.0 SP2 update

Microsoft’s Ben Hunter has a great new post on some of updates we made to App-V 5.0 SP2: With the release of MDOP 2013 R2 on Dec 2 nd 2013, I would now like to provide you with more details on some interesting updates we have made to App-V 5.0 SP2 as...(read more)

↧

KB: How to deploy and manage Office 2013 on App-V 5.0

December 11, 2013, 12:44 pm

≫ Next: Hotfix Package 4 for Microsoft Application Virtualization 4.6 Service Pack 2 is now available

≪ Previous: More details on some interesting updates we made to App-V 5.0 SP2

This article describes the supported scenarios for various versions of Microsoft Office and Microsoft Application Virtualization (App-V). The following product versions are included in this article: - Microsoft App-V 5.0 Service Pack 2 (SP2...(read more)

↧

Hotfix Package 4 for Microsoft Application Virtualization 4.6 Service Pack 2 is now available

December 12, 2013, 9:16 am

≫ Next: Hotfix Package 3 for Microsoft Application Virtualization 5.0 SP1 now available

≪ Previous: KB: How to deploy and manage Office 2013 on App-V 5.0

Hotfix Package 4 for Microsoft Application Virtualization 4.6 Service Pack 2 is now available for download. It contains the latest hotfixes for Microsoft Application Virtualization 4.6 Service Pack 2 (App-V 4.6 SP2). To see what’s fixed and get a download...(read more)

↧

Hotfix Package 3 for Microsoft Application Virtualization 5.0 SP1 now available

December 16, 2013, 10:47 am

≫ Next: KB: Current list of App-V 5.0 file versions

≪ Previous: Hotfix Package 4 for Microsoft Application Virtualization 4.6 Service Pack 2 is now available

Hotfix Package 3 for Microsoft Application Virtualization 5.0 SP1 (App-V 5.0 SP1) is now available for download. To see what’s fixed and get a download link, please see the following: KB2897085 - Hotfix Package 3 for Microsoft Application Virtualization...(read more)

↧

KB: Current list of App-V 5.0 file versions

December 18, 2013, 10:58 am

≫ Next: Now Available: Microsoft Application Virtualization 4.6 Service Pack 3

≪ Previous: Hotfix Package 3 for Microsoft Application Virtualization 5.0 SP1 now available

This article is a quick reference to determine Microsoft Application Virtualization 5.0 (App-V 5.0) file versions. This is helpful to support personnel in determining whether an environment is using the latest binaries. To identify the build version...(read more)

↧

Now Available: Microsoft Application Virtualization 4.6 Service Pack 3

January 9, 2014, 9:58 am

≫ Next: Your guide to App-V 5.0 application publishing and client interaction

≪ Previous: KB: Current list of App-V 5.0 file versions

Microsoft Application Virtualization 4.6 Service Pack 3 (App-V 4.6 SP3) is now available. This service pack provides the latest updates to App-V 4.6. Additionally, this service pack includes some improvements and a hotfix rollup. For details and instructions...(read more)

↧

Your guide to App-V 5.0 application publishing and client interaction

January 20, 2014, 11:28 am

≫ Next: Microsoft Application Virtualization 4.6 SP3 is now supported on System Center Configuration Manager

≪ Previous: Now Available: Microsoft Application Virtualization 4.6 Service Pack 3

We just published a new guide designed to help both new and experienced users of Microsoft Application Virtualization (App-V) gain a better understanding of how the App-V 5.0 SP2 client processes packages and presents them to users. It provides details...(read more)

↧

Microsoft Application Virtualization 4.6 SP3 is now supported on System Center Configuration Manager

January 27, 2014, 9:49 am

≫ Next: How to troubleshoot App-V 5.0 DeploymentConfig & UserConfig script deployment failures using AppV Manage

≪ Previous: Your guide to App-V 5.0 application publishing and client interaction

System Center Configuration Manager 2007 SP2 and System Center 2012 Configuration Manager SP1 now support Microsoft Application Virtualization (App-V) 4.6 SP3 Desktop Client and Application Virtualization Client for Remote Desktop Services. This client...(read more)

↧

How to troubleshoot App-V 5.0 DeploymentConfig & UserConfig script deployment failures using AppV Manage

January 30, 2014, 10:42 am

≫ Next: Applications Suitable for Virtualizing in Microsoft Application Virtualization (App-V)

≪ Previous: Microsoft Application Virtualization 4.6 SP3 is now supported on System Center Configuration Manager

Hello everyone, John Behneman here again. Recently I had case where a customer wanted to modify policy registry keys during a publishing event. Specifically, he wanted to disable protected mode for his Adobe 11 package. By default, protected mode is enabled...(read more)

↧

Applications Suitable for Virtualizing in Microsoft Application Virtualization (App-V)

February 10, 2014, 12:39 pm

≫ Next: Hotfix Package 1 for Microsoft User Experience Virtualization 2.0 is now available

≪ Previous: How to troubleshoot App-V 5.0 DeploymentConfig & UserConfig script deployment failures using AppV Manage

~ Chuck Timon A question often asked by customers is “What types of applications are suitable for virtualizing using Microsoft’s Application Virtualization (App-V) solution?” Occasionally it’s more specific where the question is “Does Microsoft publish...(read more)

↧

Hotfix Package 1 for Microsoft User Experience Virtualization 2.0 is now available

February 12, 2014, 8:05 am

≫ Next: How to sequence a shortcut to a file extension using App-V v5

≪ Previous: Applications Suitable for Virtualizing in Microsoft Application Virtualization (App-V)

This one is UE-V specific but since so many App-V customers also use UE-V I thought I’d go ahead and post this here. Consider the following scenario: - You deploy the Microsoft User Experience Virtualization 2.0 agent. - You have Microsoft Excel or another...(read more)

↧

How to sequence a shortcut to a file extension using App-V v5

February 13, 2014, 9:17 am

≫ Next: App-V 5.0 SP2 and UE-V 2.0 are now available

≪ Previous: Hotfix Package 1 for Microsoft User Experience Virtualization 2.0 is now available

~ Philip McLoughlin Hi everyone, I recently came across an interesting issue with App-V v5 and I wanted to share it in case anyone else happened to see it. I was working with a customer who had sequenced a shortcut to an HTA file but when the app was...(read more)

↧

App-V 5.0 SP2 and UE-V 2.0 are now available

December 2, 2013, 3:51 pm

≫ Next: New recommendations for App-V 5.0 capacity planning

≪ Previous: How to sequence a shortcut to a file extension using App-V v5

↧

New recommendations for App-V 5.0 capacity planning

February 26, 2014, 12:54 pm

≫ Next: Hotfix Package 2 for Microsoft Application Virtualization 5.0 Service SP2 is now available

≪ Previous: App-V 5.0 SP2 and UE-V 2.0 are now available

We recently published new recommendations that can be used as a baseline to help determine capacity planning information that is appropriate to your organization’s App-V 5.0 infrastructure. The following sections are included: Determine the Project Scope...(read more)

↧