Error 0x80070001 caquietexec failed

The recurring error I’m getting is «CAQuietExec:  Error 0x80070001: CAQuietExec Failed».

The above troubleshooting article mentions that the most likely cause is the action that was executed just above the first instance of «Return value 3» within the log. This is the chunk of output that I have for this:

CAQuietExec:  
MSI (s) (A0!EC) [10:02:23:235]: Closing MSIHANDLE (650) of type 790531 for thread 6892
MSI (s) (A0!EC) [10:02:23:235]: Creating MSIHANDLE (651) of type 790531 for thread 6892
CAQuietExec:  Error 0x80070002: Command line returned an error.
MSI (s) (A0!EC) [10:02:23:235]: Closing MSIHANDLE (651) of type 790531 for thread 6892
MSI (s) (A0!EC) [10:02:23:235]: Creating MSIHANDLE (652) of type 790531 for thread 6892
CAQuietExec:  Error 0x80070002: CAQuietExec Failed
MSI (s) (A0!EC) [10:02:23:235]: Closing MSIHANDLE (652) of type 790531 for thread 6892
CustomAction CA_START_WMI_SERVICES returned actual error code 1603 but will be translated to success due to continue marking
MSI (s) (A0:A4) [10:02:23:235]: Closing MSIHANDLE (646) of type 790536 for thread 1928
MSI (s) (A0:88) [10:02:23:235]: Executing op: ActionStart(Name=CA_ROLLBACK_START_REMOVEDATA_SERVICES,,)
Action 10:02:23: CA_ROLLBACK_START_REMOVEDATA_SERVICES. 
MSI (s) (A0:88) [10:02:23:235]: Executing op: CustomActionSchedule(Action=CA_ROLLBACK_START_REMOVEDATA_SERVICES,ActionType=1281,Source=BinaryData,Target=CAQuietExec,CustomActionData=»C:Program FilesMicrosoftExchange ServerV14\binQuietExe.exe»
«C:WindowsSystem32WindowsPowerShellv1.0powershell.exe» » -Version 2.0 -command . ‘C:Program FilesMicrosoftExchange ServerV14\binservicecontrol.ps1’ BeforePatch»)
MSI (s) (A0:88) [10:02:23:235]: Executing op: ActionStart(Name=CA_START_REMOVEDATA_SERVICES,Description=Starting services,Template=Service: [1])
Action 10:02:23: CA_START_REMOVEDATA_SERVICES. Starting services
MSI (s) (A0:88) [10:02:23:235]: Executing op: CustomActionSchedule(Action=CA_START_REMOVEDATA_SERVICES,ActionType=1025,Source=BinaryData,Target=CAQuietExec,CustomActionData=»C:Program FilesMicrosoftExchange ServerV14\binQuietExe.exe» «C:WindowsSystem32WindowsPowerShellv1.0powershell.exe»
» -Version 2.0 -command . ‘C:Program FilesMicrosoftExchange ServerV14\binservicecontrol.ps1’ AfterPatch»)
MSI (s) (A0:88) [10:02:23:251]: Creating MSIHANDLE (653) of type 790536 for thread 1928
MSI (s) (A0:78) [10:02:23:267]: Invoking remote custom action. DLL: C:WindowsInstallerMSICD7B.tmp, Entrypoint: CAQuietExec
MSI (s) (A0!50) [10:02:30:735]: Creating MSIHANDLE (654) of type 790531 for thread 9040
CAQuietExec:  Error 0x80070001: Command line returned an error.
MSI (s) (A0!50) [10:02:30:735]: Closing MSIHANDLE (654) of type 790531 for thread 9040
MSI (s) (A0!50) [10:02:30:735]: Creating MSIHANDLE (655) of type 790531 for thread 9040
CAQuietExec:  Error 0x80070001: CAQuietExec Failed
MSI (s) (A0!50) [10:02:30:735]: Closing MSIHANDLE (655) of type 790531 for thread 9040
CustomAction CA_START_REMOVEDATA_SERVICES returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (A0:78) [10:02:30:735]: Closing MSIHANDLE (653) of type 790536 for thread 1928
Action ended 10:02:30: InstallFinalize. Return value 3.
MSI (s) (A0:88) [10:02:30:751]: User policy value ‘DisableRollback’ is 0
MSI (s) (A0:88) [10:02:30:751]: Machine policy value ‘DisableRollback’ is 0
MSI (s) (A0:88) [10:02:30:766]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1231638331,LangId=1033,Platform=589824,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (A0:88) [10:02:30:766]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (A0:88) [10:02:30:766]: Executing op: DialogInfo(Type=1,Argument=Update Rollup 15 for Exchange Server 2010 Service Pack 3 (KB3184728))
MSI (s) (A0:88) [10:02:30:766]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back actions,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
Action 10:02:30: Rollback. Rolling back actions

This was initially failing right at the beginning when attempting to stop the services but managed to get past this by following the advice in the last post of this thread: https://translate.google.co.uk/translate?hl=en&sl=de&u=http://www.mcseboard.de/topic/197327-exchange-2010-sp3-rollup-5-installiert-nicht/&prev=search

However, this now fails and rolls back right at the end when trying to start services with the above log output.

I have another 3 instances of Return value 3 in the log but the troubleshooting article suggests the first instance is the cause of the failure, however, I can provide these snippets if need be.

I’ve been running the installer from an administrator prompt, UAC is disabled, AV is disabled and PowerShell LocalMachine execution
policy is set to unrestricted and is what the «CAQuietExec:  Error 0x80070001″ error references to,
again, according to the above article.

Been troubleshooting this for the last 2 weeks without success. Any ideas?

Two issues of IIS Express v10 on microsoft/windowsservercore:10.0.14393.576 #524

