VMware Horizon Community
starshark
Enthusiast
Enthusiast
Jump to solution

Appvol agent update for 4.0.1 failed with roolback

Erro in installation log containing string

MSI (s) (70:FC) [12:41:13:144]: Executing op: CustomActionSchedule(Action=ExecSecureObjects,ActionType=11265,Source=BinaryData,Target=**********,CustomActionData=**********)

MSI (s) (70:E8) [12:41:13:160]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI55C4.tmp, Entrypoint: ExecSecureObjects

ExecSecureObjects:  Entering ExecSecureObjects in C:\Windows\Installer\MSI55C4.tmp, version 3.11.2318.0

ExecSecureObjects:  Securing Object: C:\Program Files (x86)\CloudVolumes\Agent\Logs\ Type: CreateFolder User: Authenticated Users

ExecSecureObjects:  Error 0x80070534: failed to get sid for account: NT AUTHORITY\Authenticated Users

CustomAction ExecSecureObjects returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Action ended 12:41:13: InstallFinalize. Return value 3.

MSI (s) (70:FC) [12:41:13:191]: Note: 1: 2265 2:  3: -2147287035

MSI (s) (70:FC) [12:41:13:191]: User policy value 'DisableRollback' is 0

MSI (s) (70:FC) [12:41:13:207]: Machine policy value 'DisableRollback' is 0

MSI (s) (70:FC) [12:41:13:207]: Note: 1: 2318 2: 

MSI (s) (70:FC) [12:41:13:207]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1350133029,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)

MSI (s) (70:FC) [12:41:13:207]: Executing op: DialogInfo(Type=0,Argument=1033)

MSI (s) (70:FC) [12:41:13:207]: Executing op: DialogInfo(Type=1,Argument=App Volumes Agent)

MSI (s) (70:FC) [12:41:13:207]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])

Action 12:41:13: Rollback. Rolling back action:

Rollback: ExecSecureObjects

MSI (s) (70:FC) [12:41:13:222]: Executing op: ActionStart(Name=ExecSecureObjects,,)

MSI (s) (70:FC) [12:41:13:222]: Executing op: ProductInfo(ProductKey={FA91D6E1-0690-4B56-ACB0-E9B8BD346095},ProductName=App Volumes Agent,PackageName=App Volumes Agent.msi,Language=1033,Version=67108865,Assignment=1,ObsoleteArg=0,ProductIcon=CloudVolumes.ico,PackageMediaPath=\Installation\Agent\,PackageCode={4D948CF3-7984-4A7E-80AB-0E25949B7F03},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)

Rollback: Updating environment strings

In non-english (example russian) windows system not exists nt account NT AUTHORITY\Authenticated Users, but exist localized account with same sid.

For example

part of cmd whoami /groups

.....

NT AUTHORITY\Прошедшие проверку                                      Хорошо известная группа S-1-5-11     Обязательная группа, Включены по умолчанию, Включенная группа

.....

Maybe this information help us. Thanks for great product.

1 Solution

Accepted Solutions
julatoski
VMware Employee
VMware Employee
Jump to solution

starshark​, DanielLenz​, ryul

The download of 4.0.1 has been corrected to support versions of Microsoft Windows 10 which provide a language translation of the NT AUTHORITY\Authenticated Users account.

If you are having this issue, please 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.

We truly appreciate the patience from our customers in Russia, Germany, Poland and any other locations that have had this issue.

Thank you again!


Jeff Ulatoski
Product Line Manager, App Volumes

View solution in original post

7 Replies
julatoski
VMware Employee
VMware Employee
Jump to solution

Hi starshark​,

You're more than welcome.  I'm happy you like the product.

Was this a new install of the agent or an upgrade from the App Volumes 4.0.0 build?

Have you submitted a support request with VMware?

Best regards.


Jeff Ulatoski
Product Line Manager, App Volumes
Reply
0 Kudos
DanielLenz
Enthusiast
Enthusiast
Jump to solution

Hi julatoski

same here with a customer using german language. Install routine does not find the SID of "NT-Authority\Authenticated Users".

Will there be a fix for the installer or should we install the master/parent vm with en-us and use language pack?

Best regards

Daniel

Reply
0 Kudos
starshark
Enthusiast
Enthusiast
Jump to solution

Hi julatoski

Thanks for answer.

I am trying update from the App Volumes 4.0.0 build - unsuccesfull. Rollback delete all, with version 4.0.0.

Then i am install once more 4.0.1 (new install) and unsuccesfull again with same error.

I have'nt a support VMware.

Reply
0 Kudos
julatoski
VMware Employee
VMware Employee
Jump to solution

Hi DanielLenz​ and starshark​,

Thank you for your help in identifying this issue. Our team is already aware of the issue and are testing a fix. The problem appears to be limited to Windows versions which have translated NT AUTHORITY\Authenticated Users to the country's native language.  It also appears that many Windows versions with non-english languages have retained the original translation for the account name and should not be affected.

The workaround to use the en-us version of Windows and add the appropriate language pack is a good suggestion. We also realize this may not be sufficient in some organizations.  If your organization requires a specific language of Windows and a rapid resolution to this issue, my recommendation is to open a support ticket asking for a fix. 

Thank you again for your help!


Jeff Ulatoski
Product Line Manager, App Volumes
ryul
Enthusiast
Enthusiast
Jump to solution

Hi there,

is an official solution provided by VMware on it's way (workaround or fix), that does not depend on using a different language Windows image?

I personally think it's strange that such issue occurs on an expensive enterprise software by VMware.

This is an error which should be detected by quality checks in no time, because testing on english only OS systems is definitly not the reality here.

Reply
0 Kudos
julatoski
VMware Employee
VMware Employee
Jump to solution

Hi ryul

A new installer will be available for download shortly.  You may also download and use App Volumes 4.0.0 which does not have this installer issue.  If you need 4.0.1 sooner, please contact our global support team and they can help.

Thank you for your patience.


Jeff Ulatoski
Product Line Manager, App Volumes
julatoski
VMware Employee
VMware Employee
Jump to solution

starshark​, DanielLenz​, ryul

The download of 4.0.1 has been corrected to support versions of Microsoft Windows 10 which provide a language translation of the NT AUTHORITY\Authenticated Users account.

If you are having this issue, please 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.

We truly appreciate the patience from our customers in Russia, Germany, Poland and any other locations that have had this issue.

Thank you again!


Jeff Ulatoski
Product Line Manager, App Volumes