It also happens with a clean install in my scenario.
-Original Message-
From: Sascha Sertel [mailto:sascha.ser...@gmail.com]
Sent: 28 August 2014 22:28
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the
default key
Hi all -- we have a bundle containing MsiPackage entries for SQL Server
Compact 3.5 SP2. There are actually two MSI's: x86 and x64. The latter
seems to have problems being repaired via our bootstrapper (standard burn
bootstrapper application, no custom code). I don't want to further hijack
anoth
I got a very similar issue on one of my client's machines; the fix was to
un-install the KB update. We had antivirus disabled. We could not install
anything on that machine until we un-installed the KB update. The error we
got from the installer was something like "error: object not found", and
I got that once when some McAfee product or other was trying to install itself
at the same time (we run its AV and a few other things on my target machines),
and a few months ago - well before this update.
Somehow also when that happens one gets the McAfee product details in the
install log cre
I just tried it with KB2918614 removed, and got a different error, "Error
1316.A network error occurred while attempting to read from the file" :
Action start 14:45:54: PublishFeatures.
MSI (s) (7C:8C) [14:45:54:217]: Doing action: PublishProduct
Action ended 14:45:54: PublishFeatures. Return valu
@Neil: That's good to know, and great to have an easy repro, I'm sure
Microsoft will need that to come up with a fix. But this still only affects
the upgrade case, or does it happen on first install for you as well? In my
case it's only on (minor) upgrade, fresh install works fine.
This makes me w
Our install isn't any of those :-)
WiX 3.7, Per Machine, No bootstrapper, No managed CA
I can reproduce the issue with a very minimal MSI, no UI, only installs 1 file.
Neil
-Original Message-
From: Sascha Sertel [mailto:sascha.ser...@gmail.com]
Sent: 28 August 2014 21:31
To: General dis
@Neil: Yes, for us removing KB2918614 fixed the error and got us back to
working state. No other workaround known at this time.
I've been trying to figure out why this only seems to affect certain MSIs.
Here some parameters that might be relevant:
- WiX 3.8
- per-User install, no elevated privileg
We just started seeing a possibly-related error recently. We have a burn
bootstrapper in Wix 3.8 and among the bundle MSI's is SQL Server Compact SP2
x64 (SSCERuntime-ENU-x64.msi). When the bootstrapper attempts to repair the
application, the repair of SQL Server Compact SP2 x64 fails with "Error
I think it is somehow related to the user context it is running as, in our case
we using PowerShell remoting to install the MSI (using msiexec). The bit I have
never seen before are the SECREPAIR messages, these only get triggered for us
when we do this remote deployment. Although it works with
I have seen that reported but I think it is slightly different. Does removing
kb2918614 fix it?
-Original Message-
From: Matt O'Connell [mailto:techsupport...@gmail.com]
Sent: 26 August 2014 11:35
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcqu
For now, you could always write a little wrapper exe yourself that receives
the InstallCommand and UninstallCommand and does the right thing and
include the real setup.exe as a payload of that package.
On Thu, Aug 28, 2014 at 10:48 AM, Hoover, Jacob
wrote:
> Gut feel is if we can get the uninst
Gut feel is if we can get the uninstall key info, we should be able to get the
path from there (and optional parameters).
-Original Message-
From: Rob Mensching [mailto:r...@firegiant.com]
Sent: Thursday, August 28, 2014 10:35 AM
To: General discussion about the WiX toolset.
Subject: Re:
Yeah, we should talk about the best way to implement this on wix-devs. IIRC,
with InnoSetup there are a couple options we could implement.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Orig
And assuming we could reliably capture the path to the uninstaller it shouldn't
be hard to implement. Not sure if it would be a 3.x, but certainly a 4.x thing.
-Original Message-
From: Rob Mensching [mailto:r...@firegiant.com]
Sent: Thursday, August 28, 2014 10:19 AM
To: General discussi
Not today. Good feature request though.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Carlier, Frederik [mailto:frederik.carl...@jamosolutions.com]
Sent: Thurs
Hi,
I'm using Burn to redistribute my installer and most of the dependencies. That
works well, except for one dependency which is packaged using InnoSetup.
The catch here is that while the InstallCommand is just about passing
parameters to the source file, to uninstall, I need to run an uninstal
Is there a wiki article or anything on security best practices where this stuff
could be captured a little more formally?
-Original Message-
From: Sean Hall [mailto:r.sean.h...@gmail.com]
Sent: August-27-14 6:44 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Bu
Hi,
I'm building a MBA and I noticed that I should probably make calls to
SendEmbeddedProgress/SendEmbeddedError when my bootstrapper is run in
UI-less/embedded mode (during the uninstallation of the previous version in an
uninstallation, for instance). However, there are three progress events o
Thank you. I will look at that. I have not actually done any of the mba
implementation yet as I have been focused on the underlying Bundle/MSI
behavior, and getting the ServiceInstall and XmlConfig pieces figured out.
--
View this message in context:
http://windows-installer-xml-wix-toolset.6
20 matches
Mail list logo