I was trying to install IIS Express v10 on the latest (as of 27/12/2016) windowsservercore image:

Then looking at the installation log, we got errors like this:

But on a pretty old TP5 image we don’t have this, instead the log look like this:

After looking at the msi with Orca, if I run manually:

So this is issue one, that we got incomplete install of IIS Express here.

Now issue two is even more of a trouble, for an asp.net site I did which works perfectly before on TP5, now if I do curl http://localhost -UseBasicParsing I would get

This seems can be solved by

But nonetheless it does work before on TP5, without needing this extra bit, which kind of cancelled the point of having an Express. So it must be something in the base image for these two issues.

The text was updated successfully, but these errors were encountered:

@xied75 the Web-WHC is probably a change in default from TP5, you should add it as part of the Dockerfile if you need it.

I can repro the msi problem. It doesn’t look like there’s an MSI parameter to turn of that feature.

@xied75 out of curiosity, why are you wanting to run IIS express vs. full IIS (for which there are Microsoft-maintained base images).

@friism I went back to TP5 and checked, there is no WHC enabled there. So it’s something else. In any way IIS Express should work by itself without rely on some magic components, nothing mentioned in its documentation for this.

Regarding the msi problem, it does not affect the website running; the compatibility database is just a bunch of HKLM keys, but it might worth finding out why it doesn’t work on RTM base image, as it could affect other softwares.

For the last question, I’m using IIS Express for this:
https://github.com/coderobin/windows-container/tree/master/windowsservercore/nuget.server
Given this is more a «workgroup» solution, as NuGet team also has a full blown version which is better suited for full IIS, I thought it’s reasonable to use the «smaller» thing for it.

Besides, IIS Express is an executable, not a service, making it much better fit with Docker idiom, look the difference of my ENTRYPOINT with the official IIS one, the «ping» thing is not ideal. If the service die, the container should stop.

Ping @shirhatti — do you know someone that could help with this one? I’m not familiar with IIS Express. We should get a code sample published in this doc repo

Is there anything I can help with? Trying to close dead issues

Are you still having problems Dong?

I’m still waiting answers from you guys.

OK I circled back with the team and got some answers. Sorry this has been sitting so long. That’s our bad.

There was a bug. You helped us find it, thank you!

We fixed the bug and shipped the patch with an OS update a few months ago. Client: Win10 Anniversary Update, Server: Windows Server 2016. If you still are having issues, definitely let me know!

If you are curious, the bug was around the way containers handle registry keys.

I was looking at your NuGet project and I want to make sure I’m helping you achieve your goals with Windows Containers. What are you trying to do exactly?

@mylesbkeating1993 Thanks for all these.

Regarding the fix, do you mean the fix is on the container host (i.e. Windows Server 2016 in my case) or the windowsservercore base image or both?

I was using 10.0.14393.576 when I raised this issue. Could you kindly point out from which version the fix is in? https://hub.docker.com/r/microsoft/windowsservercore/tags/

About why I’m using IIS Express with this simple NuGet project:

1, This is one component in my CI build pipeline. My Jenkins build will be triggered by GitHub push and build my portable libraries and push to my Nuget source.
2, when build containers the best practice is to keep it as small as possible, in my case I just need a nuget container that can hold enough packages for my UWP app development use, therefore using the «proper» https://github.com/NuGet/NuGetGallery is overkill, thus using full IIS is also overkill.

Ok update.
Sorry for the delay — DockerCon and prepping for Build have taken over our lives haha

I jumped the gun, it’s a little more complicated.

• The fix is in the OS, not the image
• It has to do with registry key virtualization. Happy to explain further if you are curious
• Original plan was to create and ship a fix with Server 2016, but the work was pushed back on the grounds that using full IIS is a workaround
• Since this is a Server OS fix, this means the next opportunity to ship it is actually in the fall

So in short, if you want to use IIS express you’ll need to wait for the Server update in the fall. In the meantime, full IIS is your best bet.

I understand this isn’t your ideal scenario to make your container as small as possible. Unfortunately we have more things to work on than we have time to complete, so we need to prioritize.

Please let me know if I can help with anything else!

Again, thanks a lot for posting. You helped us find a bug and a fix is on the way 🙂

@mylesbkeating1993 Thanks a lot for your good work and good words. I fully understand how much backlog you guys have for Windows container. Keep going.

Wish you a great Build, (are you giving any talks? Which session?)

Feel free to close this issue. 🙂

p.s. This is the App I built with my own CI pipeline fully running in Windows Containers on Azure:
https://www.microsoft.com/store/apps/9ntphrk6qlfg

@xied75 Thank you for using our stuff and building cool things with it!

Источник

Troubleshooting Windows HLK Setup

This article contains information to help you to troubleshoot Windows Hardware Lab Kit (Windows HLK) installation and setup issues.

Cannot browse \ HLKInstall on Studio or Client computer

If you cannot browse to the HLKInstall folder from the Windows HLK Studio or Client, review the setup and configuration information in the Step 1: Install Controller and Studio on the test server topic.

Cannot change or repair Windows HLK by using Control Panel

If you try to change or repair the Windows HLK by using Control Panel, you receive an error message that the repair failed. To change or repair your Windows HLK installation, use Control Panel to uninstall Windows Hardware Certification Kit, and then reinstall the Windows HLK See Step 1: Install Controller and Studio on the test server.

Cannot install HLK.AddLoggerEntries: Access is denied

In rare cases, Windows HLK setup might fail just before it completes. If you look at the Windows HLK Controller log, CA AddLoggerEntries appears with an Access is denied error. If this happens, run HLKSetup.exe again to see if the Windows HLK installs successfully. If setup fails again, see Windows HLK Support for instructions about how to contact Support. Include the *HLKControllerx86_en_us.log file from the %temp%hlk folder. For information about how to review the Windows HLK Controller log file, see To review the Windows HLK Controller log file.

