Did you ever find a fix to this, or does anyone else know what to do about
it?
Thanks,
Rob
From John Leung, on 01 Oct 2010:
-
I notice that during installation on a Windows 7 machine, if I minimized my
install Progress Dialog box,
then this ExitDialog will
Can you post a full install log somewhere - attachments tend to get deleted by
the mailing system ?
Also the exact error you get when you try and start the service.
You may need to enter a bug.
-Original Message-
From: Stephen I. Woolhead [mailto:s...@gtl.biz]
Sent: 16 January 2014
You can use Burn to chain together 3rd party pre-requisites and your
MSI(s). Detecting hotfixes is the tricky part. I believe the cannonical
way to do so is via WMI, which you can do if you write your own
bootstrapper application (BA) for Burn, but if you only want to use what
comes out of the
There's a predefined exepackage in wix; put this in chain: PackageGroupRef
Id=NetFx40ClientRedist/ This installs silently with progress in same window.
Or if you want to create your own exe package use Protocol=netfx4 and I think
InstallCommand to specify command line parameters like quiet
OK, here are the log files, also a couple of screen shots.
https://gtl.sharefile.com/d/sbf6c4368f35490e9
ServiceManager.png - Service manager after install
StartError.png - Error we get when attempting to start service
ResetViaUI.png - Service manager after we reset the logon account via the
Hello,
is it just me, who thinks that the votive Paths page looks like a redraw
error?
There are no labels... This is the same in VS2012 and VS 2013.
Bernd
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7591851/jy63ex4jm5.png
--
View this message in context:
Opps, wrong link in message below.
Correct one is:
https://gtl.sharefile.com/d/s9ec51dd7d1a4dd09
Stephen.
-Original Message-
From: Stephen I. Woolhead [mailto:s...@gtl.biz]
Sent: 17 January 2014 13:18
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Problem with
Thanks. It seems that we can treat 4.0.3 update in similar manner as netfx4.
First tests show that it is working as expected.
On Friday, January 17, 2014 1:56 PM, Wesley Manning wmann...@dynagen.ca wrote:
There's a predefined exepackage in wix; put this in chain: PackageGroupRef
Sorry I thought you were talking about 4.0. Did not read carefully.
-Original Message-
From: Goran Malovic [mailto:malov...@yahoo.com]
Sent: January-17-14 10:49 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Install exe package conditionally in bundle
Thanks.
What OSs do you support? If Vista and above maybe you can install .net 4.5 or
4.5.1. Although more computers would have .net 4.0 and above than 4.5 and I
think you need to have SP2 on Vista (SP1 for .net 4.0) and SP1 on Windows 7.
Or if you need to support XP also you could just install the
Hi,
I am testing the setup on the 2003 Server SP2. Our app requires fx40client to
work, and our setup installs fx40client through bundle chain (PackageGroupRef
Id=NetFx40ClientRedist /). When running the setup, we receive the following
error while installing fx40client: 0x13ec - Asia.
Log
See Bug:
http://sourceforge.net/p/wix/bugs/3058/
and upgrade to WiX 3.8 as the migration arrow suggests, and report back to us.
Quoting Goran Malovic malov...@yahoo.com:
Hi,
I am testing the setup on the 2003 Server SP2. Our app requires
fx40client to work, and our setup installs
I'm not sure there is an issue with the way wix looks the account name up as
you seem to use this in several other places and they are working and the
values returned seem to be right.
The actual error seems to be about the dependency services, which seems to be
msmq according to your install
We are supporting XP sp3 also. We decided not to provide two different
frameworks for the setup, since that would only complicate things, without some
actual benefit. If there is already 4.5 or 4.5.1 installed, we just install our
software. If there is no fx4 (or higher), we install fx5.0 +
I have noticed this behavior with other command line tools like when Rundll32
printui.dll,PrintUIEntry. I just thought it was common behavior unrelated
to wix.
--
View this message in context:
Thanks for the feedback. While the error thrown appears to be a dependant
service error, MSMQ is indeed running and the only change required to allow the
service to start is change the service logon account in service manager UI.
This is not a problem that exists in English or other
Hi, following up on an issue that came up in another thread, we have the need
to enable platform features such as MSMQ during our install. At the moment we
do this during install with dism.exe in a custom action. This so far has
worked well for us but it was hinted this was not ideal.
Does
Disregarding for now the log content, is there actually an issue? Do the
file version rules get applied if the file is installed? Assuming of course
that the component itself is actually being installed rather than
conditioned out or in a feature not being installed. There should be a
FileCopy
The DISM API might be able to do this - it says it works for an online
Windows installation. The key might be to do the DismOpenSession()
with DISM_ONLINE_IMAGE and then use something like DismEnableFeature.
I've never tried it though,
There's often some concern about doing this without making it
I am experiencing the same behavior, although it seems we are complaining
about different issues. I am complaining about wix displaying a message that is
quite different from the message that a standalone fx40 setup shows. I am
already using 3.8v.
On Friday, January 17, 2014 4:46 PM,
In that case, go here:
http://www.microsoft.com/en-us/download/details.aspx?id=32
Download the package and include it in the bootstrapper, making sure
it installs before Fx40
Quoting Goran Malovic malov...@yahoo.com:
I am experiencing the same behavior, although it seems we are
It is just you. I have both VS 2012 and VS2013 installed and WiX 3.8 displays
normally. WiX 3.6 displays normally for VS 2012 (not supported in VS 2013).
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434
It is not a problem with providing WIC, my concern was why wix, while
installing fx40 (as PackageGroupRef), shows different error message than the
standalone fx40 installation. Obviously they experience the same problem, but
provide different output, and I was wondering why.
On Friday,
What is the Error that is Displayed in the Standalone install? The
reason I ask is when I Googled the error in your Error Logs, which led
me to the bug I gave you earlier. Regardless, the error is occurring
because some prerequisite is not met on your OS Install. In short,
are you
No, this is not related to embedding WIC in setup. When I tested setup on
different platforms, on Win2K3 I got the not so understandable message - error
0x13ec Asia. Digging deeper into temp logs we can see more info from the
framework installation log, which lead me to try starting manually
Asia is the (IMHO, incredibly lame) error code that the executable returns
when it fails this way. At the same time it puts better error messages in their
log file. You'll have to ask them why they made that design decision.
-Original Message-
From: Goran Malovic
Ther bug listing that I gave you earlier id the same bug given by the
Fx40 Standalone Installer, You must install the 32 bit WIC before you
run Setup.
The Error is WIC related, and making the WIC a prerequisite BEFORE
Installing Fx40, will alleviate the problem. I.e., if you dont want a
So the real problem is in insufficient information from the fx40 installation.
Thanks...
On Saturday, January 18, 2014 12:07 AM, Carter Young ecyo...@grandecom.net
wrote:
Ther bug listing that I gave you earlier id the same bug given by the
Fx40 Standalone Installer, You must install
@Carter x13ec Asia code is not specific to WIC requirement, it can relate to
many different problems. For example, it can be raised when there is
insufficient free disk space...
And for that reason my question was raised.
On Saturday, January 18, 2014 2:53 AM, Goran Malovic
29 matches
Mail list logo
