To give some contradictory feedback:
Installing KB3000988 did not fix the error 1316 issue on my machine.
>From the log:
MSI (s) (5C:94) [10:14:49:895]: SECREPAIR: CryptAcquireContext succeeded
MSI (s) (5C:94) [10:14:49:895]: Determining source type
MSI (s) (5C:94) [10:14:49:896]: Note: 1: 2203
the WiX toolset.
Subject: Re: [WiX-users] KB2918614
This seems to be the fix - I haven't noticed anyone post it here yet:
http://support.microsoft.com/kb/3000988
---
Phil Wilson
Has anyone seen the issue below?
We are deploying MSIs via a remote PowerShell script and last we
0T6
keith.doug...@statcan.gc.ca
Telephone | Téléphone 613-854-5589
Facsimile | Télécopieur 613-951-4674
Government of Canada | Gouvernement du Canada
-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: October-14-14 6:31 PM
To: General discussion about the WiX toolset.
Subject:
This seems to be the fix - I haven't noticed anyone post it here yet:
http://support.microsoft.com/kb/3000988
---
Phil Wilson
On Mon, Sep 29, 2014 at 11:19 AM, roberthyang wrote:
> Aha ! This would explain what we have been seeing: if the install is done
> after KB2918614, then the
Aha ! This would explain what we have been seeing: if the install is done
after KB2918614, then the repair is successful. If the install was done
prior to KB2918614, then the repair for SQL Server CE 3.5 SP2 x64 fails.
The difference in the log is as follows :
MSI (s) (50:CC) [12:30:26:258]: De
That is what I use (and I also use /norestart). I don't have MSUs, just
MSIs, but they now uninstall consistently. Many months ago when I first
implemented this I saw situations where the packages were not removed. I
think that happened when I tried to call the cached version of the bundle
(usin
6 matches
Mail list logo