Cannot install the Windows HLK Client

If you cannot install the Windows HLK Client, review the installation info in the Step 2: Install Client on the test system(s) topic and make sure that you follow these instructions.

If you still cannot install the Windows HLK Client, locate these Client log files in the %TEMP% folder for the user that installed the HLK client. See Windows HLK Support for information about how to contact Support, and share the following client log files with Microsoft Support:

HLKInstall.log or WLKInstall.log for older kits

Windows Hardware Certification Kit Client_Install.log

Windows Driver Testing Framework (WDTF) Runtime Libraries_Install.log

Application Verifier x64 External Package_Install.log

Cannot install or remove the Windows HLK Controller

If you encounter issues installing the Windows HLK Controller, confirm the following:

The operating system uses the English language (en-us) version of Windows ServerВ 2008В R2 x64 or Windows ServerВ 2012 and is not running as a domain controller.

The system language is set to US English. To do this, click Region and Language in Control Panel, click the Administrative tab, click Change system locale, and then select English (United States).

If you cannot install or remove the Windows HLK Controller, review the controller log file that is located in the %temp%HLK folder.

To review the Windows HLK Controller log file

At a command prompt, type %HomeDrive%, and then press Enter.

Type cd %temp%HLK, and then press Enter.

Type dir *HLKControllerx86_en_us.log, and then press Enter.

Open the log file in a text editor such as Notepad.

If more than one file ends in HLKControllerx86_en_us.log, open the newest file. To open the log file in Notepad from the command line, type Notepad, the full file name, and then press Enter.

Search for return value 3 to see which action failed. Error information is located a few lines above the string return value 3.

If the *HLKControllerx86_en_us.log file includes Error while creating new data store ‘Jobs’, complete these steps:

Delete these files from the C:Program Files (x86)Microsoft SQL ServerMSSQL10_50.MSSQLSERVERMSSQLDATA folder:

Reinstall the Windows HLK Controller. For info on how to do this, see Step 1: Install Controller and Studio on the test server

Client installation fails with error «This app can’t run on your PC»

The system returns an error «This app can’t run on your PC» if you try to install Windows HLK Client software on a computer that is running WindowsВ 8 RT. This is not a supported platform; however, you can install Windows HLK Client software on a computer that is running WindowsВ RT 8.1.

Error: Failed to connect to database. Failed to connect to OM.

If you get an error message that states Failed to connect to database. Failed to connect to OM when you start Windows HLK Studio, make sure that your user account is added to the Windows HLK Controller. For instructions on how to add your user account to the Windows HLK Controller, see «Configure additional user accounts» in Install a remote HLK Studio.

Error: SQL client components are required for this operation

This error occurs when you attempt to install the full version of HLK (HLK Controller + Studio option), after you first downloaded the HLK product on a separate machine that already has the HLK Studio only option installed.

Workaround: Uninstall the HLK Studio-only version and try downloading and reinstalling the full HLK version again.

This error can occur when uninstalling and then reinstalling HLK. When the new instance of HLK is installed, one of the following error messages appears:

• There is already an object named DSLinkType in the database.
• The database database_name already exists.
• Failed to create SQL database.

When uninstalling HLK, database uninstall can fail if the database is locked by another process. The HLK uninstall reports success, but the database is left behind.

To recover, follow these steps:

From an elevated command prompt, run SQLCMD -E

From the SQL Shell command line, enter the following:

Verify that C:Program FilesMicrosoft SQL ServerMSSQL(sql version).MSSQLSERVERMSSQLDATA contains no files starting with WTTIdentity or HLKJobs

Источник

Deployment & Management

Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.

• Qlik Community
• :
• All Forums
• :
• Deployment & Management
• :
• Failed to configure per machine MSI package during.

• Subscribe to RSS Feed
• Mark Topic as New
• Mark Topic as Read
• Float this Topic for Current User
• Bookmark
• Subscribe
• Mute
• Printer Friendly Page

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Hello, I’ve been struggling to get our Qliksense September 2018 installation to update properly to September 2019 on a Windows 2016 Standard server.

The upgrade process seems to run fine and in the installation logs I see all .MSI’s getting installed properly, except the ServiceDispatcher. It is during the installation of this .MSI that I get the error 0x80070643 as shown in the log snippet below.

I’ve ran SFC and DISM to correct any missing install files for .NET or MSI installer and they both without reporting any issues. I found a post which mentioned that .NET Framework 4.8 might be at fault, but this isn’t installed.

After rolling back the Qliksense installation is not complete and only a few services still exist. I have to revert to a snapshot of the server made previously, in order to get the system back online again.

I can’t seem to find any solution that works for this and would appreciate any help !

Источник

Cannot apply Exchange 2010 SP3 roll-up 11

I’m trying to apply a roll-up to our Exchange 2010 servers, but I keep getting an error that indicates that the account I am using does not have permissions in Exchange. While I don’t doubt that there is a permission error in here somewhere, I am 100% certain that the account has permissions to pretty much do anything in Exchange. I’ve tried multiple downloads, elevated command prompts, unrestricted PowerShell execution policies and I am just stuck. Currently I am trying to go from Exchange SP3 Roll-up 7 to Rollup 11. I even tried Roll-up 10 but got the same error. I’ve run a verbose log during an install, but I’m not sure I can post it here due to size. From what I’ve dug up, it looks like the error is here, but I’m not sure:

remove-PSSnapin -Name Microsoft.Exchange.Management.PowerShell.E2010

Exit ($exitcode)». (ec: 0x0)

MSI (c) (14!E8) [17:14:14:537]: Closing MSIHANDLE (2) of type 790531 for thread 6888

