VMware Workspace ONE Community
ahumbert
Contributor
Contributor

Issue with upgrade on version 19.9.04

Hello,


I need some help...I've an issue with the upgrade on premise to 19.9.0.4 from 19.7.0.20.


I made my db update successfully but the application update is failling.. All my airwatch service and iis service are disabled for the moment. Should I enable again the service IIS without any risk ?


I already tried to restart the server but same issue..


Thanks


Here is the last lines of the log:


Action start 16:35:07: AWValidateAWWebServerDialog.
Action ended 16:35:07: AWValidateAWWebServerDialog. Return value 1.
Action start 16:35:07: AWGetIISSiteInfo.
Action ended 16:35:08: AWGetIISSiteInfo. Return value 3.
Info 2896. Executing action AWGetIISSiteInfo failed.
Action ended 16:35:08: InstallWelcome. Return value 3.
Action start 16:35:08: SetupCompleteError.
Action start 16:35:34: ISSetupFilesCleanup.
Action ended 16:35:34: ISSetupFilesCleanup. Return value 1.
Action ended 16:35:34: SetupCompleteError. Return value 2.
Action ended 16:35:34: INSTALL. Return value 3.
=== Logging stopped: 24.10.2019  16:35:34 ===
MSI (c) (0C:6C) [16:35:34:816]: Product: Workspace ONE UEM -- Installation operation failed.

MSI (c) (0C:6C) [16:35:34:816]: Windows Installer installed the product. Product Name: Workspace ONE UEM. Product Version: 19.9.0.4. Product Language: 1033. Manufacturer: VMware, Inc.. Installation success or error status: 1603.

Labels (1)
30 Replies
phil_84
Contributor
Contributor

Hi,
are there any news on this? Just ran into the same error? I will try it with 1907 application Installer now.
best regards
Philipp
Reply
0 Kudos
phil_84
Contributor
Contributor

Ok, just found it in the new release notes : https://kb.vmware.com/s/article/75670
Reply
0 Kudos
PeterDonato
Contributor
Contributor

So, this issue is currently being acknowledged by VMware as ' a bug'  that causes the 1909_Full_Installer (19.9.0.4) to fail, because it fails to respect and honor the IIS binding settings. I have a case open with VMware, and have asked their engineers to apply the ' fix'  to a newer, updated, and working 1909_Full_Installer and they are refusing. They claim its ' too much work' .
As mentioned in the article listed by Philipp R is to apply the ' workaround'  steps:
1. Open IIS Manager on the server and expand the Sites folder in the Connections pane
2. Right-click on Default Web Site and select Edit Bindings
3. Remove all Types other than http or https
     Examples of non-http/https bindings include:
     net.pipe
     net.msmq
     msmq.formatname
     net.tcp
4. Run the Workspace ONE UEM 1909 Application Installer

which I can report is successfully, and then apply the 19.9.0.11 patch
DubravkoJug
Contributor
Contributor

This issue is still present. When will it be corrected?
Reply
0 Kudos
MichaelIllgen
Contributor
Contributor

I was able to install the upgrade after I've removed IIS bindings as described here: https://kb.vmware.com/s/article/75670
Reply
0 Kudos
DubravkoJug
Contributor
Contributor

Does your other things work normal? Like assisgning new apps and creating Tunnel configuration?
Reply
0 Kudos
PhichitB
Contributor
Contributor

What is windows version?
Reply
0 Kudos
JesseIUH
Contributor
Contributor

How has VMware allowed this issue to persist without a warning included when downloading the installer files?
Reply
0 Kudos
BrianMcQueen
Contributor
Contributor

Had issue on just one of my DS servers and followed suggested article posted above in thread https://kb.vmware.com/s/article/75670 and it worked

Reply
0 Kudos
UiliamFoschiera
Enthusiast
Enthusiast

Hi all

Here, only with workaround described in this post (remove other IIS protocols from bindings) I was able to proceed with installation of version 19.9.04. Thanks for sharing.

Someone that opens a support case, was received some explanation about this bug ?

Regards

Uiliam Mello

Reply
0 Kudos
GabeBSCU
Contributor
Contributor

Thank you for the answer, this issue has derailed my upgrade for some time, but after applying the fix everything was smooth sailing 🙂

Reply
0 Kudos