Application Virtualization Client 4.6 SP2 error 1603 / 1708

Previous MSI deployments of 4.6, SP1, and hotfix 3. I believe the prereqs were installed separately since the MSIs were used rather than the EXEs. Everything has been working perfectly until I try to roll out SP2 via setup_upgrade.exe. Here are the errors from the log:

.........................................................................................................................................................................................................
SoftGrid Action: SWI41sp1UpgradeFix Details: 41sp1UpgradeFix process started.
ProductCode specified: {DB9F70CD-29BC-480B-8BA2-C9C2232C4553};{40C3258B-F9D1-46DF-AE97-72C1F86F2427}
::MsiGetProductInfoW error 0x57.Failed to get ``LocalPackage'' value for product code {DB9F70CD-29BC-480B-8BA2-C9C2232C4553};{40C3258B-F9D1-46DF-AE97-72C1F86F2427}.
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)
.........................................................................................................................................................................................................
MSI (s) (6C:3C) [16:42:35:844]: Note: 1: 1708
MSI (s) (6C:3C) [16:42:35:844]: Product: Microsoft Application Virtualization Desktop Client -- Installation operation failed.

MSI (s) (6C:3C) [16:42:35:844]: Windows Installer installed the product. Product Name: Microsoft Application Virtualization Desktop Client. Product Version: 4.6.2.24020. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
.........................................................................................................................................................................................................

I'm not finding any details about SWI41sp1UpgradeFix / Softgrid 4.1SP1/4.2 client errors. Both of these GUIDs are installed and visible in the registry. All I can think is that this is somehow due to the previous MSI deployments rather than EXE and / or corrupt components?
 

Question Info


Last updated March 20, 2018 Views 1,662 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

hi

I was going through some of the issues we saw during the 4.5 beta and came across another one I thought you might find interesting.  This is one where the installation of the App-V client will fail with the following error:

"Installation operation failed. Error 1708"

If you then check the Verbose MSI log you'll also see something along the lines of the following:

=============================
Verbose MSI logs will show MSI (s) (34:68) [19:45:35:263]: Note: 1: 1708
MSI (s) (34:68) [19:45:35:263]: Product: Microsoft Application Virtualization Desktop Client -- Installation operation failed.

MSI (s) (34:68) [19:45:35:263]: Cleaning up uninstalled install packages, if any exist
MSI (s) (34:68) [19:45:35:263]: MainEngineThread is returning 1603
MSI (s) (34:64) [19:45:35:279]: Destroying RemoteAPI object.
MSI (s) (34:88) [19:45:35:279]: Custom Action Manager thread ending.
=== Logging stopped: 7/24/2008  19:45:35 ===
MSI (c) (48:C8) [19:45:35:279]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (48:C8) [19:45:35:279]: MainEngineThread is returning 1603
=== Verbose logging stopped: 7/24/2008  19:45:35 ===

The key here is where it says MainEngineThread is returning 1603.

The exact cause of this can vary but is most likely due to a performance counter registration related issue.  This can happen when a previous version of the client was installed at one time and the unregister failed when it was uninstalled, or there could be registry / file permissions on the machine that are not allowing the creation of one of the temporary files needed to create and register the performance counters. 

To fix this we'll need to clean up the client in question in order to allow a proper re-installation.  To do this open a CMD prompt on the client in question and run the following commands:

regsvr32 /u mavcperf.dll

and then

mofcomp <PATH>\SGCliprvUninstall.Mof

Note: If you are unable to unregister mavcperf.dll (step #1 above) you can perform the following steps:

1.) Run the following command from a command prompt:

unlodctr "Mav Client PerfMon Provider"

2.) Delete the following registry key: 

HKLM\System\CurrentControlSet\Services\MAV Client PerfMon Provider

With any luck, once you do this the client will now install without error.

