App-V Support Tip: Installation of App-V 4.6 SP3 client fails with error 0x57
~ Keshav Deo Jain
Hi everyone, my name is Keshav and I’m an App-V support engineer here at Microsoft. I recently came across an interesting issue where the App-V 4.6 SP3 client fails to install so I thought I would share what we found with you here. It’s a rare problem but at least with this you’ll know how to fix it in case you ever happen to run across it.
The Problem
In certain scenarios, installation of the Microsoft Application Virtualization 4.6 Service Pack 3 Client (APP-V 4.6 SP3) fails with the following error:
ProductCode specified: {5D80483C-D297-4E04-9EDF-DD58521E9565};{342C9BB8-65A0-46DE-AB7A-8031E151AF69} ::MsiGetProductInfoW error 0x57.Failed to get ``LocalPackage'' value for product code {5D80483C-D297-4E04-9EDF-DD58521E9565};{342C9BB8-65A0-46DE-AB7A-8031E151AF69}. SoftGrid Action: SWI41sp1UpgradeFix Details: Child exited with code 87 SoftGrid Action: SWI41sp1UpgradeFix Details: 41sp1UpgradeFix.exe failed with error: 87 SoftGrid Action: SWI41sp1UpgradeFix Details: Action ended CustomAction SWI41sp1UpgradeFix returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) Action ended 15:02:57: SWI41sp1UpgradeFix. Return value 3. |
Background
Before we dig further towards the solution, let’s have a look at some important MSI properties for App-V 4.6 installers:
Product |
version |
Upgrade code |
Product Code |
Microsoft Application Virtualization Desktop Client. |
4.6.1.20870 |
{515E0D38-8D2E-4B0C-B189-E9BAD1E773EE} |
{342C9BB8-65A0-46DE-AB7A-8031E151AF69} |
Microsoft Application Virtualization Desktop Client |
4.6.2.24020 |
{515E0D38-8D2E-4B0C-B189-E9BAD1E773EE} |
{5D80483C-D297-4E04-9EDF-DD58521E9565} |
Microsoft Application Virtualization Desktop Client |
4.6.3.24870 |
{515E0D38-8D2E-4B0C-B189-E9BAD1E773EE} |
{8D00DBC4-DEB4-4910-9D7C-30A5C6898195} |
This how the upgrade table looks like for APP-V 4.6 SP3:
UpgradeCode |
VersionMin |
VersionMax |
Language |
Attributes |
Remove |
ActionProperty |
{515E0D38-8D2E-4B0C-B189-E9BAD1E773EE} |
4.6.3.24870 |
513 |
OLDPRODUCTS |
|||
{515E0D38-8D2E-4B0C-B189-E9BAD1E773EE} |
4.6.3.24870 |
2 |
NEWPRODUCTFOUND |
The table above has some value defined for the Attribute which has the following meaning:
Attribute |
Meaning |
512 + 1 = (513) |
1 = Migrates feature states by enabling the logic in the MigrateFeatureStates action. 512 = Detects the range of versions including the value in VersionMax. |
2 |
Detects products and applications but does not remove. |
What this all means is that if the installer finds any App-V product with an upgrade code of {515E0D38-8D2E-4B0C-B189-E9BAD1E773EE} and a version less than “4.6.3.24870” then the installer tries to migrate the existing product installed on the machine to the recent version (which we are trying to install).
Cause
So based on the information above, we can see that App-V 4.6 SP3 is trying to migrate the features of App-V 4.6 SP1 ({342C9BB8-65A0-46DE-AB7A-8031E151AF69}) and App-V 4.6 SP2 ({5D80483C-D297-4E04-9EDF-DD58521E9565}.
Since this is a migration, the installer for App-V 4.6 SP3 needs the cached installer files for the previous version. Generally these files are cached under C:\windows\installer or the ccm cache, however in this scenario these installer files seem to be missing:
ProductCode specified: {5D80483C-D297-4E04-9EDF-DD58521E9565};{342C9BB8-65A0-46DE-AB7A-8031E151AF69} ::MsiGetProductInfoW error 0x57.Failed to get ``LocalPackage'' value for product code {5D80483C-D297-4E04-9EDF-DD58521E9565};{342C9BB8-65A0-46DE-AB7A-8031E151AF69}. |
If you tried to repair the App-V 4.6 SP2, you would probably get the error below. Here as well, the App-V 4.6 SP2 installer is trying to find the locally cached installer.
The Resolution
In a case like this, we simply need to remove the installed version of the client (App-V 4.6 SP2 or APP-V 4.6 SP1) before installing APP-V 4.6 SP3. The uninstall command line for these products are below:
Product |
Version |
Command line: |
Microsoft Application Virtualization Desktop Client. |
4.6.1.20870 |
Msiexec /x {342C9BB8-65A0-46DE-AB7A-8031E151AF69} |
Microsoft Application Virtualization Desktop Client |
4.6.2.24020 |
Msiexec /x {5D80483C-D297-4E04-9EDF-DD58521E9565} |
NOTE: If uninstalling the old client fails for whatever reason, you can usually fix that with our utility here:
Fix problems that programs cannot be installed or uninstalled
Keshav Deo Jain | Support Engineer | Microsoft GBS Management and Security Division
Get the latest System Center news on Facebook and Twitter :
System Center All Up: https://blogs.technet.com/b/systemcenter/
Configuration Manager Support Team blog: https://blogs.technet.com/configurationmgr/
Data Protection Manager Team blog: https://blogs.technet.com/dpm/
Orchestrator Support Team blog: https://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: https://blogs.technet.com/momteam/
Service Manager Team blog: https://blogs.technet.com/b/servicemanager
Virtual Machine Manager Team blog: https://blogs.technet.com/scvmm
Microsoft Intune: https://blogs.technet.com/b/microsoftintune/
WSUS Support Team blog: https://blogs.technet.com/sus/
The RMS blog: https://blogs.technet.com/b/rms/
App-V Team blog: https://blogs.technet.com/appv/
MED-V Team blog: https://blogs.technet.com/medv/
Server App-V Team blog: https://blogs.technet.com/b/serverappv
The Surface Team blog: https://blogs.technet.com/b/surface/
The Application Proxy blog: https://blogs.technet.com/b/applicationproxyblog/
The Forefront Endpoint Protection blog : https://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : https://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: https://blogs.technet.com/b/isablog/
The Forefront UAG blog: https://blogs.technet.com/b/edgeaccessblog/