Should I report it? Where?
Any clue on how it can get bypassed somehow?
Thanks
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Tuesday, November 18, 2014 16:27
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Problems upgrading to
It's a reported bug (#4601) and seems that it was already solved in #4600.
-Original Message-
From: Majcica, Mario [mailto:mario.majc...@bakerhughes.com]
Sent: Wednesday, November 19, 2014 09:51
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Problems upgrading to
I have looked more closely at the logs and if I try to open the file I want to
change at the point Before=InstallFinalize, then the file does not exist. If I
use After=InstallFinalize then I can open the file but I don't have permission
to write it back to its folder in Program Files.
Any idea
Hi fellows,
Our Bootstrapper consuming Burn is of 70MB, containing Net Framework 4, VC
Runtimes and two more pre-requisites + Product.msi itself. Whenever we
execute it from a network location, it took much longer time to execute
(last time it was almost 40 seconds . We suspect that such delay is
Hi,
I added in Product tag - language=1036 and Codepage=1252 (French).
It's always the same problem !
This is the error message :
... error CNDL0104 : Not a valid source file; detail: Il existe un caractŠre
non valide dans l'encodage donn...
Any ideas ?
Fabrice
-Message d'origine-
On 11/19/2014 2:37 AM, jason.small...@bt.com wrote:
I have looked more closely at the logs and if I try to open the file
I want to change at the point Before=InstallFinalize, then the file
does not exist. If I use After=InstallFinalize then I can open the
file but I don't have permission to
Did you set Package/@SummaryCodepage.
I don't use the Text element (or any MSI UI so can't advise on that, but I
build MSI(s) and mba which supports French.
I added a wxl file to the project and set header of that file as follows:
?xml version=1.0 encoding=utf-8?
WixLocalization Culture=fr-FR
I use an ANT script to generate MSI installer (with custom WXS file).
I don't use Wix project to do that.
So how to connect the WSL file to my WXS file ?
I've this error message :
error LGHT0102 : The localization variable !(loc.xxx) is unknown. Please
ensure the variable is defined.
Better to look at log file than guess what is slow (i.e. add logging to your BA
start and see how long it takes for that to be logged).
There is also the splash screen.
Signed bundles can be very slow because Windows verifies the whole executable.
Agreed. My guys at FireGiant jumped on that one quickly.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Majcica, Mario [mailto:mario.majc...@bakerhughes.com]
Sent:
Hi,
I have to assign some of the Security Rights(SecPol.msc) to the user that i
am going to create on the application install. Luckily i found that WiX does
gives an option to give LogonAsBatchJob and LogonAsService and the util
extension seemed to save me from writing CustomAction.
But,
I can't advise on using an ANT script. I guess I would create a project
using the localization tutorials, and then evaluate how to change the ANT
script to achieve the same results.
When wix setup project is created in VS there is a .wixproj file, and if
localization is added, then there are
What are the remaining ACL's to assign?
--
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: ssmsam
Hi John,
only these 5 are there.
Firstly, user is being created as local and then added to administrators
group. then. There was a c++ dll C.A which performs LSA operations was
used(InstallShield). So i am converting everything in WiX. So making use of
util:user extension.
Thanks,
Sampat
--
Following are the 5 ACEs to be assigned.
1. Access this computer from the network
2. Replace a process level token
3. Act as part of the operating system.
4. Log on as a Batch Job
5. Log on as service.
Regards,
Sampat
--
View this message in context:
There is a user in Turkey that gets the following error simply by double
clicking on the .msi to install a program: The installation source for this
product is not available. Verify that the source exists and that you can
access it.
He is the only user that I know of that is having this problem
Yes, our bundle and msi are both signed. However, I will do the logging
again.
Thanks
On Wed, Nov 19, 2014, 8:53 PM Rob Mensching-7 [via Windows Installer XML
(WiX) toolset] ml-node+s687559n7598089...@n2.nabble.com wrote:
Better to look at log file than guess what is slow (i.e. add logging
After a lot of advice from this group, I implemented some functionality where I
encrpyt part of a file that is installed. I do this with a deferred custom
action.
Now it won't uninstall. If I remove the custom action then it uninstalls.
How do I rollback this action? If a full rollback will
After a lot of advice from this group, I implemented some functionality where I
encrpyt part of a file that is installed. I do this with a deferred custom
action.
Now it won't uninstall. If I remove the custom action then it uninstalls.
How do I rollback this action? If a full rollback will
I think you may have replied to the wrong e-mail.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SOURCEMGMT-Failed-to-resolve-source-MainEngineThread-is-returning-1612-tp7598095p7598100.html
Sent from the wix-users mailing list archive at
A !*$@
You are right.
From: David Fritch [dfri...@ldschurch.org]
Sent: 19 November 2014 17:42
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How do I rollback a file change custom action
I think you may have replied to the wrong
Hi John,
Do you suggest me to use the C.A (an old C++ dll C.A which performs LSA
operations. to achieve this).
Regards,
Sampat
--
View this message in context:
Is the GUID in the log the same as the product code of the MSI you are trying
to install? (IE, is the MSI already installed on his machine?) If so, you may
need to recache the package, then do an uninstall.
Is this MSI a pre-user install? If so you could dig into the registry
It's difficult to tell from that log fragment, but it's vaguely
possible that the product has already been installed and as a result
Windows will go seek out the original MSI file. Otherwise, that
location might be accessible to the user account but not the system
account, so it can be started by
Yes you can change the guids in a major upgrade with the caveat that
you should do the RemoveExistingProducrs early in the process, such as
afterInstallInitialize. The issue is that you don't want to be doing
an upgrade with REP at the end where there may be differing guids for
the same resources.
Hi John,
Is there any way in wix to assign additional local securities ?
Regards,
Sampat
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Assigning-User-rights-Security-Policies-to-the-application-user-tp7598091p7598105.html
Sent from the
Hello Everyone and good day,
As part of our automated build process I back up all generated .wixpdb files.
I'm just wondering how useful these are when debugging a crash or hang of an
MSI when given a dump file from a customer. Can they be used at all? I need
the .wixpdb files for
Thanks for your comments.
It looks like I cannot find the value 2CF25F13-12F8-4B54-AC62-0F29F54E4F54
in my .wxs file. I am guessing it is a mistake to leave the Product Id=*
as an asterisk? (I inherited this file from a previous developer and am
still very new to WiX.)
Is the GUID in the log
Today: patching. Future: ?
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Tunney, Stephen [mailto:stephen.tun...@nuance.com]
Sent: Wednesday, November 19, 2014 10:32 AM
They can be used in patch generation. Other than that, I haven't found them
very useful.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
You may have to be more explicit. I suspect that it's not the
installer that's changing the file - it's your code in a custom
action. An elevated install can write data pretty much everywhere.
However an impersonated custom action running from that install will
not be elevated and therefore cannot
Yes, but at a much lower level.
See util:PermissionEx
For users, some permissions are set in the util:User element.
I don't set or clear GPO during an install because: 1) they'll generally roll
right back in; and 2) removing a GPO doesn't necessarily remove the
restrictions it imposes.
--
You can look in the MSI file for the ProductCode in the Property
table. If you're new to this, get hold of Orca from the Windows
SDK/Kit. It's useful to see inside MSI files. Instead maybe useful
also.
---
Phil Wilson
On Wed, Nov 19, 2014 at 10:35 AM, David Fritch
..I think I got spell corrected. The tool is called Insted .
---
Phil Wilson
On Wed, Nov 19, 2014 at 10:47 AM, Phil Wilson phildgwil...@gmail.com wrote:
You can look in the MSI file for the ProductCode in the Property
table. If you're new to this, get hold of Orca from the
+1 for InstEd, it just seems easier to use for me.
-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: Wednesday, November 19, 2014 12:47 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SOURCEMGMT: Failed to resolve source MainEngineThread
Thanks everyone for the input. This at least gives me a few more tools to
look into the problem to try and diagnose what the issue could be.
I just barely found out from the customer that the temporary solution I sent
him has worked. Bascially, I created a new installer just for him. I
Don't tease me like that, Rob! :)
Stephen Tunney
Nuance Communications, Inc.
Solutions Architect, Imaging Division
Waterloo, Ontario, Canada
stephen.tun...@nuance.com
519-880-7463Office
NUANCE.COM
The experience speaks for itself (tm)
-Original Message-
From: Rob Mensching
Thanks everyone for the input. This at least gives me a few more tools to look
into the problem to try and diagnose what the issue could be.
I just barely found out from the customer that the temporary solution I sent
him has worked. Bascially, I created a new installer just for him. I
After a lot of advice from this group, I implemented some functionality where
I
encrpyt part of a file that is installed. I do this with a deferred custom
action.
Now it won't uninstall. If I remove the custom action then it uninstalls.
That's not surprising. When you modify a file
No, the only User Rights supported by WiX today are the
LogonAsBatchJob and LogonAsService
rights. It looks like there was a feature request for this
http://wixtoolset.org/issues/533/, but I can't find the issue that this is
supposed to be a duplicate of.
On Wed, Nov 19, 2014 at 12:37 PM, John
Found it: http://wixtoolset.org/issues/1938/
On Wed, Nov 19, 2014 at 3:21 PM, Sean Hall r.sean.h...@gmail.com wrote:
No, the only User Rights supported by WiX today are the LogonAsBatchJob
and LogonAsService rights. It looks like there was a feature request for
this
Ahh!! Yes. Thanks for letting this known to us.
I saw the Bob Arnson comment at the last. He changed the status from
untriaged state to resolved state and marked as duplicate.
But the request was to provide an optional attribute to pass on the comma
seperated multiple rights.
Has it been
I've haven't been able to find any cases online where heat was used with a
project.vbprog file rather than a project.csprog file but neither have
I found any explicit statement that heat only works with C# project files.
Can anyone clear this up for me?
Thanks,
Jonathan Anderson
Software
43 matches
Mail list logo
