.
-Original Message-
From: Shawn Dwyer [mailto:[EMAIL PROTECTED]
Sent: Monday, August 18, 2008 11:24 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching fails with 1627
Thanks for the feedback and the helpful links. I've read all of Heath's
blogs a few times
Shawn Dwyer wrote:
So for anyone else running into this issue, apparently one of the causes
could be too many characters in the Id field of the TargetImage element,
which has a max length of 13 characters. The same for the UpgradeImage
element.
Can you file a bug? It sounds like
discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching fails with 1627
Hi,
I'm running into what seems to be a common error on the mailing list,
but
none of the solutions so far have worked for me.
I have 3 basic test patches:
RTM: installs file1
Patch1: targets rtm
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Tony Juricic [EMAIL
PROTECTED]
Sent: Monday, August 18, 2008 8:19 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching fails with 1627
Don't patch the patch!
Always target:
a) only RTM
] [
[EMAIL PROTECTED] On Behalf Of Tony Juricic
[EMAIL PROTECTED]
Sent: Monday, August 18, 2008 8:19 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching fails with 1627
Don't patch the patch!
Always target:
a) only RTM
b) RTM + another (non-patched) full
Hi,
I'm running into what seems to be a common error on the mailing list, but
none of the solutions so far have worked for me.
I have 3 basic test patches:
RTM: installs file1
Patch1: targets rtm, updates launch condition of RTM
Patch2: targets Patch1, updates file1 and installs directory2\file2
PM
To: Huck, Jacob
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patching fails with 1627
Huck, Jacob wrote:
In case someone was looking at a similar issue: basically we
have multiple cab files in a debug install (to contain the pdbs, which
exceed 2GB in many cases
Huck, Jacob wrote:
I was positive the spirit of the msdn doc was saying it would work
with PatchWiz 2.0 /or greater//, /but apparently not. They said
they'd improve the error message (long term) and write up a kb (short
term).
Thanks for the follow-up! It almost makes sense, as PatchWiz 2.0
Huck, Jacob wrote:
In case someone was looking at a similar issue: basically we have
multiple cab files in a debug install (to contain the pdbs, which
exceed 2GB in many cases). When generating the patch, I was leaving
MediaDiskId blank, but in needed to be set to a value greater than the
in the msi's.
Thanks
-jh
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Huck,
Jacob
Sent: Sunday, February 25, 2007 11:03 PM
To: Bob Arnson; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patching fails with 1627
Sounded promising, but unless
Huck, Jacob wrote:
ERROR: Failed to execute a view
ERROR:The Last Error Received is: 1627
ERROR:The Last Error Received is: 1: 2259 2:
c:\temp\~pcw_tmp.tmp\3000.MSI 3: 4:
I've gotten that before when I was use a File/Sequence column of I4; by
default, Patchwiz supplies
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 25, 2007 1:38 PM
To: Huck, Jacob
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patching fails with 1627
Huck, Jacob wrote:
ERROR: Failed to execute a view
ERROR:The Last Error
I'm currently building two varieties of my install, release and debug,
using WiX 3.0. Right now I'm able to successfully create an MSP using
msimsp 4.0 for the release msi's only; when I try to generate a debug
MSP, I get the following error:
ERROR: Failed to execute a view
ERROR:
13 matches
Mail list logo
