Can't you "read" and serialize the key into temporary rows in the Registry
table? That wouldn't have to run after InstallInitialize.
The "canonical" way to deal with your situation is to use a bootstrapper
that forces an update to the broken installation that changes the registry
action value, and
Short answer: Not directly.
Long answer: If something is vital, or if the user cancels a prompt to retry
the operation, its failure is fatal. Otherwise it's ignorable.
Custom actions can be treated as either vital (e.g. Return="check") or
ignored (e.g. Return="ignore"). Files can be marked as vit
Please help, guys.
I screwed up badly and need to fix this before the problem gets worse.
My current idea is to run a custom action before upgrade that stores the
registry key in a file and then another action after the uninstall to restore
the key. I have implemented the custom actions, but I'
In article ,
James Poole writes:
> I seem to recall this being possible, but I am getting an error
> "Uninstallation of the patch package is not supported" when I try to install
> the second patch that supersedes the first.
Does the verbose log indicate this messages is about the original
>From the verbose log file...
MSI (c) (6C:BC) [02:12:26:232]: PROPERTY CHANGE: Modifying INSTALLDIR property.
Its current value is 'C:\Program Files (x86)\Novell\SecureBridge\'. Its new
value: 'C:\'.
MSI (c) (6C:BC) [02:12:26:321]: Note: 1: 2318 2: C:\pagefile.sys
DEBUG: Error 2318: File does
Are there any document of MSI shows what error is fatal and what can be
ignore?
Thanks,
-Elfe
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Questions-about-showing-warning-error-message-dialog-tp5328727p5340588.html
Sent from the wix-users mailing
2318 is file does not exist error.
If you use C: as the INSTALLLOCATION, the application will be installed
under the drive root (c:\), there is no application folder like SecureBridge
been created.
Does your installer tring to access files under the application folder?
You can use /l*v to have th
Do you mean QtExec ?
http://wix.sourceforge.net/manual-wix3/qtexec.htm
http://wix.sourceforge.net/manual-wix3/qtexec.htm
In order to use QtExec, you must include a reference to the WixUtilExtension
when building your MSI. To do this, add the command line argument -ext
WixUtilExtension.dll when
Hi, anyone can help me on this? Would you please check if the attached sample
code works, or if I've made any mistake?
I doubt if I should also insert records to Directory table, but it seems to
me is the wrong direction. Since remove entire folder is a common
requirement for uninstall, I would li
Hi Pally,
Sorry if the first example is misleading, but the data created by the
product is not related with any user (actually the product is several
services, and web services, and some of the sub folder need be shared and
allow other machines in LAN to read and write). Would you please give me
Hi all,
I am using the built-in WixUI_InstallDir.
When testers are changing the install location from my default location to
"C:\" and clicking next, the install is giving a 2318 error
The following is how I setup the default install location
Hi,
I'm getting the following build error when I try and use QuietExec in a C++
custom action:
"error LNK2001: unresolved external symbol _QuietExec"
I'm using WiX 3.0, dutil.lib and wcautil.lib are included my linker input.
What am I missing?
Thanks,
James
--
It's just scheduled and not a specific response to user action. It executes
when the user clicks next the first time.
...
...
-Tim
On Mon, Jul 26, 2010 at 2:18 PM, MikeR wrote:
>
> How is your custom action being called? As Rob said if it's off a push
> button, or launched through a
Hi folks,
I've only ever used WiX for simple installers before, with no UI customisation.
I now have to display a second EULA which is specific for a feature. I'm at a
loss on how to do this.
Ideally when the user selects the feature that requires the second EULA from
the feature tree I'd like
The technique I usually use is leave the message box error displayed and go to
the application directory to profile the EXE. I run the exe from the command
line to see if any stack dumps are displayed. I'll try to start the service by
hand to see if any messages are displayed and I'll use tool
"asyncWait" means start the action and move on with the sequence, but don't
let the entire installation transaction end until the action has ended. I
think you want "check", which would not let the sequence continue with the
next action until your action ends.
-Original Message-
From: Jere
Why not just install and launch your configuration utility to configure, on
first installation? Then you don't:
1. complicate your installation with rerunning it for configuration, and
2. duplicate code.
-Original Message-
From: Stelios Kyprou [mailto:stelios.kyp...@formicary.net]
Sent: M
Do you need this?
-service
What you should look at is both the Application and the System event logs.
Windows Installer usually displays a generic "privilege" error message
always ignoring the real error when the service control manager returns any
error
How is your custom action being called? As Rob said if it's off a push
button, or launched through any MSI UI via a DoAction control event logging
will not occur. This is a limitation of Windows Installer, it's documented
somewhere in the SDK, I forget where. If your custom action is scheduled
I worked a product where we took a set of WXS files and built them multiple
times varying a small number of inputs (such as compiler defines and/or
environment variables) and then linked each set of WIXOUTs into MSIs, as you
mention. I don't see a problem with that.
Not every build environment eas
I usually recommend that all components that you can assign reasonable
KeyPaths to where the rest of the component "lives" in the same profile
(per-machine vs. per-user), where the compiler accepts it, and where you
haven't already released that component into the wild use automatic guids
(aka "*")
I took the msi call code out of wcautil and called it manually without
without the checks for log level.
Using the log command directly from wcalog.cpp
MsiProcessMessage(install, INSTALLMESSAGE_INFO, hrec); returns 0 creating
no output
Modifying it to try and force logging
MsiProcessMessage(inst
Greetings WiX Users!
Not so long ago I posted my dilemma regarding Custom Actions not persisting
session data through to UI dialogs... I modified the ExitDialog to have a
button that took you to further configuration options so that it could read
in default options from the deployed App.Config fil
Hi
In my installer I add a value to
HKLM\Software\Microsoft\Windows\CurrentVersion\Run.
By mistake I set the action to "createAndRemoveOnUninstall", so now when you
uninstall or upgrade my program it removes the Run key. Very bad.
Is there anything I can do in the next version, so when you upgra
This is more of a general MSI question...
Can a Patch that is NOT Uninstallable be superseded?
I seem to recall this being possible, but I am getting an error
"Uninstallation of the patch package is not supported" when I try to install
the second patch that supersedes the first.
Thanks,
James Po
Hello everyone,
I would like to ask your opinions on one topic.
I have a c# application, which uses configuration files to set some
values needed to run the application.
These values are set by the installer through the dialogs, and all
values are validated via custom actions (in wix 3.5)
But in
I've narrowed this down to being an issue with Light and the -xo (output wixout
format) and -bf (bind files) options. I set OutputAsXml = true and
LinkerBindFiles = true in my project file. Those get passed to the Light
MSBuild task, which calls Light.exe with the -xo and -bf parameters. I do
Hi,
No after removing whole ServiceControl component I am getting same
message during service install. I am not understanding is it really
permission issue or I am missing some service components like registry
entries, dependency or dependent files. My works properly when I use
CnvRemoteService.ex
the error message maybe incorrect, remove the start=install part and attempt to
start it post install manually... it maybe that the service is dependent on a
file that is not yet installed (.net or CRT etc)
-Original Message-
From: rahul.ekb...@sungard.com [mailto:rahul.ekb...@sungard.co
Hi,
I am getting following error during installing the windows service
"Verify that you have sufficient privilege to install system services"
My WIX code is
Can any one knows what I need to change
Dear Peter,
Thank you for the hint! I replaced it now by ERROR_INSTALL_USEREXIT
which fits the best in my opinion.
Regards,
Luke
Am 26.07.2010 13:03, schrieb Peter Shirtcliffe:
> Sorry, I havent been following this thread, but I did have a glance at
> the code while waiting for an installati
yes! thank you
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: 26 July 2010 12:38
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall list icon
http://www.tramontana.co.hu/wix/lesson6.php#6.7 &
http://msdn.microsoft.co
http://www.tramontana.co.hu/wix/lesson6.php#6.7 &
http://msdn.microsoft.com/en-us/library/aa367593.aspx
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environme
InstEd is a much better (free) tool than Orca if you absolutely have to
open up MSI's -> http://apps.instedit.com/
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrat
Sorry, I havent been following this thread, but I did have a glance at
the code while waiting for an installation :)
!ERROR_SUCCESS isnt a valid custom action return. See this list
http://msdn.microsoft.com/en-us/library/aa368072%28VS.85%29.aspx
-Original Message-
From: Lukas Haase [mail
InstallExecuteSequence is always called. However when running with full
UI it goes InstallUISequence first followed by InstallExecuteSequence
which is why your code is working now. When running with basic (/qb) or
no (/qn) UI it only runs the InstallExecuteSequence.
What I was trying to highlight
Dear Blair,
Thank you very much. I think now I also understand the difference
between InstallExecuteSequence and InstallUISequence.
Regards, Luke
Am 25.07.2010 17:56, schrieb Blair:
> According to the log you posted, the InstallExecuteSequence was not run
> because the install was canceled from
Dear Bob,
Am 25.07.2010 15:45, schrieb Bob Arnson:
> On 7/25/2010 8:10 AM, Lukas Haase wrote:
>> However, there is also need to replace Product/@Id and
>> Product/@UpgradeCode ...
>
> Use preprocessor variables and/or localization variables.
Thank you for your reply. This is what I already did wi
Dear dB,
Thank you for your comment. You are right, maybe a bootstrapper would
have been the better apporach ...
I will have a look at dotNetInstaller.
Am 23.07.2010 16:43, schrieb dB.:
> Having dealt with a similar scenario with InstallShield, the best I can
> suggest is to bootstrap uninstal
Hi,
I changed my approach a little bit. For reference:
This is what I added to my wxs file:
And this is my small CheckSpecialist.c:
http://pastebin.com/mBL01Wtz
So the return value is either ERROR_SUCCESS or !ERROR_SUCCESS. I do not
use MsiSetProperty any more and just one custom act
Hello all,
A simple one here (the question I mean). Since I've moved across to WIX 3 my
applications no longer have an icon in the uninstall list in windows7 (and
maybe others). They just have the default .exe one, not even the MSI icon, an
ideas? I have an icon specified in each product..
Sim
Thanks!
I consult the Q/A.(also Yours)
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Updating-multiple-versions-of-a-product-td1384674.html
I successed to make 1.2 patch from 1.0 or 1.1
Here is.
42 matches
Mail list logo