MSI (c) (14!E8) [17:14:14:537]: Creating MSIHANDLE (3) of type 790531 for thread 6888

1: ExPatchCa: GetProperty: Get property: RunCommandTimeout (RunCommandTimeout): 300000. (ec: 0x0)

MSI (c) (14!E8) [17:14:14:537]: Closing MSIHANDLE (3) of type 790531 for thread 6888

MSI (c) (14!E8) [17:14:40:433]: Creating MSIHANDLE (4) of type 790531 for thread 6888

1: ExPatchCa: RunCommand: ExecCommand: exit code: 0x5. timeout: 300000 ms(user set). (ec: 0x0)

MSI (c) (14!E8) [17:14:40:433]: Closing MSIHANDLE (4) of type 790531 for thread 6888

MSI (c) (14!E8) [17:14:40:433]: PROPERTY CHANGE: Adding RunCommandResult property. Its value is ‘5’.

MSI (c) (14!E8) [17:14:40:433]: Creating MSIHANDLE (5) of type 790531 for thread 6888

1: ExPatchCa: SetProperty: Set property: RunCommandResult: 5. (ec: 0x0)

MSI (c) (14!E8) [17:14:40:433]: Closing MSIHANDLE (5) of type 790531 for thread 6888

MSI (c) (14:BC) [17:14:40:433]: Closing MSIHANDLE (1) of type 790542 for thread 6668

Action ended 17:14:40: CA_PATCH_OWA_PERMISSION. Return value 1.

MSI (c) (14:0C) [17:14:40:433]: Doing action: CA_PATCH_OWA_PERMISSION_ERROR

Action 17:14:40: CA_PATCH_OWA_PERMISSION_ERROR.

Action start 17:14:40: CA_PATCH_OWA_PERMISSION_ERROR.

MSI (c) (14:0C) [17:14:40:448]: Transforming table CustomAction.

MSI (c) (14:0C) [17:14:40:448]: Transforming table CustomAction.

MSI (c) (14:0C) [17:14:40:448]: Note: 1: 2262 2: CustomAction 3: -2147287038

MSI (c) (14:0C) [17:14:40:448]: Transforming table CustomAction.

MSI (c) (14:0C) [17:14:40:448]: Transforming table CustomAction.

MSI (c) (14:0C) [17:14:40:448]: Note: 1: 2262 2: CustomAction 3: -2147287038

MSI (c) (14:0C) [17:14:40:448]: Transforming table CustomAction.

MSI (c) (14:0C) [17:14:40:448]: Transforming table CustomAction.

MSI (c) (14:0C) [17:14:40:448]: Note: 1: 2262 2: CustomAction 3: -2147287038

MSI (c) (14:24) [17:14:40:464]: Transforming table Binary.

MSI (c) (14:24) [17:14:40:464]: Transforming table Binary.

MSI (c) (14:24) [17:14:40:464]: Note: 1: 2262 2: Binary 3: -2147287038

MSI (c) (14:24) [17:14:40:464]: Transforming table Binary.

MSI (c) (14:24) [17:14:40:464]: Transforming table Binary.

MSI (c) (14:24) [17:14:40:464]: Note: 1: 2262 2: Binary 3: -2147287038

MSI (c) (14:24) [17:14:40:464]: Transforming table Binary.

MSI (c) (14:24) [17:14:40:464]: Transforming table Binary.

MSI (c) (14:24) [17:14:40:464]: Note: 1: 2262 2: Binary 3: -2147287038

MSI (c) (14:24) [17:14:40:464]: Note: 1: 2262 2: Error 3: -2147287038

MSI (c) (14:24) [17:14:40:464]: Transforming table Error.

MSI (c) (14:24) [17:14:40:464]: Transforming table Error.

MSI (c) (14:24) [17:14:40:464]: Note: 1: 2262 2: Error 3: -2147287038

MSI (c) (14:24) [17:14:40:464]: Transforming table Error.

MSI (c) (14:24) [17:14:40:464]: Transforming table Error.

MSI (c) (14:24) [17:14:40:464]: Note: 1: 2262 2: Error 3: -2147287038

MSI (c) (14:24) [17:14:40:464]: Transforming table Error.

MSI (c) (14:24) [17:14:40:479]: Transforming table Error.

MSI (c) (14:24) [17:14:40:479]: Note: 1: 2262 2: Error 3: -2147287038

DEBUG: Error 2826: Control BottomLine on dialog ErrorDlg extends beyond the boundaries of the dialog to the right by 5 pixels

The installer encountered an unexpected error while installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: ErrorDlg, BottomLine, to the right

The user who’s currently logged on doesn’t have sufficient permissions to install this package. You need at least Exchange Server Administrator permissions on the current computer to complete this task.

MSI (c) (14:0C) [17:19:35:069]: Note: 1: 2262 2: Error 3: -2147287038

MSI (c) (14:0C) [17:19:35:069]: Transforming table Error.

MSI (c) (14:0C) [17:19:35:069]: Transforming table Error.

MSI (c) (14:0C) [17:19:35:069]: Note: 1: 2262 2: Error 3: -2147287038

MSI (c) (14:0C) [17:19:35:069]: Transforming table Error.

MSI (c) (14:0C) [17:19:35:085]: Transforming table Error.

MSI (c) (14:0C) [17:19:35:085]: Note: 1: 2262 2: Error 3: -2147287038

MSI (c) (14:0C) [17:19:35:085]: Transforming table Error.

MSI (c) (14:0C) [17:19:35:085]: Transforming table Error.

MSI (c) (14:0C) [17:19:35:085]: Note: 1: 2262 2: Error 3: -2147287038

MSI (c) (14:0C) [17:19:35:085]: Product: Microsoft Exchange Server — The user who’s currently logged on doesn’t have sufficient permissions to install this package. You need at least Exchange Server Administrator permissions on the current computer to complete this task.

