VMware Horizon Community
mario_981
Enthusiast
Enthusiast
Jump to solution

Custom Appstack

Hi Everyone,

We had a requirement wherein we needed a custom appstack template of size 60GB.

We had a Windows Server 2012 R2 machine which we used to create the custom appstack template of size 60GB using the 20 GB default template.

Once all done with the creation of new template, we started the capture using 60GB template.

While installing the app , msi installer says error 2755 unable to detect the file. Then I ended this failed capture session and disconnected the appstack.

Once again I tried to install application but this time on OS directly, then no such errors were reported.

Then I tried to connect the good old 20GB template and tried a capture, even then I get the same error.

Anyone came across such scenario , Please suggest.

1 Solution

Accepted Solutions
sconley
Enthusiast
Enthusiast
Jump to solution

I just got off of a call with VMware regarding this issue.  Uninstalling just KB 4487017 on Windows 10 1803 resolved the issue for me.  Apparently this breaks MSI based provisioning only and is not exclusive to 2.15 as we downgraded to 2.14.2 and had the same issue.  .EXE based installs still work without issue (we tested with NOTEPAD++ while on the call).

View solution in original post

44 Replies
sjesse
Leadership
Leadership
Jump to solution

What application are you trying to install, and if its not common, what does it do. Also if your trying to install the file from a network share, try coping it locally.

Reply
0 Kudos
mario_981
Enthusiast
Enthusiast
Jump to solution

It happens for any application we try to install , I have tried copying the content locally and running it but error remains the same.

Reply
0 Kudos
sjesse
Leadership
Leadership
Jump to solution

Is the windows installer service running?

Reply
0 Kudos
mario_981
Enthusiast
Enthusiast
Jump to solution

yeah its running and i have tried restarting it as well.

Also tried to restart the app volumes agent as well.

Reply
0 Kudos
sjesse
Leadership
Leadership
Jump to solution

Have you successfully done this before? Normally to build the provisioning machines I copy the parent image used to create the pool your are deploying the application to. Then I uninstall everything but the app volumes agent, make sure a local administrator is created and added to the local administrators group.

Read these if you haven't before

Preparing a Provisioning Machine

Best Practices for Provisioning Virtual Machines and Applications

VMware App Volumes Deployment Considerations: VMware App Volumes 2.12 and Later

Reply
0 Kudos
mario_981
Enthusiast
Enthusiast
Jump to solution

Can we use the same machine first for creating custom template and second to do provisioning.

Is it allowed or we must use different VMs for both these process.

Reply
0 Kudos
Ray_handels
Virtuoso
Virtuoso
Jump to solution

When creating an appstack if I notice that the default 20GB template doesn't cut it I simply enlarge the disk there and then. I once needed to extend the appstack 2 times, just enlarge it using the packaging machine and extend in Windows et voila.

If you do have an error with the default 20Gb template without extending my guess is that you have a different issue.

When looking at your use case you need to have the applications to be published using RDSH? Because you are packaging on a Server 2012? You do know that you need to remove View Agent before packaging? Do you happen to have any kind of logging or screenshots about what is happening? When is the error showing up? Are you able to start the packaging process?

Reply
0 Kudos
mario_981
Enthusiast
Enthusiast
Jump to solution

I get an event ID 10005 and msi installer error 2755 with argument 110.

I cant understand its an Windows issue or Appstack issue.

But installation works fine when appstack is detached.

Reply
0 Kudos
ESBINF
Contributor
Contributor
Jump to solution

Hi,

We have the same problem

Which appvolume version do you use? 2.15?

Reply
0 Kudos
sjesse
Leadership
Leadership
Jump to solution

I don't think its an appstack issue if it works without it. Whats the application and what version of appvolumes are you using

Reply
0 Kudos
mario_981
Enthusiast
Enthusiast
Jump to solution

2.14.2.9 is the version we are running today.

Did you guys managed to fix it in your envrionment or was there a workaround.

Reply
0 Kudos
mario_981
Enthusiast
Enthusiast
Jump to solution

Problem corresponds to all application when tried for installation in provisioning mode.

But all apps do get installed  local C Drive, when we detach the appstack in first place.

' The Installer says system cannot open the device or file specified and then shows an error code 2755 '

Reply
0 Kudos
sjesse
Leadership
Leadership
Jump to solution

You may want to open a ticket with support, they can do a webex to watch whats going on. I have deployed probably over unique 100 app stacks by now and haven't seen this. I believe its an issue with your provisioning process. Your doing a provisioning machine with 2012, have you tried any other ones, like a windows 7 one. I currently capture all my 2012 appstacks on a windows 7 machine because we have never had an issue sharing them, if you edit the appstack after its checked you can pick the os you can attach them to.

Reply
0 Kudos
hermanc01
Enthusiast
Enthusiast
Jump to solution

I'm experiencing this issue as well.  Doesn't matter if I use 2.14.2 or 2.15.0 of the agent.  Any application that uses an msi to perform the install throws the 2755 msi error code.

I haven't confirmed it yet but I think it started happening after the "February 12, 2019—KB4487017 (OS Build 17134.590)" Windows Update.

If I attempt to install the failing applications on the same system but without in provisioning mode, the application installs just fine.

Reply
0 Kudos
sjesse
Leadership
Leadership
Jump to solution

on your provisioning machines do you have windows update disabled, and are you rolling back to a clean state after capturing applications.

Reply
0 Kudos
hermanc01
Enthusiast
Enthusiast
Jump to solution

Yes and yes.

I even rebuilt our provisioning machine (Windows 10 1803) in the event the Windows Installer service was corrupt.

Reply
0 Kudos
mario_981
Enthusiast
Enthusiast
Jump to solution

Hermanac01 - After OS reinstallation ( assuming your image didnt contain that update ) did provisioning work ?

Reply
0 Kudos
hermanc01
Enthusiast
Enthusiast
Jump to solution

It failed on the rebuilt VM but I did have the latest Windows Updates installed.

I rolled it back to having no updates installed (Windows 10 1803 build 17134.1) and I didn't get the issue.  Definitely some issue between the latest Windows Updates and the App Volumes agent.

I do have a case open with support about this as well.

Reply
0 Kudos
mario_981
Enthusiast
Enthusiast
Jump to solution

Let me give it a shot and let you know

Reply
0 Kudos