[WiX-users] Package download failed in Web Installer
Hi,
I have created two msi file (SampleSetup1 & SampleSetup2) using wix
toolset3.8.
In Installation,SampleSetup1 download successfully,but While downloading a
SampleSetup2,it shown below error.
(Note:Two msi were download successfully in another machine.)
Error 0x80072ee2: Failed while reading from internet.
Error 0x80072ee2: Failed while reading from internet and writing to:
C:\Users\shant\AppData\Local\Temp\{0c8156b4-ccb1-499f-bbd0-7478920ba13d}\SampleSetup2
Error 0x80072ee2: Failed to download URL: http://dummy.msi
Error 0x80072ee2: Failed attempt to download URL: 'http://dummy.msi' to:
'C:\Users\shant\AppData\Local\Temp\{0c8156b4-ccb1-499f-bbd0-7478920aa13d}\SampleSetup2'
Error 0x80072ee2: Failed to acquire payload from: 'http://dummy.msi' to
working path:
'C:\Users\shant\AppData\Local\Temp\{0c8156b4-ccb1-499f-bbd0-7478920aa13d}\SampleSetup2'
Failed to acquire payload: WindowsFormsSamplesPackage to working path:
C:\Users\shant\AppData\Local\Temp\{0c8156b4-ccb1-499f-bbd0-7478920aa13d}\SampleSetup2,
error: 0x80072ee2.
Error 0x80072ee2: Cache thread exited unexpectedly.
can you please share why this kind of error occurred ?
Please share any idea on this.
Regards,
Mohamed Yasir K
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Package-download-failed-in-Web-Installer-tp7597807.html
Sent from the wix-users mailing list archive at Nabble.com.
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Adding Registry Entries in both 32 and 64 Bits
Thanks for your answer John. I am trying something similar in my bootstrapper code. This is what I wrote: But with this I will still need to create 2 Installers, one for 32 bit and one for 64 bit. The 64 bit one I made works fine in a 64 bit OS and Chrome 32 or 64 bit but does not work on a 32 bit OS. Is it possible to have one universal installer which will hold good in all cases? Please let me know. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-Registry-Entries-in-both-32-and-64-Bits-tp7597760p7597808.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Package download failed in Web Installer
What's the difference between the two machines? Firewall? Different network
configuration/subnet?
On Fri, Nov 7, 2014 at 7:15 AM, Mohamed Yasir
wrote:
> Hi,
>
> I have created two msi file (SampleSetup1 & SampleSetup2) using wix
> toolset3.8.
>
> In Installation,SampleSetup1 download successfully,but While downloading a
> SampleSetup2,it shown below error.
>
> (Note:Two msi were download successfully in another machine.)
>
> Error 0x80072ee2: Failed while reading from internet.
>
> Error 0x80072ee2: Failed while reading from internet and writing to:
>
> C:\Users\shant\AppData\Local\Temp\{0c8156b4-ccb1-499f-bbd0-7478920ba13d}\SampleSetup2
>
> Error 0x80072ee2: Failed to download URL: http://dummy.msi
>
> Error 0x80072ee2: Failed attempt to download URL: 'http://dummy.msi' to:
>
> 'C:\Users\shant\AppData\Local\Temp\{0c8156b4-ccb1-499f-bbd0-7478920aa13d}\SampleSetup2'
>
> Error 0x80072ee2: Failed to acquire payload from: 'http://dummy.msi' to
> working path:
>
> 'C:\Users\shant\AppData\Local\Temp\{0c8156b4-ccb1-499f-bbd0-7478920aa13d}\SampleSetup2'
>
> Failed to acquire payload: WindowsFormsSamplesPackage to working path:
>
> C:\Users\shant\AppData\Local\Temp\{0c8156b4-ccb1-499f-bbd0-7478920aa13d}\SampleSetup2,
> error: 0x80072ee2.
>
> Error 0x80072ee2: Cache thread exited unexpectedly.
>
> can you please share why this kind of error occurred ?
>
> Please share any idea on this.
>
> Regards,
> Mohamed Yasir K
>
>
>
>
>
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Package-download-failed-in-Web-Installer-tp7597807.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> --
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
"They may forget what you said but they will never forget how you made them
feel." -- Anonymous
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Adding Registry Entries in both 32 and 64 Bits
No. Has to with the way WOW and the Windows Installer Service was implemented. It's not Wix-specific at all. At run time, the VersiontNT64 Burn variable is only defined on 64-bit OS's and you can use this to choose which MSI's to run out of a chain. -- John Merryweather Cooper Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |jocoo...@jackhenry.com -Original Message- From: vikasyv [mailto:vikas@gmail.com] Sent: Friday, November 7, 2014 1:12 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Adding Registry Entries in both 32 and 64 Bits Thanks for your answer John. I am trying something similar in my bootstrapper code. This is what I wrote: But with this I will still need to create 2 Installers, one for 32 bit and one for 64 bit. The 64 bit one I made works fine in a 64 bit OS and Chrome 32 or 64 bit but does not work on a 32 bit OS. Is it possible to have one universal installer which will hold good in all cases? Please let me know. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-Registry-Entries-in-both-32-and-64-Bits-tp7597760p7597808.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] FireDaemon and WiX?
We are using FireDaemon for hosting services, instead of writing our own services. When using the OEM versioin, we need to do all the install ourself, and that we want to automate during the installation of rest of the software, but it seems like we cannot use the normal way using ServiceInstall and ServiceControl, since it have its own way of doing things: http://www.firedaemon.com/manual/index.html?OEMQuickStart Not sure yet if that way is made as an convenience, or if it is possible to use sc.exe etc, but so far we havent found any good way. Have anyone tried that?, or have some clever idea? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/FireDaemon-and-WiX-tp7597811.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: FireDaemon and WiX?
The wix elements use the msi standard tables for things like installing services and registry entries. This provides a better user experience, including rollback support, in contrast to calling an open ended external process like myservice.exe --install. Most of the information needed is in the link provided, but installing the app on a test system using their process and evaluating the result with sc.exe or regedit.exe would provide confirmation of the information needed to use ServiceInstall, etc. Use Heat.exe to generate wix authoring after you install the app using their instructions and export the additional registry keys detailed in the document -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/FireDaemon-and-WiX-tp7597811p7597812.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Localizing Managed BA
Hi, I am trying to support localization for my Managed BA. I generated pseudo localized satellite assembly for en-US. Modified bundle.wxs to include satellite resource dll But I get the error when I run my BA (See below). What am I doing wrong? I even tried to build my BA with compressed property set to "no" on the resource dll payload to see if the file is copied to language specific folder, but that didn't work either. Thanks [101B4:10244][2014-11-07T14:30:19]e000: System.Xaml.XamlObjectWriterException: The invocation of the constructor on type 'Agilent.OpenLAB.Installation.Pages.License.LicensePage' that matches the specified binding constraints threw an exception. ---> System.Resources.MissingSatelliteAssemblyException: The satellite assembly named "Agilent.OpenLAB.Installation.resources.dll, PublicKeyToken=968ccb9b2a5fe74" for fallback culture "en-US" either could not be found or could not be loaded. This is generally a setup problem. Please consider reinstalling or repairing the application. at System.Resources.ManifestBasedResourceGroveler.HandleSatelliteMissing() at System.Resources.ManifestBasedResourceGroveler.GrovelForResourceSet(CultureInfo culture, Dictionary`2 localResourceSets, Boolean tryParents, Boolean createIfNotExists, StackCrawlMark& stackMark) at System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo requestedCulture, Boolean createIfNotExists, Boolean tryParents, StackCrawlMark& stackMark) at System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo culture, Boolean createIfNotExists, Boolean tryParents) at System.Resources.ResourceManager.GetResourceSet(CultureInfo culture, Boolean createIfNotExists, Boolean tryParents) at MS.Internal.Resources.ResourceManagerWrapper.get_ResourceSet() at MS.Internal.Resources.ResourceManagerWrapper.GetStream(String name) at MS.Internal.AppModel.ResourcePart.EnsureResourceLocationSet() at MS.Internal.AppModel.ResourcePart.GetContentTypeCore() at System.IO.Packaging.PackagePart.get_ContentType() at System.Windows.Application.LoadComponent(Object component, Uri resourceLocator) at Agilent.OpenLAB.Installation.Pages.License.WelcomePageView.InitializeComponent() at Agilent.OpenLAB.Installation.Pages.License.LicensePage..ctor() --- End of inner exception stack trace --- -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: Adding Registry Entries in both 32 and 64 Bits
I also deploy both x86 and x64 packages in my bundle. To clarify the use of preprocessor statements in your code snippet would cause the pre-compiler to include only one of the two code fragments at compile time. Probably not what you want. You can create two separate MSI projects for you application, one for x86 and the other for x64, and then create a bundle.exe with a chain that includes both packages. In the bundle you will have two MsiPackage elements with different IDs and in the x86 MsiPackage/@InstallCondition use (NOT VersionNT64). There are a number of examples out there of how to create a single msi project which when built twice produces a x86 MSI and a x64 msi. http://alekdavis.blogspot.com/2011/05/build-32-and-64-bit-installers-using.html There are several things in this sample, which over time I realized could be done differently, but it was a helpful starter. I prefer to use: x64 in the wixproj file, Product/@Id='*' and a single Product/@UpgradeCode since I do not allow both platform variants of my driver on the same target. system. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-Registry-Entries-in-both-32-and-64-Bits-tp7597760p7597814.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Localizing Managed BA
I think you should be putting the en-US satellite assembly in an en-US subfolder (http://msdn.microsoft.com/en-us/library/21a15yht.aspx On Fri, Nov 7, 2014 at 5:15 PM, wrote: > Hi, I am trying to support localization for my Managed BA. I generated > pseudo localized satellite assembly for en-US. > > Modified bundle.wxs to include satellite resource dll > SourceFile="..\Translation\lib\Release\en-US\Agilent.OpenLAB.Installation.resources.dll" > Name="1033\Agilent.OpenLAB.Installation.resources.dll"/> > > But I get the error when I run my BA (See below). What am I doing wrong? > > I even tried to build my BA with compressed property set to "no" on the > resource dll payload to see if the file is copied to language specific > folder, but that didn't work either. > Thanks > > [101B4:10244][2014-11-07T14:30:19]e000: > System.Xaml.XamlObjectWriterException: The invocation of the constructor on > type 'Agilent.OpenLAB.Installation.Pages.License.LicensePage' that matches > the specified binding constraints threw an exception. ---> > System.Resources.MissingSatelliteAssemblyException: The satellite assembly > named "Agilent.OpenLAB.Installation.resources.dll, > PublicKeyToken=968ccb9b2a5fe74" for fallback culture "en-US" either could > not be found or could not be loaded. This is generally a setup problem. > Please consider reinstalling or repairing the application. >at > System.Resources.ManifestBasedResourceGroveler.HandleSatelliteMissing() >at > System.Resources.ManifestBasedResourceGroveler.GrovelForResourceSet(CultureInfo > culture, Dictionary`2 localResourceSets, Boolean tryParents, Boolean > createIfNotExists, StackCrawlMark& stackMark) >at System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo > requestedCulture, Boolean createIfNotExists, Boolean tryParents, > StackCrawlMark& stackMark) >at System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo > culture, Boolean createIfNotExists, Boolean tryParents) >at System.Resources.ResourceManager.GetResourceSet(CultureInfo culture, > Boolean createIfNotExists, Boolean tryParents) >at MS.Internal.Resources.ResourceManagerWrapper.get_ResourceSet() >at MS.Internal.Resources.ResourceManagerWrapper.GetStream(String name) >at MS.Internal.AppModel.ResourcePart.EnsureResourceLocationSet() >at MS.Internal.AppModel.ResourcePart.GetContentTypeCore() >at System.IO.Packaging.PackagePart.get_ContentType() >at System.Windows.Application.LoadComponent(Object component, Uri > resourceLocator) >at > Agilent.OpenLAB.Installation.Pages.License.WelcomePageView.InitializeComponent() >at Agilent.OpenLAB.Installation.Pages.License.LicensePage..ctor() >--- End of inner exception stack trace --- > > -- > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: Localizing Managed BA
I also wanted to comment that ILSpy along with ProcessMon and ProcessExplorer were helpful in sorting these issues out. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Localizing-Managed-BA-tp7597813p7597817.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: Localizing Managed BA
I had similar challenges back when I first created a mba and added
localization about a year ago. I was just learning C# (from a C++
background) and so I was pretty green (and still am with C#). One issue
that I had was that since my mba.dll is hosted in another application, there
seemed to be a conflict with using the default resources.resx, as it was
already used in the host application. I found that I needed to have it in
my project, empty, but also add my strings to new files, in project's
Properties folder mymbaUXRes.en.resx, mymbaUXRes.de.resx etc.
My namespace is:
company.div.app.Properties.myUXRes
I also had to comment out this in my assembly file.
//causes an exception when using Strings.resx
//[assembly: NeutralResourcesLanguage("en-US",
UltimateResourceFallbackLocation.Satellite)]
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Localizing-Managed-BA-tp7597813p7597815.html
Sent from the wix-users mailing list archive at Nabble.com.
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] [SPAM] Re: Package download failed in Web Installer
I sometimes see errors like this when the bundle downloads several packages successfully and starts installing those packages. Then while downloading a later package, one of the earlier packages encounters an error, and starts a rollback. The download process is aborted resulting in errors like these. But the real issue may be in the log of the other package which downloaded successfully and was being installed at the time. Look for another error with an earlier timestamp. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Package-download-failed-in-Web-Installer-tp7597807p7597818.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to suppress the StdBA Bootstrapper UI
Ahh!! That is really in detail and most helpful. Thank you very much for the helpful links and in details. Regards, Sampat -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-suppress-the-StdBA-Bootstrapper-UI-tp7597705p7597819.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Pop up a modify setup DialogBox
Hi All,
I write a bootstrapper application and use “WixStandardBootstrapperApplication”
GUI.
After my bootstrapper application runs a MSI to install device drivers by
calling a custom action dll
, it indicates that installation successfully. But after a few seconds, it pops
up another “Modify Setup”
dialogBox again. I am wondering why this happened.
I checked the log file of the bootstrapper application and found nothing was
wrong. What is the reason that
the bootstrapper application pops up “Modify Setup” dialogbox? How do I stop
the popup of the “Modify Setup”
dialogBox?
Here is the XML code to install and uninstall driver.
(NOT Installed)
Installed AND
REMOVE="ALL"
Installed AND
REMOVE="ALL"
///Custom Action all
[CustomAction]
public static ActionResult UninstallService(Session session)
{
Process process;
int result;
session.Log("Begin to UninstallService");
try
{
if (!bServiceInstalled)
{
return ActionResult.SkipRemainingActions;
}
string InstallDir = GetInstallationFolder(session);
if (InstallDir == string.Empty)
{
session.Log("WARNING!!! in UninstallService: Service not
installed");
return ActionResult.SkipRemainingActions;
}
string servicePath = InstallDir + "HishEp.exe";
session.Log("Exec the following command {0}", servicePath);
process = System.Diagnostics.Process.Start(servicePath, "/uninstall");
process.WaitForExit();
result = process.ExitCode;
}
catch (Exception ex)
{
session.Log("WARNING!!! in UninstallService: {0}", ex.ToString());
ShowMessage(session, ex.ToString());
return ActionResult.Failure;
}
return ActionResult.Success;
}
[CustomAction]
public static ActionResult InstallDrivers(Session session)
{
session.Log("Begin to InstallDrivers");
try
{
string InstallDir = GetInstallationFolder(session);
if (InstallDir == string.Empty)
{
session.Log("WARNING!!! in InstallDrivers: Service not
installed");
return ActionResult.SkipRemainingActions;
}
string UninstallBuffer = "DefaultInstall 128 ";
string SockInfBuffer = UninstallBuffer + InstallDir +
SOCKMON_INF_NAME;
string FileFilterInfBuffer = UninstallBuffer + InstallDir +
MINISPY_INF_NAME;
session.Log("InstallDrivers: start to install socket monitor
driver {0}", SockInfBuffer);
InstallHinfSection(IntPtr.Zero, IntPtr.Zero, SockInfBuffer, 0);
session.Log("InstallDrivers: start to install file filter driver
{0}", FileFilterInfBuffer);
InstallHinfSection(IntPtr.Zero, IntPtr.Zero, FileFilterInfBuffer,
0);
}
catch (Exception ex)
{
session.Log("WARNING!!! in InstallDrivers: {0}", ex.ToString());
ShowMessage(session, ex.ToString());
return ActionResult.Failure;
}
return ActionResult.Success;
}
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