Action ended 17:19:35: CA_PATCH_OWA_PERMISSION_ERROR. Return value 3.

MSI (c) (14:0C) [17:19:35:085]: Doing action: FatalError

Popular Topics in Microsoft Exchange

I ended up punting on this. IT seems that the particular server I was trying to update is just screwed up somehow. I was able to update a different CAS server in my environment with the same account. The unpatchable server will just server to expedite my Exchange 2013 migration.

Did you run the update as administrator? If running from Exchange powershell did you launch that as administrator? Obviously, is the account you are using a full exchange admin account?

Also make sure your powershell script execution policy is set to unrestricted.

***EDIT*** I see you have done this all already.

One last thing, I believe the account needs to be in the OU «Microsoft Exchange Security Groups -> Organization Management»

Thanks for the effort, but there is nothing here that I have not already checked/verified. That’s part of why I am stumped.

I tried a different admin account and ended up with a different error:

Action 16:48:41: CA_CUSTOMER_PREPATCH_INSTALL.

MSI (s) (40:A0) [16:48:41:128]: Executing op: CustomActionSchedule(Action=CA_CUSTOMER_PREPATCH_INSTALL,ActionType=1089,Source=BinaryData,Target=CAQuietExec,CustomActionData=»C:Program FilesMicrosoftExchange ServerV14\binQuietExe.exe» «C:WindowsSystem32WindowsPowerShellv1.0powershell.exe» » -Version 2.0 -command . ‘C:Program FilesMicrosoftExchange ServerV14\scriptscustomizationCustomPatchInstallerActions.ps1’ PrePatchInstallActions»)

MSI (s) (40:A0) [16:48:41:128]: Creating MSIHANDLE (17) of type 790536 for thread 9888

MSI (s) (40:88) [16:48:41:143]: Invoking remote custom action. DLL: C:WindowsInstallerMSIDB.tmp, Entrypoint: CAQuietExec

MSI (s) (40:DC) [16:48:41:143]: Generating random cookie.

MSI (s) (40:DC) [16:48:41:159]: Created Custom Action Server with PID 8088 (0x1F98).

MSI (s) (40:98) [16:48:41:190]: Running as a service.

MSI (s) (40:98) [16:48:41:190]: Hello, I’m your 32bit Impersonated custom action server.

MSI (s) (40!78) [16:48:41:658]: Creating MSIHANDLE (18) of type 790531 for thread 7288

CAQuietExec: Error 0x80070001: Command line returned an error.

MSI (s) (40!78) [16:48:41:658]: Closing MSIHANDLE (18) of type 790531 for thread 7288

MSI (s) (40!78) [16:48:41:658]: Creating MSIHANDLE (19) of type 790531 for thread 7288

CAQuietExec: Error 0x80070001: CAQuietExec Failed

MSI (s) (40!78) [16:48:41:658]: Closing MSIHANDLE (19) of type 790531 for thread 7288

CustomAction CA_CUSTOMER_PREPATCH_INSTALL returned actual error code 1603 but will be translated to success due to continue marking

MSI (s) (40:88) [16:48:41:658]: Closing MSIHANDLE (17) of type 790536 for thread 9888

MSI (s) (40:A0) [16:48:41:658]: Executing op: ActionStart(Name=CA_ROLLBACK_SAVEDATA_STOP_SERVICES,,)

Action 16:48:41: CA_ROLLBACK_SAVEDATA_STOP_SERVICES.

MSI (s) (40:A0) [16:48:41:658]: Executing op: CustomActionSchedule(Action=CA_ROLLBACK_SAVEDATA_STOP_SERVICES,ActionType=1281,Source=BinaryData,Target=CAQuietExec,CustomActionData=»C:Program FilesMicrosoftExchange ServerV14\binQuietExe.exe» «C:WindowsSystem32WindowsPowerShellv1.0powershell.exe» » -Version 2.0 -command . ‘C:Program FilesMicrosoftExchange ServerV14\binservicecontrol.ps1’ AfterPatch»)

MSI (s) (40:A0) [16:48:41:658]: Executing op: ActionStart(Name=CA_START_WMI_SERVICES_ROLLBACK,,)

Action 16:48:41: CA_START_WMI_SERVICES_ROLLBACK.

MSI (s) (40:A0) [16:48:41:674]: Executing op: CustomActionSchedule(Action=CA_START_WMI_SERVICES_ROLLBACK,ActionType=1345,Source=BinaryData,Target=CAQuietExec,CustomActionData=»C:WindowsSysWOW64net.exe» start WinMgmt)

MSI (s) (40:A0) [16:48:41:674]: Executing op: ActionStart(Name=CA_ENABLE_WMI_SERVICES_ROLLBACK,,)

Action 16:48:41: CA_ENABLE_WMI_SERVICES_ROLLBACK.

MSI (s) (40:A0) [16:48:41:674]: Executing op: CustomActionSchedule(Action=CA_ENABLE_WMI_SERVICES_ROLLBACK,ActionType=1345,Source=BinaryData,Target=CAQuietExec,CustomActionData=»C:WindowsSysWOW64sc.exe» config WinMgmt start= auto)

MSI (s) (40:A0) [16:48:41:674]: Executing op: ActionStart(Name=CA_SAVEDATA_STOP_SERVICES,Description=Stopping services,Template=Service: [1])

Action 16:48:41: CA_SAVEDATA_STOP_SERVICES. Stopping services

