VMware Horizon Community
SchwarzC
Enthusiast
Enthusiast

VMware Horizon Client not updateable via AppVolume

Dear all,

When trying to update the Horizon Client from v 4.2.0 to 4.3 or 4.4 I get an error on our Provision Machine and the installation process gets back rolled. The error msg doesn`t say anything specific.

Anybody has the same issue?

Best,

Clemens

Reply
0 Kudos
2 Replies
Lakshman
Champion
Champion

Could you share the error number please? As a workaround, please provision the latest version of Horizon client in a new AppStack.

Reply
0 Kudos
SchwarzC
Enthusiast
Enthusiast

MSI (s) (BC:50) [17:06:14:076]: MainEngineThread is returning 1603

MSI (s) (BC:C8) [17:06:14:076]: User policy value 'DisableRollback' is 0

MSI (s) (BC:C8) [17:06:14:076]: Machine policy value 'DisableRollback' is 0

MSI (s) (BC:C8) [17:06:14:076]: Incrementing counter to disable shutdown. Counter after increment: 0

MSI (s) (BC:C8) [17:06:14:076]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2

MSI (s) (BC:C8) [17:06:14:076]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2

MSI (s) (BC:C8) [17:06:14:076]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1

MSI (s) (BC:C8) [17:06:14:076]: Restoring environment variables

MSI (s) (BC:C8) [17:06:14:076]: Destroying RemoteAPI object.

MSI (s) (BC:68) [17:06:14:076]: Custom Action Manager thread ending.

MSI (c) (58:94) [17:06:14:076]: Back from server. Return value: 1603

MSI (c) (58:94) [17:06:14:076]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1

MSI (c) (58:94) [17:06:14:076]: PROPERTY CHANGE: Deleting SECONDSEQUENCE property. Its current value is '1'.

Action ended 17:06:14: ExecuteAction. Return value 3.

MSI (c) (58:94) [17:06:14:076]: Doing action: FatalError

MSI (c) (58:94) [17:06:14:076]: Note: 1: 2205 2:  3: ActionText

Action 17:06:14: FatalError.

Action start 17:06:14: FatalError.

Action 17:06:14: FatalError. Dialog created

This is what I extracted out of the TEMP Folder (vminst.log) - can you work with this? Yeah I wanted to avoid this, since we bundle our Applications for Departments.

Reply
0 Kudos