I'd also like to extend a special thanks to Steve Thomas.  He diligently worked so many of these beta issues and discovered many of the solutions I post here, including this one.  Without him many of these issues would go undocumented.

Hope this helps,

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I was going through some of the issues we saw during the 4.5 beta and came across another one I thought you might find interesting.  This is one where the installation of the App-V client will fail with the following error:

"Installation operation failed. Error 1708"

If you then check the Verbose MSI log you'll also see something along the lines of the following:

=============================
Verbose MSI logs will show MSI (s) (34:68) [19:45:35:263]: Note: 1: 1708
MSI (s) (34:68) [19:45:35:263]: Product: Microsoft Application Virtualization Desktop Client -- Installation operation failed.

MSI (s) (34:68) [19:45:35:263]: Cleaning up uninstalled install packages, if any exist
MSI (s) (34:68) [19:45:35:263]: MainEngineThread is returning 1603
MSI (s) (34:64) [19:45:35:279]: Destroying RemoteAPI object.
MSI (s) (34:88) [19:45:35:279]: Custom Action Manager thread ending.
=== Logging stopped: 7/24/2008  19:45:35 ===
MSI (c) (48:C8) [19:45:35:279]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (48:C8) [19:45:35:279]: MainEngineThread is returning 1603
=== Verbose logging stopped: 7/24/2008  19:45:35 ===

The key here is where it says MainEngineThread is returning 1603.

The exact cause of this can vary but is most likely due to a performance counter registration related issue.  This can happen when a previous version of the client was installed at one time and the unregister failed when it was uninstalled, or there could be registry / file permissions on the machine that are not allowing the creation of one of the temporary files needed to create and register the performance counters.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

To fix this we'll need to clean up the client in question in order to allow a proper re-installation.  To do this open a CMD prompt on the client in question and run the following commands:

regsvr32 /u mavcperf.dll

and then

mofcomp <PATH>\SGCliprvUninstall.Mof

Note: If you are unable to unregister mavcperf.dll (step #1 above) you can perform the following steps:

1.) Run the following command from a command prompt:

unlodctr "Mav Client PerfMon Provider"

2.) Delete the following registry key: 

HKLM\System\CurrentControlSet\Services\MAV Client PerfMon Provider

With any luck, once you do this the client will now install without error.

I'd also like to extend a special thanks to Steve Thomas.  He diligently worked so many of these beta issues and discovered many of the solutions I post here, including this one.  Without him many of these issues would go undocumented.

Hope this helps,

 

            

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Thanks JPIFSwongcly. I should have been a little more thorough in my initial post. I actually found this info in my research, but when I run regsvr32 /u mavcperf.dll I get the following error: "The module "mavcperf.dll" was loaded but the call to DllUnregisterServer failed with error code 0x80070002."

When I run mofcomp "c:\Program Files\Microsoft Application Virtualization Client\SGCliprvUninstall.Mof", I get the following:
"Parsing MOF file: c:\Program Files\Microsoft Application Virtualization Client\SGCliprvUninstall.Mof
MOF file has been successfully parsed.
Storing data in the repository...
WARNING: File C:\Program Files\Microsoft Application Virtualization Client\SGCliprvUninstall.Mof does not contain #PRAGMA AUTORECOVER.
If the WMI repository is rebuilt in the future, the contents of this MOF file will not be included in the new WMI repository.
To include this MOF file when the WMI Repository is automatically reconstructed, place the #PRAGMA AUTORECOVER statement on the first line of the MOF file.
Done!


When I attempt to run unlodctr "Mav Client PerfMon Provider", I get the following: "Unable to open driver SYSTEM\CurrentControlSet\Services\Mav Client PerfMon Provider. Status: 2"

I can't delete the following reg key, because it does not exist: HKLM\System\CurrentControlSet\Services\MAV Client PerfMon Provider



Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Anyone?

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Applies To: Application Virtualization