MSI (s) (40:A0) [16:48:41:674]: Executing op: CustomActionSchedule(Action=CA_SAVEDATA_STOP_SERVICES,ActionType=1025,Source=BinaryData,Target=CAQuietExec,CustomActionData=»C:Program FilesMicrosoftExchange ServerV14\binQuietExe.exe» «C:WindowsSystem32WindowsPowerShellv1.0powershell.exe» » -Version 2.0 -command . ‘C:Program FilesMicrosoftExchange ServerV14\binservicecontrol.ps1’ BeforePatch»)

MSI (s) (40:A0) [16:48:41:674]: Creating MSIHANDLE (20) of type 790536 for thread 9888

MSI (s) (40:7C) [16:48:41:674]: Invoking remote custom action. DLL: C:WindowsInstallerMSI2FE.tmp, Entrypoint: CAQuietExec

MSI (s) (40!8C) [16:48:44:918]: Creating MSIHANDLE (21) of type 790531 for thread 11148

CAQuietExec: Error 0x80070001: Command line returned an error.

MSI (s) (40!8C) [16:48:44:918]: Closing MSIHANDLE (21) of type 790531 for thread 11148

MSI (s) (40!8C) [16:48:44:918]: Creating MSIHANDLE (22) of type 790531 for thread 11148

CAQuietExec: Error 0x80070001: CAQuietExec Failed

MSI (s) (40!8C) [16:48:44:918]: Closing MSIHANDLE (22) of type 790531 for thread 11148

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

MSI (s) (40:7C) [16:48:44:918]: Closing MSIHANDLE (20) of type 790536 for thread 9888

Action ended 16:48:44: InstallExecute. Return value 3.

Источник

I was trying to install IIS Express v10 on the latest (as of 27/12/2016) windowsservercore image:

RUN powershell -Command 
    wget https://download.microsoft.com/download/C/E/8/CE8D18F5-D4C0-45B5-B531-ADECD637A1AA/iisexpress_amd64_en-US.msi -OutFile iisexpress_amd64_en-US.msi; 
    Start-Process -FilePath msiexec.exe -ArgumentList /i, "C:iisexpress_amd64_en-US.msi", /qn, /L, iisexpress_amd64_en-US.install.log -PassThru -Wait;

Then looking at the installation log, we got errors like this:

Action start 15:05:49: InstallFinalize.
CAQuietExec:  Error: Couldn't add 'IIS Express Application Compatibility Database for x64' to registry.
CAQuietExec:  Uninstallation of IIS Express Application Compatibility Database for x64 complete.
CAQuietExec:  Error 0x80070001: Command line returned an error.
CAQuietExec:  Error 0x80070001: CAQuietExec Failed
CustomAction CA_SETUP_APPCOMPAT returned actual error code 1603 but will be translated to success due to continue marki
g
CAQuietExec:  Error: Couldn't add 'IIS Express Application Compatibility Database for x86' to registry.
CAQuietExec:  Uninstallation of IIS Express Application Compatibility Database for x86 complete.
CAQuietExec:  Error 0x80070001: Command line returned an error.
CAQuietExec:  Error 0x80070001: CAQuietExec Failed
CustomAction CA_SETUP_APPCOMPAT32 returned actual error code 1603 but will be translated to success due to continue mar
ing

But on a pretty old TP5 image we don’t have this, instead the log look like this:

Action start 13:34:59: InstallFinalize.
CAQuietExec:  Installation of IIS Express Application Compatibility Database for x64 complete.
CAQuietExec:  Installation of IIS Express Application Compatibility Database for x86 complete.
CAQuietExec:  Command 'setupDefaultUrls' completed.

After looking at the msi with Orca, if I run manually:

PS C:> sdbinst.exe -q .iisexpressshim.sdb
Error: Couldn't add 'IIS Express Application Compatibility Database for x64' to registry.
Uninstallation of IIS Express Application Compatibility Database for x64 complete.

So this is issue one, that we got incomplete install of IIS Express here.

Now issue two is even more of a trouble, for an asp.net site I did which works perfectly before on TP5, now if I do curl http://localhost -UseBasicParsing I would get

Server Error in '/' Application.
 Specified argument was out of the range of valid values.Parameter name: site

This seems can be solved by

PS C:> Install-WindowsFeature Web-WHC

as mentioned here: https://social.msdn.microsoft.com/Forums/windows/en-US/cb6a04e1-19d6-4a75-be25-aca16b89f166/server-error-application-httpexception-0x80004005?forum=winformssetup

But nonetheless it does work before on TP5, without needing this extra bit, which kind of cancelled the point of having an Express. So it must be something in the base image for these two issues.

Installation Checklist 

Further investigation, during the ServiceDispatcher installation the logfile says :

File: C:Program FilesQlikSenseHybridDeploymentServiceappsettings.json; Won’t Overwrite; Won’t patch; Existing file is unversioned but modified.

Our current (Sept2018) appsetings.json file in this location doesn’t hold the node :

«LocalBearerToken»: {
«SigningAlgorithm»: «RS256»,
«Certificate»: «./server.pem»,
«PrivateKey»: «./server_key.pem»
}

The Powershell script that is executed during the installation IS updated as per the log :

File: C:Program FilesQlikSenseHybridDeploymentServiceConfigure-Service.ps1; Overwrite; Won’t patch; Existing file is unversioned and unmodified — hash doesn’t match source file

I unpacked all installation files from the SchedulerDispatcher.MSI and took a peek at the updated Configure-Service.ps1 script. In this script they try to set 2 variables based on an object (appsettings) created from the unmodified/not-overwritten appsettings.json file:

$appsettings.LocalBearerToken.Certificate = «$localCertificatesLocationserver.pem»
$appsettings.LocalBearerToken.PrivateKey = «$localCertificatesLocationserver_key.pem»

As this node doesn’t  exist in the not-updated appsettings.json file, the Powershell script returns the error in previous post, returning in the MSI returning an error code and the whole rollback starts.

