Code Signing Wix installer in the pipeline using azure key vault - wix

I'm trying to code sign a Wix installer package that was developed by another company (I have limited knowledge of Wix).
As a proof of concept piece of work we did I signed the MSIs and EXE using WixSharp.DigitalSignature as below, which seemed to work with a self signed certificate
project.DigitalSignature = new DigitalSignature()
{
PfxFilePath = Resources.CertificateUri,
HashAlgorithm = HashAlgorithmType.sha256,
Description = Resources.BootstrapperProject,
TimeUrls = new System.Collections.Generic.List<Uri>() { new Uri("http://timestamp.digicert.com") }
};
But now the time has come to implement with a proper certificate from GlobalSign it seems the above option isn't now possible as we now have to store the certificate in Azure Key Vault.
We have tried signing the MSIs and EXEs with AzureSignTool through the pipelines but when running the installer I'm always getting the error "0x80070001 - Incorrect function".
The log file outputs the below information:
[0ADC:1034][2021-12-21T11:00:53]i320: Registering bundle dependency provider: {0315ab7d-04da-4a77-8536-fa0e0211c531}, version: 1.0.0.124
[0ADC:1034][2021-12-21T11:00:53]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{0315ab7d-04da-4a77-8536-fa0e0211c531}, resume: Active, restart initiated: No, disable resume: No
[1710:10C8][2021-12-21T11:00:53]i336: Acquiring container: WixAttachedContainer, copy from: C:\Users\Administrator\Desktop\DigiView Installer.exe
[1710:10C8][2021-12-21T11:00:58]i000: Setting string variable 'WixBundleLastUsedSource' to value 'C:\Users\Administrator\Desktop\'
[1710:1720][2021-12-21T11:00:58]e000: Error 0x80070001: Failed to extract all files from container, erf: 1:2:0
[1710:10C8][2021-12-21T11:00:58]e000: Error 0x80070001: Failed to wait for operation complete.
[1710:10C8][2021-12-21T11:00:58]e000: Error 0x80070001: Failed to open container.
[1710:10C8][2021-12-21T11:00:58]e000: Error 0x80070001: Failed to open container: WixAttachedContainer.
[1710:10C8][2021-12-21T11:00:58]e312: Failed to extract payloads from container: WixAttachedContainer to working path: C:\Users\ADMINI~1\AppData\Local\Temp\2\{4D72E5B3-50AB-4B5D-BD93-BC559386F434}\5A4A1D973A87D89730BC20C9B805B7A384EF1383, error: 0x80070001.
[1710:0F88][2021-12-21T11:00:59]e000: Error 0x80070001: Failed while caching, aborting execution.
There is very limited information online about this scenario, does anyone have a way forward for the particular problem I'm facing? Or can point me to some useful resources?

Related

I am trying to apply a patch on one of the WebLogic servers but it throws me this error

I am trying to apply the following patch on below version of WebLogic-
WebLogic Server 12.2.1.1 - Patch 26519400
Opatch version - 13.9
I am getting the below error:
OPatch detects the Middleware Home as "D:\iAS_12c"
Verifying environment and performing prerequisite checks...
Prerequisite check "CheckActiveFilesAndExecutables" failed.
The details are:
Following files are active :
UtilSession failed: Prerequisite check "CheckActiveFilesAndExecutables" failed.
Log file location: D:\iAS_12c\cfgtoollogs\opatch\opatch2022-11-18_14-42-41PM_1.l
og
OPatch failed with error code = 73
I am trying to apply a patch for vulnerabilities.

Cargo cannot download dependencies

I'm trying to build local Rust projects with dependencies from various crates using Rust 1.35.0 on Windows 10 x64. Every time I try to run cargo build or cargo run the following error message appears.
error: failed to download from `https://crates.io/api/v1/crates/nom/5.0.0/download`Caused by: [35] SSL connect error (schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.)
I've tried this with several other crates apart from nom and got exactly the same error message with exception of crate name and version. Reading around pointed me to disabling my firewall, this does not work.
How can it be solved.

downloading from a clickonce deployment

I publish my vb.Net windows form app to a location in the server for users to install on their machines. It starts running for about 32% and errors with the following message: Application validation did not succeed. Unable to continue.
Details:
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of \MyServer\Dep\Databases\Apps\MyApp.application resulted in exception. Following failure messages were detected:
+ Reference in the manifest does not match the identity of the downloaded assembly TsLibGen.exe.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

Error running akka-http-microservice Activator template