You can use the procedures in this section to configure and manage the Microsoft Application Virtualization (App-V) Client. Procedures are provided for manual interaction with the App-V Client by using the App-V Client Management Console and also by using the command line.

In This Section
How to Use the Desktop Notification Area for Application Virtualization Client Management
Includes information about using the features and commands that are available from the Windows desktop notification area.
How to Manage Virtual Applications Manually
Provides information about how to manage the virtual applications by using the App-V Client Management Console.
How to Configure the Application Virtualization Client Settings Manually
Provides a set of procedures that you can use to configure App-V Client settings by using the App-V Client Management Console.
How to Manage Virtual Applications by Using the Command Line
Provides important procedures you can use to manage virtual applications and packages by using the SFTMIME command-line language.
How to Configure the App-V Client Registry Settings by Using the Command Line
Provides a set of procedures you can use to change the configuration of the App-V Client.
Troubleshooting Information for the Application Virtualization Client
Provides information about troubleshooting the App-V Client.
Application Virtualization Client Reference
Contains detailed technical reference material related to installing and managing system components.
See Also

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I don't see anything here in reference to my issues.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

HI

 

Self-support options

Windows 7 Help & how to
Visit the Windows 7 Help & how to center to learn about how to get all you can out of Windows 7.

Windows 7 and hardware and software compatibility
Find out if your software or hardware is compatible or if you just need a software upgrade or a new driver.

Get the latest service packs, updates and more
Visit the Windows Download Center to find the latest services packs, updates, trials and drivers.

Self-support options for work

IT Pros: Windows 7 TechCenter on TechNet
Visit the Windows 7 TechCenter on TechNet for advanced troubleshooting and guidance for IT Pros.

Microsoft Desktop Optimization Pack
Learn more about this suite of technologies available as a subscription for Software Assurance customers to improve compatibility and management, reduce support costs, improve asset management, and improve policy control in your environment.

Developers: Windows Client Developer Center on MSDN
Visit the Visit the Windows Client Developer Center on MSDN to learn about Windows development.

Support for Small Business
Simple help and troubleshooting for small businesses.

Microsoft Partners: Visit the Microsoft Partner Network
Microsoft Partners can access unlimited online support via the Microsoft Partner Network.

Small and Midsize Business Guide
Find tools, technical overviews, step-by-step guides, and videos to help you deploy the latest Windows Client operating system in a small or midsize environment.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

You forgot google.com / bing.com.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Application Virtualization | Topic profile
Topic profile page for Application Virtualization. This page has aggregated data from forum posts, threads, listings, online discussions, newsgroups, messageboards, and other online sources which contain user generated content for the term: Application Virtualization.
Topic "Application virtualization" was discussed 1,892 times on 110 sites in last 3 months
Search discussions, forums about "Application virtualization" on BoardReader!
 

BoardReader Trendy!

Topic 1:

Topic 2:

Topic 3:

Domain Profile

Domain:
Posting activity graph on application virtualization:
 

I thought i'd write up a quicky blog post on using the ConfigMgr Task Sequence to deploy Software Packages, and reveal select parts of the functionality available to you to accomplish the task.

Open up your ConfigMgr console, navigate to the Operating System Deployment node and right click "Task Sequences"

1.       Select “Create a new custom task sequence”

2.       Give it a name

3.       Don’t choose a boot package

4.       Bring the new Task Sequence up in the Task Sequence Editor

Here we go, useful options available to you are:

General:

Run Command Line

Install Software

Connect to Network Folder

The other categories deal with Disks, User State, Images, Drivers and Settings and most are OSD specific and not much use when deploying Software.

So, those three commands under the General category don’t seem much do they? But these puppies give you a lot of control and ability over your package execution.

Here’s a breakdown of the abilities each of these commands gives you:

Run Command Line

Command line can contain NT BATCH statements, but is a bit limited in that the script has to sit on one line. Easy enough if you can use | and &/&&, and other command line tricks to achieve the end result. It can be an executable, a script or any extension that has an association mapped to an application on the client.

 “Start in” is an absolute path to the file system on the client, or relative to the Distribution Point.