This evening, before trying the upgrade for a 4th time, I will modify the appsettings.json file to hold this LocalBearerToken entry in the current appsettings.json file. This should cause the Configure-Service.ps1 script not to throw an error and hopefully finished the installation succesfully. I will post the outcome.

I’m writing some CustomActions in WiX to migrate a web.config from IIS6 to IIS7 and am getting an error. However if I copy and paste the failing command from the install log file, it succeeds. Here’s section of the log file that indicates the error. You’ll see the first two appcmds succeed but the last migration command fails.

Action 10:43:52: UnlockModulesCmd. 
Action start 10:43:52: UnlockModulesCmd.
MSI (s) (80:44) [10:43:52:631]: PROPERTY CHANGE: Adding QtExecCmdLine property. Its value is '"C:Windowssystem32inetsrvappcmd" unlock config -section:system.webServer/modules'.
Action ended 10:43:52: UnlockModulesCmd. Return value 1.
MSI (s) (80:44) [10:43:52:641]: Doing action: UnlockModules
Action 10:43:52: UnlockModules. Migrating to IIS7
Action start 10:43:52: UnlockModules.
MSI (s) (80:44) [10:43:52:691]: Creating MSIHANDLE (834) of type 790542 for thread 2116
MSI (s) (80:B8) [10:43:52:691]: Invoking remote custom action. DLL: C:WindowsInstallerMSI72FF.tmp, Entrypoint: CAQuietExec
MSI (s) (80!7C) [10:43:52:771]: Creating MSIHANDLE (835) of type 790541 for thread 892
MSI (s) (80!7C) [10:43:52:771]: Creating MSIHANDLE (836) of type 790531 for thread 892
MSI (s) (80!7C) [10:43:52:781]: Closing MSIHANDLE (836) of type 790531 for thread 892
MSI (s) (80!7C) [10:43:52:781]: PROPERTY CHANGE: Deleting QtExecCmdLine property. Its current value is '"C:Windowssystem32inetsrvappcmd" unlock config -section:system.webServer/modules'.
MSI (s) (80!7C) [10:43:53:752]: Creating MSIHANDLE (837) of type 790531 for thread 892
CAQuietExec:  Unlocked section "system.webServer/modules" at configuration path "MACHINE/WEBROOT/APPHOST".
MSI (s) (80!7C) [10:43:53:762]: Closing MSIHANDLE (837) of type 790531 for thread 892
MSI (s) (80!7C) [10:43:53:762]: Closing MSIHANDLE (835) of type 790541 for thread 892
MSI (s) (80:B8) [10:43:53:762]: Closing MSIHANDLE (834) of type 790542 for thread 2116
Action ended 10:43:53: UnlockModules. Return value 1.
MSI (s) (80:44) [10:43:53:772]: Doing action: UnlockHandlersCmd
Action 10:43:53: UnlockHandlersCmd. 
Action start 10:43:53: UnlockHandlersCmd.
MSI (s) (80:44) [10:43:53:792]: PROPERTY CHANGE: Adding QtExecCmdLine property. Its value is '"C:Windowssystem32inetsrvappcmd" unlock config -section:system.webServer/handlers'.
Action ended 10:43:53: UnlockHandlersCmd. Return value 1.
MSI (s) (80:44) [10:43:53:792]: Doing action: UnlockHandlers
Action 10:43:53: UnlockHandlers. Migrating to IIS7
Action start 10:43:53: UnlockHandlers.
MSI (s) (80:44) [10:43:53:862]: Creating MSIHANDLE (838) of type 790542 for thread 2116
MSI (s) (80:08) [10:43:53:862]: Invoking remote custom action. DLL: C:WindowsInstallerMSI7780.tmp, Entrypoint: CAQuietExec
MSI (s) (80!60) [10:43:54:123]: Creating MSIHANDLE (839) of type 790541 for thread 2144
MSI (s) (80!60) [10:43:54:123]: Creating MSIHANDLE (840) of type 790531 for thread 2144
MSI (s) (80!60) [10:43:54:123]: Closing MSIHANDLE (840) of type 790531 for thread 2144
MSI (s) (80!60) [10:43:54:133]: PROPERTY CHANGE: Deleting QtExecCmdLine property. Its current value is '"C:Windowssystem32inetsrvappcmd" unlock config -section:system.webServer/handlers'.
MSI (s) (80!60) [10:43:54:493]: Creating MSIHANDLE (841) of type 790531 for thread 2144
CAQuietExec:  Unlocked section "system.webServer/handlers" at configuration path "MACHINE/WEBROOT/APPHOST".
MSI (s) (80!60) [10:43:54:503]: Closing MSIHANDLE (841) of type 790531 for thread 2144
MSI (s) (80!60) [10:43:54:503]: Closing MSIHANDLE (839) of type 790541 for thread 2144
MSI (s) (80:08) [10:43:54:513]: Closing MSIHANDLE (838) of type 790542 for thread 2116
Action ended 10:43:54: UnlockHandlers. Return value 1.
MSI (s) (80:44) [10:43:54:634]: Doing action: MigrateIIS7Cmd
Action 10:43:54: MigrateIIS7Cmd. 
Action start 10:43:54: MigrateIIS7Cmd.
MSI (s) (80:44) [10:43:54:644]: PROPERTY CHANGE: Adding QtExecCmdLine property. Its value is '"C:Windowssystem32inetsrvappcmd" migrate config "Default Web Site/sdportal"'.
Action ended 10:43:54: MigrateIIS7Cmd. Return value 1.
MSI (s) (80:44) [10:43:54:654]: Doing action: MigrateIIS7
Action 10:43:54: MigrateIIS7. Migrating to IIS7
Action start 10:43:54: MigrateIIS7.
MSI (s) (80:44) [10:43:54:704]: Creating MSIHANDLE (842) of type 790542 for thread 2116
MSI (s) (80:E8) [10:43:54:704]: Invoking remote custom action. DLL: C:WindowsInstallerMSI7ADE.tmp, Entrypoint: CAQuietExec
MSI (s) (80!14) [10:43:54:714]: Creating MSIHANDLE (843) of type 790541 for thread 2068
MSI (s) (80!14) [10:43:54:724]: Creating MSIHANDLE (844) of type 790531 for thread 2068
MSI (s) (80!14) [10:43:54:724]: Closing MSIHANDLE (844) of type 790531 for thread 2068
MSI (s) (80!14) [10:43:54:724]: PROPERTY CHANGE: Deleting QtExecCmdLine property. Its current value is '"C:Windowssystem32inetsrvappcmd" migrate config "Default Web Site/sdportal"'.
MSI (s) (80!14) [10:43:55:755]: Creating MSIHANDLE (845) of type 790531 for thread 2068
CAQuietExec:  Error 0x80070001: Command line returned an error.
MSI (s) (80!14) [10:43:55:765]: Closing MSIHANDLE (845) of type 790531 for thread 2068
MSI (s) (80!14) [10:43:55:765]: Creating MSIHANDLE (846) of type 790531 for thread 2068
CAQuietExec:  Error 0x80070001: CAQuietExec Failed
MSI (s) (80!14) [10:43:55:775]: Closing MSIHANDLE (846) of type 790531 for thread 2068
MSI (s) (80!14) [10:43:55:775]: Closing MSIHANDLE (843) of type 790541 for thread 2068
MSI (s) (80:E8) [10:43:55:775]: Closing MSIHANDLE (842) of type 790542 for thread 2116
Action ended 10:43:55: MigrateIIS7. Return value 1.