Error running akka-http-microservice Activator template
Unable to run example template: akka-http-microservice from the Activator
Project builds, but on running, unable to access URL,
http://localhost:9000/ip/8.8.8.8
getting
'Internal Server Error'
Error on running service: [ERROR] [04/21/2016 12:06:35.506]
[default-akka.actor.default-dispatcher-10]
[akka://default/user/StreamSupervisor-0/flow-2-0-unknown-operation]
Error in stage [One2OneBidi]: Inner stream finished before inputs
completed. Outputs might have been truncated.
(akka.http.impl.util.One2OneBidiFlow$OutputTruncationException$)
This is just with code taken directly from downloaded template *.zip file.
Running on Mac OSx, El Capitan. Running Scala v2.10.3.
Activator v1.3.9
============
(update) still a problem after attempted fix from tutorials support team:
[DEBUG] [04/22/2016 11:58:47.749] [default-akka.actor.default-dispatcher-2] [akka://default/system/IO-TCP/selectors/$a/2] Connection established to [freegeoip.net/104.131.63.168:80]
[ERROR] [04/22/2016 11:58:47.832] [default-akka.actor.default-dispatcher-2] [akka://default/user/StreamSupervisor-0/flow-2-0-unknown-operation] Error in stage [One2OneBidi]: Inner stream finished before inputs completed. Outputs might have been truncated. (akka.http.impl.util.One2OneBidiFlow$OutputTruncationException$)
[ERROR] [04/22/2016 11:58:47.851] [default-akka.actor.default-dispatcher-3] [akka.actor.ActorSystemImpl(default)] Error during processing of request HttpRequest(HttpMethod(GET),http://localhost:9000/ip/8.8.8.8,List(Host: localhost:9000, C
Most responsive help forums related to this issue are:
1) Activator templates
https://github.com/theiterators/akka-http-microservice/issues
2) Akka Mailing List
https://groups.google.com/forum/#!forum/akka-user
I got a response from the company supporting the Activator template tutorials here; and they have fixed the transient issue: https://github.com/theiterators/akka-http-microservice/issues/21
HOWEVER -- I tried running the Service again, and it looks like there's still a problem:
[DEBUG] [04/22/2016 11:58:47.749] [default-akka.actor.default-dispatcher-2] [akka://default/system/IO-TCP/selectors/$a/2] Connection established to [freegeoip.net/104.131.63.168:80]
[ERROR] [04/22/2016 11:58:47.832] [default-akka.actor.default-dispatcher-2] [akka://default/user/StreamSupervisor-0/flow-2-0-unknown-operation] Error in stage [One2OneBidi]: Inner stream finished before inputs completed. Outputs might have been truncated. (akka.http.impl.util.One2OneBidiFlow$OutputTruncationException$)
[ERROR] [04/22/2016 11:58:47.851] [default-akka.actor.default-dispatcher-3] [akka.actor.ActorSystemImpl(default)] Error during processing of request HttpRequest(HttpMethod(GET),http://localhost:9000/ip/8.8.8.8,List(Host: localhost:9000, C
Tried instead to download LATEST tutorial template; and overwrite the one I'd downloaded yesterday. Then rebuilt, rerun that.
NOW the microservice comes up; and it appears to be working! Problem resolved!

Installing SSMS 2014 giving error of DLL required

I'm installing SSMS 2014 but while installing I'm getting below error:-
"There is a problem with this Windows Installer package. A DLL required
for this installation to complete could not be run. Contact your
support personnel or package vendor."
Can anyone tell me what is the problem?
Here is the error log:
Detailed results:
Feature: Management Tools - Complete
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Native Client Access Component
Component error code: 1723
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150528_153228\sqlncli_Cpu64_1.log
Error description: There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723
Feature: Client Tools Connectivity
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Common Files
Component error code: 2331
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150528_153228\sql_common_core_Cpu64_1.log
Error description: The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2331.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sql_common_core.msi%40Do_LogInstallStart_64%402331
Feature: Client Tools SDK
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Native Client Access Component
Component error code: 1723
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150528_153228\sqlncli_Cpu64_1.log
Error description: There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Common Files
Component error code: 2331
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150528_153228\sql_common_core_Cpu64_1.log
Error description: The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2331.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sql_common_core.msi%40Do_LogInstallStart_64%402331
Feature: Management Tools - Basic
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Native Client Access Component
Component error code: 1723
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150528_153228\sqlncli_Cpu64_1.log
Error description: There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723
Feature: SQL Client Connectivity
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Native Client Access Component
Component error code: 1723
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150528_153228\sqlncli_Cpu64_1.log
Error description: There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723
Feature: SQL Client Connectivity SDK
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Native Client Access Component
Component error code: 1723
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150528_153228\sqlncli_Cpu64_1.log
Error description: There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723
I solved this problem by NOT putting in a DEFAULT target server URL when prompted. It is an optional field, so leave it blank, click next, and the installation completes without issue. You can add that link later once the application installs.
Try installing it as administrator. Right click on setup.exe file and click run as administrator.