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
AnthonyCardona
Contributor
Contributor

if you have ran a snapshot I would revert , and only shut off the Airwatch services and NOT IIS then run the installer. 
Reply
0 Kudos
Mtakacs88
Contributor
Contributor

Same error detected from our side, SQL is installed successfully but the console server drop an error like this. I try the last comment but won't helped.
Reply
0 Kudos
DavidJonesDavid
Contributor
Contributor

I am getting the same error trying to install 19.9.04
Reply
0 Kudos
KevinKrumm
Enthusiast
Enthusiast

Exactly the same here. I opened up a ticket.
Reply
0 Kudos
ahumbert
Contributor
Contributor

I've also opened a case..  I'll let you know.
Did you made a rollback of the db ?
Reply
0 Kudos
KevinKrumm
Enthusiast
Enthusiast

I didn’t roll back the database. I left it for now. I wanted to see if support can help.
Reply
0 Kudos
MichaelSchn
Enthusiast
Enthusiast

I have the exact same issue.
DB Installer went without problems.
Everything is configured in the application installer and before the the last Install screen appears I get the messsage that the Wizard was interrupted and the installation was not successfull.


Hope they bring a fix soon.
I will disable the services for now because it is fortunately in my testenvironment.


BR
Michael

Reply
0 Kudos
BDBos
Enthusiast
Enthusiast

Same problem here. Already opened a case yesterday (19074767610).


I run on production now with a updated database. Device /Console servers on 1907. Seems to be no problems for the time being.

Reply
0 Kudos
BDBos
Enthusiast
Enthusiast

Warning. For everyone who has already updated the database, pay attention. It appears that the new APNS certificates are not included in this new version!
Everything in the console now ends within 3 days! After the update you have to run the script below again. https://kb.vmware.com/s/article/50121242?lang=en_US

Reply
0 Kudos
ahumbert
Contributor
Contributor

Someone received a response from the support?
@Ben Bos, so you have the db in version 1909 and the console in 1907 without issue?
Reply
0 Kudos
KevinKrumm
Enthusiast
Enthusiast

No response. I'm running 19.7.0.20 for the console and deployments services. And 19.9.0.4 for the Database with no seeable issues. 
Reply
0 Kudos
BDBos
Enthusiast
Enthusiast

Adrien, yes. That’s right. 19.7,0.8 console and device services here and 19.9.0.4 database.
No problems so far here. Waiting for reply from support.
Reply
0 Kudos
PeterDonato
Contributor
Contributor

We encountered the same situation. We were able to upgrade our SQL database to 19.9.0.4, then upgrade the Admin console to the new version, but then encountered the AWGetIISSiteInfo error (repeatedly after trying several reboots and upgrade attempts). At this time, we are running the DS server using 19.7.0.15 and DB/admin console on 19.9.0.4. We have a support case filed for this
Reply
0 Kudos
PeterMohr
Contributor
Contributor

We saw the same today. Upgrading from 1811.
Haven't created a support case yet. We did a rollback of the DB and re-installed 1811

Peter
Reply
0 Kudos
PeterGiesa
Contributor
Contributor

Yes, same in here. We use SNI and have another website on the server. First I thought that this might have caused this issue.
Supported suggested a rollback.
Reply
0 Kudos
BenByCegeka
Contributor
Contributor

Hello,

As far as I can tell, our upgrade was successful. However, we had other problems afterwards:
1. apps could not be uploaded and assigned and any more, no matter in which area (internal, vpp)
2. we couldn't update any documents in the content area, but we already had the problem with AirWatch 19.03.15
3. tunnel profile could not be installed

Benjamin
P.S. We'll roll back.
Reply
0 Kudos
johnsonjf
Contributor
Contributor

We attempted to update from 9.7.0.12 to 1909 last night and got the same error during the Application Server install. We rolled back the DB and then we pivoted to 1907. We were successful with the install to 1907. Has there been any headway or progress with support regarding this 1909 install problem?
Reply
0 Kudos
ahumbert
Contributor
Contributor

The support collected some logs of my airwatch server for the dev teams.
They told me to restore my DB to the previous version.


We can see these erros on the extended logs :


10-28-2019[04:29:05 PM]: Checking setup prerequisite 'Microsoft SQL Server 2012 Native Client 11.3.6538.0 (x64).prq'
10-28-2019[04:29:05 PM]: Prerequisite 'Microsoft SQL Server 2012 Native Client 11.3.6538.0 (x64).prq' scheduled before feature selection
10-28-2019[04:29:05 PM]: Extracting 'Microsoft SQL Server 2012 Native Client 11.3.6538.0 (x64).prq' to C: or Users or A87E7~1.HUM or AppData or Local or Temp or 2 or {9B9CEDF4-5F62-4999-BCC1-C1306BDA3F3F} or Microsoft SQL Server 2012 Native Client 11.3.6538.0 (x64).prq
10-28-2019[04:29:05 PM]: PrereqEngine: condition,16,2,[System64Folder],sqlncli11.dll,,2011.110.6538.0 -- Failed!
10-28-2019[04:29:05 PM]: PrereqEngine: operatingsystemcondition,6,0, -- Failed!,
10-28-2019[04:29:05 PM]: PrereqEngine: operatingsystemcondition,6,0, -- Failed!,
10-28-2019[04:29:05 PM]: PrereqEngine: operatingsystemcondition,6,1,2,1, -- Failed!,

Reply
0 Kudos
turkay_yaray
Contributor
Contributor

Thank you for your help. That workaround worked for us as well. Some protocols, such as net.tcp & net.msmq cannot normally be deleted from the IIS bind list. which can be overcome by removing these features from the ' .NET Framework 4.6'
https://www.c-sharpcorner.com/article/enable-other-protocols-tcp-pipe-msmq-etc-in-iis/
in this way, you will have met the requirements for the workaround, and the installation will be completed successfully.
Reply
0 Kudos