search

wixtoolset / issues

WiX Toolset Issues Tracker
http://wixtoolset.org/
129 stars 36 forks source link

PerfCounterManifest extension fails to load Manifests on upgrades when RemoveExisting products is scheduled after InstallFinalize #4462

Open wixbot opened 10 years ago

wixbot commented 10 years ago

We are using PerfCounterManifest from the Util Extension to install the Performance counter Manifests in our Wix 3.8 installer. We had observed that our upgrades had been failing when the performance counter was being loaded.

The following lines were seen in the installation log:

CAQuietExec: "lodctr.exe" /m:"C:\Program Files (x86)\Application1\Application1PerfCountersManifest.xml" "C:\Program Files (x86) \Application1" CAQuietExec:
CAQuietExec: Error: Unable to install performance counters in C:\Program Files (x86)\Application1\Applicaion1PerfCountersManifest.xml, error code is 13 CAQuietExec: Error 0x8007000d: Command line returned an error. CAQuietExec: Error 0x8007000d: CAQuietExec Failed CustomAction RegisterPerfmonManifest returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) MSI (s) (64:64) [09:35:31:334]: User policy value 'DisableRollback' is 0 MSI (s) (64:64) [09:35:31:334]: Machine policy value 'DisableRollback' is 0 Action ended 09:35:31: InstallFinalize. Return value 3.

RemoveExisting products in our installer was scheduled after InstallFinalize. So the Performance counter Manifests in our upgraded installer were being loaded before the one's from the previous build were unloaded. We scheduled our RemoveExisting products action between InstallValidate and InstallInitialize to handle this and now our upgrades don't fail.

Could this possibly mean the PerfCounterManifest extension handling while install of Performance counter Manifests during upgrades may need some work?

Originally opened by an.animesh

wixbot commented 10 years ago
  1. We should doc this limitation.
  2. Investigate manifest in Binary table (if no other files are needed).
  3. Otherwise, block. Maybe?

Release changed from v3.8 to v3.x

AdrianoModa commented 6 years ago

I did two things:

  1. un-checking "Event tracing(ETW)"
  2. And services.msc enabled 'Volume Shadow Copy' service I put automatic

I tried all but it´s fix to me. I hope that help you.