Cough, that just gave the game away. Yes, relative to the Distribution Point, meaning you can run scripts that reside in a package that is assigned to a Distribution Point. This is powerful in itself. You could have a “Management Scripts” package and just load it up with scripts\executables et al, and you can now invoke any of these tools from your toolkit. I’ve worked for many a company that has a stash of scripts and tools on a shared area that are both for engineers and used in deployments. Maybe it’s time to copy these in to a ConfigMgr package.

In Configuration Manager R2 you can specify the credentials that are used to launch the Command Line. That’s something I remember a colleague in a past company complained was missing in the jump from SMS 2.0 to SMS2003 (Token nod to Etienne @ BNP), sure this will make him happy now J

Note: If you want to capture output from a program you need to prefix the command with CMD.EXE /C

Install Software

Pretty straight-forward, you select an existing Package and Program and execute it as part of the Task Sequence. You can execute multiple applications here, but being stuck in my ways I like to separate out the software installations in to separate steps. Essentially, so I can control error codes per execution, whether a failure is OK or if the Task Sequence should abort (drop out/exit).

Connect to Network Folder

Typical behavior you’d expect from Windows Explorer Map Network Drive function. Provide the Path, choose the Drive letter and supply the credentials to map the connection with.

Now it’s time to add another layer of complexity and thus, control, and introduce the Options tab that is available for all activities in the Task Sequence.

Options tab

Firstly you can Enable\Disable a step, and as this is all Policy based the switching on and off or even modifying the Task Sequence is done pretty quick as it only depends on a policy update being applied to the MP’s and this replicates quickly.

You also can “Continue on error” which is very handy for hopping over steps that could fail but are not critical to the entire Task Sequence.

The Task Sequence provides you with very limited conditional evaluation methods. You have limited conditional evaluation at hand with the trusty IF statement. Limited in that it meets evaluation criteria based on All, Any or None of the conditions evaluating as positive\negative. No complex IF statements here, but enough control to do some fancy tricks in this space.

The conditions are:

Task Sequence Variable (limited usefulness really)

Operating system Version

File Properties

Folder Properties

Registry Setting

Query WMI

Install Software

Now this certainly isn’t a scripting engine, so I don’t expect much functionality along those lines. But it does give us enough juice to do some interesting things with the installation of a product and its dependencies, even setting up the stage in readiness for the deployment is made simple using the above methods. And once you’ve setup your Task Sequence you can advertise it like you would a Program in a Package to any amount of Clients.

Comparing the Task Sequence as a Software Deployment method with the traditional Software Deployment method, you can see that we now have an additional tool in our toolset for managing these deployments.

Going forward, I’d really like the ConfigMgr Developers to shine some love on this aspect of the product. Make it a bit more robust by allowing me to do string manipulation, let me manipulate data from the output of command lines or existing data repositories (LOG, TXT, CSV, etc).  Allow me to query WMI\File System\Registry etc and put that data in to a string that I can evaluate on, rather than defining what I expect to see then evaluating it for positive\false.

This could become a real monster aspect of the ConfigMgr product, and give the Application deployment teams far more control over the deployment than they already have using the traditional Software Deployment feature.

Grow this area out please Microsoft!

This article was rushed out on a lunch break, it’s really only there to pique your interest and perhaps motivate you in to thinking of using Task Sequences for more than rebuilding OS’s. The amount of SMS administrators I come across, that when I talk about this stuff their eyes light up as if they have figured out how many black holes CERN will introduce to our planet when they switch on the Ring of Death! And hence why I thought I’d take the time out between munching on a sandwich to tap furiously on my keyboard to bring this to you.

Always happy to hear horror\success stories, or anything related to Software Deployments using Task Sequences!  So ping me an email or comment on my blog J

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.