MeehowGr
Contributor
Contributor

AppVolume 4.0 Provisioning Problem

Jump to solution

Hello,

Recently I've installed AppVolume Managers 4.0. Have some problems with provisioning on Windows 2016 Standard VM.

Frequently I'm getting message that everything is ok and provisioning ended up successfully, but unfortunately, on manager it looks like that:

pastedImage_0.png

There's 0 Programs in AppStack despite all of them indicated by VM agent during provisioning.

Only errors are in System Messages:

pastedImage_1.png

There's always Primordial OS is immutable and cannot be changed, and then usually Unable to find AppStack.

It's working only from time to time... Usually works when I don't revert provisioning machine back and do another provisioning.

Case opened, but it'll take time Smiley Sad

Regards

Michal

Tags (1)
0 Kudos
1 Solution

Accepted Solutions
julatoski
VMware Employee
VMware Employee

Quick update with a 4.0.2 fix that is available from VMware Global Support Services in addition to the workaround provided.

Please see the related VMware Knowledge Base article 78651 for more details.

Thank you!


Jeff Ulatoski
Product Line Manager, App Volumes

View solution in original post

7 Replies
Benoit230
Contributor
Contributor

Any update on this by chance?

0 Kudos
MattVicos
Enthusiast
Enthusiast

Did you get this issue resolved?

0 Kudos
MattVicos
Enthusiast
Enthusiast

Did you get this issue resolved?

0 Kudos
Scarlito
Contributor
Contributor

Hi everyone.

I got the same problem.

As I had a ticket opened to solve a problem with the Agent version 4.0.1 installation on a Windows 10 with a non english language pack, I asked the support engineer about this "0 program" problem.

He gave me this workaround :

To minimize the efforts of re-capturing the apps, you may use below workaround to resolve this for now,

Workaround: Move the pacakge vmdk to different datastore location, delete the package on app volume ui and move the package back to original storage and import the package on app volume manager.

Procedure:

* Login as root on ESXi through putty SSH mode.
* Navigate to package folder. command:

cd /vmfs/volumes/datastorename/appvolumes/packages

* Type ls -l command to list the packages.
* Type the below command to copy the package to other folder.

cp /vmfs/volumes/datastorename/appvolumes/packages/<nameofpackage>.* /vmfs/volumes/datastore

* Then open app vol UI and remove the package.
* Then run below command to copy the package back to original location,

cp /vmfs/volumes/datastorename/<nameofpackage>.* /vmfs/volumes/datastore/appvolumes/packages/

* Then click on applications tab and click import.

Hope this helps.

Shreyskar
VMware Employee
VMware Employee

Hi MattVicos

The download of 4.0.1 has been corrected to support versions of Microsoft Windows 10 which provide a language translation (non English packs).This was a known issue in App Volumes 4.0.0 and later fixed in 4.0.1.

I would recommend you to test with 4.0.1.

Download VMware App Volumes 4.0.1 again and reinstall from a new ISO. For reference, the corrected ISO for 4.0.1 is named VMware_App_Volumes_v401_20200402.ISO.

Please mark reply as helpful/answered if it addresses your issue.

anthony2005
Contributor
Contributor

Hi.

I also have a "0 program" problem with some applications.

Do I understand correctly that in the App Volumes UI should remove the package and not the application?

And I also guess that should use <package-name>* filemask instead of <package-name>.* so as not to lose <package-name>-flat.vmdk

0 Kudos
julatoski
VMware Employee
VMware Employee

Quick update with a 4.0.2 fix that is available from VMware Global Support Services in addition to the workaround provided.

Please see the related VMware Knowledge Base article 78651 for more details.

Thank you!


Jeff Ulatoski
Product Line Manager, App Volumes