Failed upgrading with ESMconsole from 4.2.3 to 4.2.6

Announcements
Attention: The LIVEcommunity is experiencing an interruption with videos in some areas. We apologize for any inconvenience this may cause. Thank you for your patience as we work towards a solution to restore videos.
Reply
Highlighted
L1 Bithead

Failed upgrading with ESMconsole from 4.2.3 to 4.2.6

Hi Community, 

 

After we successfully install the ESMCore to the server we are having an error

RichardP11_0-1586327532373.png

 

have you experience this? 

Highlighted
L4 Transporter

Re: Failed upgrading with ESMconsole from 4.2.3 to 4.2.6

You're going to need to run the installer again with verbose logging enabled to identify the issue.  For your install run the following:

 

msiexec.exe /i PackageName.msi /L*V Console426.log (replace PackageName with the name of your msi)

 

The output of this statement will be a log file named Console426.log in the msi directory.  (You can change the location of the log file by putting a different path). Anyway, after it fails, search for the error in the log.  If you need additional help, you can post the error here and I will review.

 

 


David Falcon 
MDR Systems Engineer, Cortex
Palo AltoNetworks® 
Highlighted
L1 Bithead

Re: Failed upgrading with ESMconsole from 4.2.3 to 4.2.6

Here's the errors:

 

 

StartIIS7ConfigTransaction: Entering StartIIS7ConfigTransaction in C:\Windows\Installer\MSI70C1.tmp, version 3.11.1701.0
MSI (s) (48:40) [12:42:04:232]: Executing op: ActionStart(Name=RollbackIIS7ConfigTransaction,Description=Rolling back IIS Config Transaction,)
Action 12:42:04: RollbackIIS7ConfigTransaction. Rolling back IIS Config Transaction
MSI (s) (48:40) [12:42:04:232]: Executing op: CustomActionSchedule(Action=RollbackIIS7ConfigTransaction,ActionType=11521,Source=BinaryData,Target=Password,CustomActionData=Password)
MSI (s) (48:40) [12:42:04:232]: Executing op: ActionStart(Name=CommitIIS7ConfigTransaction,Description=Committing IIS Config Transaction,)
Action 12:42:04: CommitIIS7ConfigTransaction. Committing IIS Config Transaction
MSI (s) (48:40) [12:42:04:232]: Executing op: CustomActionSchedule(Action=CommitIIS7ConfigTransaction,ActionType=11777,Source=BinaryData,Target=Password,CustomActionData=Password)
MSI (s) (48:40) [12:42:04:232]: Executing op: ActionStart(Name=ConfigureIIs7Exec,Description=Configuring IIS,)
Action 12:42:04: ConfigureIIs7Exec. Configuring IIS
MSI (s) (48:40) [12:42:04:232]: Executing op: CustomActionSchedule(Action=ConfigureIIs7Exec,ActionType=11265,Source=BinaryData,Target=Password,CustomActionData=Password)
MSI (s) (48:90) [12:42:04:232]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI719D.tmp, Entrypoint: ConfigureIIs7Exec
ConfigureIIs7Exec: Entering ConfigureIIs7Exec in C:\Windows\Installer\MSI719D.tmp, version 3.11.1701.0
ConfigureIIs7Exec: Skipping ScaMimeMapRead() - required table not present
ConfigureIIs7Exec: Skipping ScaHttpHeaderRead() - required tables not present.
ConfigureIIs7Exec: Skipping ScaWebErrorRead() - required tables not present.
ConfigureIIs7Exec: Entering ScaWebsRead7()
ConfigureIIs7Exec: Exiting ScaWebsRead7()
ConfigureIIs7Exec: Skipping ScaInstallWebDirs7() because IIsWebDir table not present
ConfigureIIs7Exec: Could not find Web: DefaultWebSite, defaulting to Default Web Site
ConfigureIIs7Exec: Skipping ScaFiltersRead() - no IIsFilter table
ConfigureIIs7Exec: Skipping ScaInstallProperty() - required table not present
ConfigureIIs7Exec: Skipping ScaWebSvcExtCommit() because there are no web service extensions in the list
ConfigureIIs7Exec: Custom action data hash: A1520A0D1554B4BE3B0E92BD70C1EF13CD61A88C
MSI (s) (48:40) [12:42:04:404]: Executing op: ActionStart(Name=WriteIIS7ConfigChanges,Description=Installing Config Keys and Values,)
Action 12:42:04: WriteIIS7ConfigChanges. Installing Config Keys and Values
MSI (s) (48:40) [12:42:04:404]: Executing op: CustomActionSchedule(Action=WriteIIS7ConfigChanges,ActionType=11265,Source=BinaryData,Target=Password,CustomActionData=Password)
MSI (s) (48:80) [12:42:04:419]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI724A.tmp, Entrypoint: WriteIIS7ConfigChanges
WriteIIS7ConfigChanges: Entering WriteIIS7ConfigChanges in C:\Windows\Installer\MSI724A.tmp, version 3.11.1701.0
WriteIIS7ConfigChanges: Custom action data hash: A1520A0D1554B4BE3B0E92BD70C1EF13CD61A88C
WriteIIS7ConfigChanges: CustomActionData WriteIIS7ConfigChanges length: 64
WriteIIS7ConfigChanges: Error 0x8007045a: Failed to open AppHostWritableAdminManager to configure IIS7
WriteIIS7ConfigChanges: Error 0x8007045a: WriteIIS7ConfigChanges Failed.
CustomAction WriteIIS7ConfigChanges returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 12:42:04: InstallFinalize. Return value 3.

 

--------------------------------

 

MSI (c) (90:A8) [12:42:20:060]: Product: Endpoint Security Manager Console 4.2.6.41522 -- Installation failed.

MSI (c) (90:A8) [12:42:20:060]: Windows Installer installed the product. Product Name: Endpoint Security Manager Console 4.2.6.41522. Product Version: 4.2.6.41522. Product Language: 1033. Manufacturer: Palo Alto COMworks, Inc.. Installation success or error status: 1603.

MSI (c) (90:A8) [12:42:20:060]: Grabbed execution mutex.
MSI (c) (90:A8) [12:42:20:060]: Cleaning up uninstalled install packages, if any exist
MSI (c) (90:A8) [12:42:20:075]: MainEngiCOMhread is returning 1603
=== Verbose logging stopped: 07-04-2020 12:42:20 ===

 

Thank you for your help

Highlighted
L4 Transporter

Re: Failed upgrading with ESMconsole from 4.2.3 to 4.2.6

What are the log entries prior to the rollback action?


David Falcon 
MDR Systems Engineer, Cortex
Palo AltoNetworks® 
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!