Here’s a follow up. I was able to get appcmd to work by requiring the installer be run as admin. Recently, I added an additional custom command which fails. Here’s the relevant portion of the log. Note that the other appcmd.exe commands run fine. If I copy and past the failing appcmd from the log to a command line prompt, it works. Any thoughts?

MSI (s) (1C:B0) [15:56:46:510]: Invoking remote custom action. DLL: C:WindowsInstallerMSIB74D.tmp, Entrypoint: CAQuietExec
MSI (s) (1C!B8) [15:56:46:570]: PROPERTY CHANGE: Deleting QtExecCmdLine property. Its current value is '"C:Windowssystem32inetsrvappcmd" migrate config    "Default Web Site/sdportal"'.
CAQuietExec:  Error 0x80070001: Command line returned an error.
CAQuietExec:  Error 0x80070001: CAQuietExec Failed
Action ended 15:56:47: MigrateIIS7. Return value 1.
MSI (s) (1C:14) [15:56:47:001]: Doing action: DisableRapidFailCmd
Action 15:56:47: DisableRapidFailCmd. 
Action start 15:56:47: DisableRapidFailCmd.
MSI (s) (1C:14) [15:56:47:011]: PROPERTY CHANGE: Adding QtExecCmdLine property. Its value is '"C:Windowssystem32inetsrvappcmd"  set apppool "WssAppPool"  /failure.rapidFailProtection:false'.
Action ended 15:56:47: DisableRapidFailCmd. Return value 1.
MSI (s) (1C:14) [15:56:47:021]: Doing action: DisableRapidFail
Action 15:56:47: DisableRapidFail. Disabling Rapid Fail
Action start 15:56:47: DisableRapidFail.
MSI (s) (1C:30) [15:56:47:061]: Invoking remote custom action. DLL: C:WindowsInstallerMSIB988.tmp, Entrypoint: CAQuietExec
MSI (s) (1C!64) [15:56:47:141]: PROPERTY CHANGE: Deleting QtExecCmdLine property. Its current value is '"C:Windowssystem32inetsrvappcmd"  set apppool "WssAppPool" /failure.rapidFailProtection:false'.
CAQuietExec:  APPPOOL object "WssAppPool" changed
Action ended 15:56:47: DisableRapidFail. Return value 1.
MSI (s) (1C:14) [15:56:47:502]: Doing action: ConfigureAppPoolLoggingCmd
Action 15:56:47: ConfigureAppPoolLoggingCmd. 
Action start 15:56:47: ConfigureAppPoolLoggingCmd.
MSI (s) (1C:14) [15:56:47:522]: PROPERTY CHANGE: Adding QtExecCmdLine property. Its value is '"C:Windowssystem32inetsrvappcmd" set config /section:applicationPools /[name='WssAppPool'].recycling.logEventOnRecycle:Memory,Schedule,Requests,Time,PrivateMemory'.
Action ended 15:56:47: ConfigureAppPoolLoggingCmd. Return value 1.
MSI (s) (1C:14) [15:56:47:522]: Doing action: ConfigureAppPoolLogging
Action 15:56:47: ConfigureAppPoolLogging. Configuring App Pool Logging
Action start 15:56:47: ConfigureAppPoolLogging.
MSI (s) (1C:C0) [15:56:47:562]: Invoking remote custom action. DLL: C:WindowsInstallerMSIBB7E.tmp, Entrypoint: CAQuietExec
MSI (s) (1C!A8) [15:56:47:602]: PROPERTY CHANGE: Deleting QtExecCmdLine property. Its current value is '"C:Windowssystem32inetsrvappcmd" set config /section:applicationPools /[name='WssAppPool'].recycling.logEventOnRecycle:Memory,Schedule,Requests,Time,PrivateMemory'.
CAQuietExec:  ERROR ( message:Unknown attribute ".recycling.logEventOnRecycle".  Replace with -? for help. )
CAQuietExec:  Error 0x80070585: Command line returned an error.
CAQuietExec:  Error 0x80070585: CAQuietExec Failed