[WiX-users] Failed to extract all files from container
Hi Neil, did the underlying msi files change? Are those signed correctly? I had the same problem and didn't get it to work with the commands you posted. Did you try overriding the build targets in your .wixproj file instead of using those commands as explained here too: http://wix.sourceforge.net/manual-wix3/insignia.htm ? Sabine -Ursprüngliche Nachricht- Von: Neil Sleightholm [mailto:n...@x2systems.com] Gesendet: Donnerstag, 15. November 2012 23:34 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] Failed to extract all files from container This has got something to do with signing. If I sign on my dev machine everything is ok but on the build machine it gives this error. I am using this process if it is relevant: insignia -ib bundle.exe -o engine.exe ... sign engine.exe insignia -ab engine.exe bundle.exe -o bundle.exe ... sign bundle.exe I use the same build process on both machines, on the build machine it was ok but is now failing. As far as I can tell nothing has changed on the build machine. Neil -Original Message- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: 15 November 2012 16:52 To: General toolset. (wix-users@lists.sourceforge.net) Subject: [WiX-users] Failed to extract all files from container My install has been working fine for a lot of builds and then last night's build generates this error when we run it: [0674:0A1C][2012-11-15T16:42:56]: Prompt for source of package: NetFx40Redist, payload: NetFx40Redist, path: C:\Users\Neil Sleightholm\Desktop\Redist\dotNetFx40_Full_x86_x64.exe [0674:0A1C][2012-11-15T16:42:56]: Acquiring package: NetFx40Redist, payload: NetFx40Redist, download from: http://go.microsoft.com/fwlink/?LinkId=247729 [0CF4:0770][2012-11-15T16:44:52]: Verified acquired payload: NetFx40Redist at path: C:\ProgramData\Package Cache\.unverified\NetFx40Redist, moving to: C:\ProgramData\Package Cache\58DA3D74DB353AAD03588CBB5CEA8234166D8B99\Redist\dotNetFx40_Full_x86_x64.exe. [0674:03D8][2012-11-15T16:44:56]: Error 0x80004005: Failed to extract all files from container. [0674:0A1C][2012-11-15T16:44:56]: Error 0x80004005: Faild to begin and wait for operation. [0674:0A1C][2012-11-15T16:44:56]: Error 0x80004005: Failed to extract payload: a1 from container: WixAttachedContainer [0674:0A1C][2012-11-15T16:44:56]: Failed to extract payloads from container: WixAttachedContainer to working path: C:\Users\Neil Sleightholm\Desktop\Setup.exe, error: 0x80004005. [0CF4:0770][2012-11-15T16:44:56]: Removing cached package: NetFx40Redist, from path: C:\ProgramData\Package Cache\58DA3D74DB353AAD03588CBB5CEA8234166D8B99\ [0674:027C][2012-11-15T16:44:56]: Error 0x80004005: Failed while caching, aborting execution. Any ideas what might be causing this or how to debug it? Regards Neil Neil Sleightholm X2 Systems Limited n...@x2systems.commailto:n...@x2systems.com -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WIC as a prereq before .NET 4.0 in Burn with custom BA
Hi Daniel, We had the exactly same problem. What we did to solve is, we created a second bootstrapper project called PrereqBootstrapper with the following content in Bundle.wxs (most of it is copied from the Wix NetFxExtension): Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Bundle Name=PrereqBootstrapper Version=1.0.0.0 Manufacturer=Microsoft? UpgradeCode=put your upgradecode here BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.RtfLicense / ?define NetFx40WebLink = http://go.microsoft.com/fwlink/?linkid=182805 ? ?define NetFx40RedistLink = http://go.microsoft.com/fwlink/?LinkId=247729 ? ?define NetFx40ClientWebLink = http://go.microsoft.com/fwlink/?linkid=182804 ? ?define NetFx40ClientRedistLink = http://go.microsoft.com/fwlink/?LinkId=247730 ? ?define NetFx40EulaLink = http://go.microsoft.com/fwlink/?LinkID=188993 ? Chain ExePackage InstallCommand=/q /norestart PerMachine=yes Id=WIC Vital=yes Permanent=yes SourceFile=..\windows_imaging_component\wic_x86_deu.exe / ExePackage InstallCommand=/q /norestart RepairCommand=/q /norestart UninstallCommand=/uninstall PerMachine=yes DetectCondition=NETFRAMEWORK40 Id=NetFx40ClientWeb Vital=yes Permanent=yes Protocol=netfx4 DownloadUrl=$(var.NetFx40ClientWebLink) Compressed=no Name=redist\dotNetFx40_Client_setup.exe After=WIC RemotePayload Size=889416 Version=4.0.30319.1 ProductName=Microsoft .NET Framework 4 Client Profile Description=Microsoft .NET Framework 4 Client Profile Setup CertificatePublicKey=672605E36DD71EC6B8325B91C5FE6971390CB6B6 CertificateThumbprint=9617094A1CFB59AE7C1F7DFDB6739E4E7C40508F Hash=06BECADB92A5FCCA2529C0B93687C2A0C6D0D610/ /ExePackage /Chain /Bundle /Wix Afterwards we added this to our main bootstrapper: Chain PackageGroupRef Id='Prereq' / your packages here/ /Chain /Bundle Fragment WixVariable Id=WixMbaPrereqPackageId Value=Prereq / WixVariable Id=WixMbaPrereqLicenseUrl Value=$(var.NetFx40EulaLink) / PackageGroup Id=Prereq ExePackage InstallCommand=/q /norestart /ChainingPackage quot;[WixBundleName]quot; RepairCommand=/q /norestart /repair /ChainingPackage quot;[WixBundleName]quot; UninstallCommand=/uninstall /q /norestart /ChainingPackage quot;[WixBundleName]quot; DetectCondition=NETFRAMEWORK40 PerMachine=yes Id=Prereq Vital=yes Permanent=yes SourceFile=..\PrereqBootstrapper.exe/ /PackageGroup /Fragment I have tested this in a Windows Server 2003 R2 environment and it installed both, WIC and .NET4. It still has a problem, though: The progress isn't shown correctly in UI. Maybe you can figure this out yourself and let me know if you find the solution. Best regards, Sabine Frauenhoffer Release Engineer -- Haufe-Lexware GmbH Co. KG Munzinger Str. 9, D-79111 Freiburg Tel: +49 761 898-5385 E-Mail: sabine.frauenhof...@haufe-lexware.com Internet: http://www.haufe-lexware.com Kommanditgesellschaft, Sitz und Registergericht Freiburg, HRA 4408 Komplementäre: Haufe-Lexware Verwaltungs GmbH, Sitz und Registergericht Freiburg, HRB 5557; Martin Laqua Geschäftsführung: Isabel Blank, Jörg Frey, Birte Hackenjos, Jens Köhler, Matthias Mühe, Markus Reithwiesner, Joachim Rotzinger, Dr. Carsten Thies Beiratsvorsitzende: Andrea Haufe -- » http://www.haufe.de/shop « -- -Ursprüngliche Nachricht- Von: Daniel Bruce [mailto:daniel.br...@prediktor.no] Gesendet: Montag, 8. Oktober 2012 09:31 An: General discussion for Windows Installer XML toolset.(wix-users@lists.sourceforge.net) Betreff: [WiX-users] WIC as a prereq before .NET 4.0 in Burn with custom BA Hello, We are attempting to roll out a managed bootstrapper that depends on .NET 4.0. On some platforms this requires WIC (Windows Imaging Component) to be installed prior to running the .NET 4.0 installer, which is giving us some issues. We have tried to solve this issue in a few ways, but none have worked, so I posted to stack overflow about it. Nobody has responded so far, so I'm crossposting here to see if anybody has any input. If so, it would be nice if you could take a look at the SO question, which has all the details, and perhaps shoot me an answer either there or here.
Re: [WiX-users] Custom Bootstrapper Application: Problem whentrying todetect if Bundle is already installed
Thanks for your advises.
There are two problems with WixBundleInstalled:
1) I have to distinguish 3 states: version is same, current version is lower
than installed version, current version is higher than installed version. But
WixBundleInstalled only has value 0 or 1.
2) Which is even worse: I can't get this to work. I tried
var x =
_bootstrapperApplication.Engine.StringVariables[WixBundleInstalled];
and
var y =
_bootstrapperApplication.Engine.NumericVariables[WixBundleInstalled];
Both returned 0. When I handle the DetectRelatedBundle event however, I see
that the bundle is already installed in the current version (which is
correct)...
-Ursprüngliche Nachricht-
Von: Rob Mensching [mailto:r...@robmensching.com]
Gesendet: Freitag, 28. September 2012 04:53
An: General discussion for Windows Installer XML toolset.
Betreff: Re: [WiX-users] Custom Bootstrapper Application: Problem whentrying
todetect if Bundle is already installed
The wixstdba uses WixBundleInstalled variable to determine maintenance mode. I
would recommend doing the same.
On Thu, Sep 27, 2012 at 4:03 PM, Brian C briancoving...@yahoo.com wrote:
If you have an msi which is always installed, you could check the
version of it in the DetectRelatedMsiPackage callback. You have
access to both the major and minor version in the event argument.
From: Frauenhoffer, Sabine sabine.frauenhof...@haufe-lexware.com
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent: Thursday, September 27, 2012 8:48 AM
Subject: Re: [WiX-users] Custom Bootstrapper Application: Problem
whentrying todetect if Bundle is already installed
I tried that one already. It always returned 0 no matter what version
my bundle had.
-Ursprüngliche Nachricht-
Von: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Gesendet: Donnerstag, 27. September 2012 15:36
An: General discussion for Windows Installer XML toolset.
Betreff: Re: [WiX-users] Custom Bootstrapper Application: Problem
whentrying todetect if Bundle is already installed
Could you use the built-in variable WixBundleInstalled instead ? I'm
not sure if that's version specific or not. It might be worth a look.
-Original Message-
From: Frauenhoffer, Sabine
[mailto:sabine.frauenhof...@haufe-lexware.com]
Sent: 27 September 2012 14:13
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Custom Bootstrapper Application: Problem when
trying todetect if Bundle is already installed
Hi there,
I have a problem when trying to detect whether my Bundle is already
installed. My usecase is as follows:
I am creating a bundle with a custom UI. On startup I need to check
whether my bundle is already installed in the exactly same version to
determine if I have to show the maintenance page (if the versions
match), to block installation(if a newer version is already installed)
or show the install page (else). So I make a call to
_bootstrapperApplication.Engine.Detect();
My first idea now was to handle the event
_bootstrapperApplication.DetectRelatedBundle and somehow determine
whether the productcodes are different. This is not possible as I
can't get the product code of the bundle that is going to be installed.
Then I thought it might be an idea, to check for some package which is
unique for my product. So I added the line
_bootstrapperApplication.DetectPackageComplete = DetectedPackage; (see
below) but it doesn't work as I expected:
private void DetectedPackage(object sender,
DetectPackageCompleteEventArgs e)
{
PackageState.Obsolete
if (e.PackageId.Equals(mypackage,
StringComparison.Ordinal))
{
_state = (e.State == PackageState.Present) ?
InstallationState.DetectedPresent : InstallationState.DetectedAbsent;
}
}
-If for example version 2.8 is installed and the Package in my
Bundle now has version 2.7 it returns PackageState.Absent (or Obsolete?
I can't reproduce it at the moment) which is just fine
-If version 2.8 is installed and the Package in my Bundle now has
version 2.8, too, it syas e.State = PackageState.Present which is
correct, too.
-But if version 2.8 is installed and the Package in my Bundle now
has version 2.9, I get e.State = PackageState.Present and would show
the maintenance page although I would need to show install page and
install the newer version.
Is this intended or is it a bug? Am I getting something wrong?
What I am doing as a workaround is, on DetectRelatedBundle event I
make some very ugly version comparison. Is there any other option?
Any help appreciated, thanks in advance!
Regards,
Sabine
--
---
-
Everyone hates slow websites. So do we.
Make your web apps
[WiX-users] Custom Bootstrapper Application: Problem when trying to detect if Bundle is already installed
Hi there,
I have a problem when trying to detect whether my Bundle is already
installed. My usecase is as follows:
I am creating a bundle with a custom UI. On startup I need to check
whether my bundle is already installed in the exactly same version to
determine if I have to show the maintenance page (if the versions
match), to block installation(if a newer version is already installed)
or show the install page (else). So I make a call to
_bootstrapperApplication.Engine.Detect();
My first idea now was to handle the event
_bootstrapperApplication.DetectRelatedBundle and somehow determine
whether the productcodes are different. This is not possible as I can't
get the product code of the bundle that is going to be installed.
Then I thought it might be an idea, to check for some package which is
unique for my product. So I added the line
_bootstrapperApplication.DetectPackageComplete = DetectedPackage; (see
below) but it doesn't work as I expected:
private void DetectedPackage(object sender,
DetectPackageCompleteEventArgs e)
{
PackageState.Obsolete
if (e.PackageId.Equals(mypackage,
StringComparison.Ordinal))
{
_state = (e.State == PackageState.Present) ?
InstallationState.DetectedPresent : InstallationState.DetectedAbsent;
}
}
-If for example version 2.8 is installed and the Package in my
Bundle now has version 2.7 it returns PackageState.Absent (or Obsolete?
I can't reproduce it at the moment) which is just fine
-If version 2.8 is installed and the Package in my Bundle now has
version 2.8, too, it syas e.State = PackageState.Present which is
correct, too.
-But if version 2.8 is installed and the Package in my Bundle now
has version 2.9, I get e.State = PackageState.Present and would show the
maintenance page although I would need to show install page and install
the newer version.
Is this intended or is it a bug? Am I getting something wrong?
What I am doing as a workaround is, on DetectRelatedBundle event I make
some very ugly version comparison. Is there any other option?
Any help appreciated, thanks in advance!
Regards,
Sabine
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://ad.doubleclick.net/clk;258768047;13503038;j?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom Bootstrapper Application: Problem whentrying todetect if Bundle is already installed
I tried that one already. It always returned 0 no matter what version my bundle
had.
-Ursprüngliche Nachricht-
Von: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Gesendet: Donnerstag, 27. September 2012 15:36
An: General discussion for Windows Installer XML toolset.
Betreff: Re: [WiX-users] Custom Bootstrapper Application: Problem whentrying
todetect if Bundle is already installed
Could you use the built-in variable WixBundleInstalled instead ? I'm not sure
if that's version specific or not. It might be worth a look.
-Original Message-
From: Frauenhoffer, Sabine [mailto:sabine.frauenhof...@haufe-lexware.com]
Sent: 27 September 2012 14:13
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Custom Bootstrapper Application: Problem when trying
todetect if Bundle is already installed
Hi there,
I have a problem when trying to detect whether my Bundle is already installed.
My usecase is as follows:
I am creating a bundle with a custom UI. On startup I need to check whether my
bundle is already installed in the exactly same version to determine if I have
to show the maintenance page (if the versions match), to block installation(if
a newer version is already installed) or show the install page (else). So I
make a call to _bootstrapperApplication.Engine.Detect();
My first idea now was to handle the event
_bootstrapperApplication.DetectRelatedBundle and somehow determine whether the
productcodes are different. This is not possible as I can't get the product
code of the bundle that is going to be installed.
Then I thought it might be an idea, to check for some package which is unique
for my product. So I added the line
_bootstrapperApplication.DetectPackageComplete = DetectedPackage; (see
below) but it doesn't work as I expected:
private void DetectedPackage(object sender,
DetectPackageCompleteEventArgs e)
{
PackageState.Obsolete
if (e.PackageId.Equals(mypackage,
StringComparison.Ordinal))
{
_state = (e.State == PackageState.Present) ?
InstallationState.DetectedPresent : InstallationState.DetectedAbsent;
}
}
-If for example version 2.8 is installed and the Package in my
Bundle now has version 2.7 it returns PackageState.Absent (or Obsolete?
I can't reproduce it at the moment) which is just fine
-If version 2.8 is installed and the Package in my Bundle now has
version 2.8, too, it syas e.State = PackageState.Present which is correct, too.
-But if version 2.8 is installed and the Package in my Bundle now
has version 2.9, I get e.State = PackageState.Present and would show the
maintenance page although I would need to show install page and install the
newer version.
Is this intended or is it a bug? Am I getting something wrong?
What I am doing as a workaround is, on DetectRelatedBundle event I make some
very ugly version comparison. Is there any other option?
Any help appreciated, thanks in advance!
Regards,
Sabine
-
-
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics Download AppDynamics Lite for free
today:
http://ad.doubleclick.net/clk;258768047;13503038;j?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires
that you delete it without acting upon or copying any of its contents, and we
further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY,
UK.
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics Download AppDynamics Lite for free
today:
http://ad.doubleclick.net/clk;258768047;13503038;j?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://ad.doubleclick.net/clk;258768047;13503038;j?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
