Hi all,
I am getting error of
Note: 1: 2262 2: AdminProperties 3: -2147287038
While installing sample msi created using WiX v3. I am not getting what the
problem is. Please help me out..
-- Harshil
--
Download Intel
Hi Rohit
How can we call a WarningDialog from custom action ?
Following is the code snippet of my wxs file which is calling WarningDialog.
1
WARNING =
"1"
PROCEED = "1" OR
WARNING="0"
1
1
So is there no way I can do this, even if I could HIDE the feature in
selection tree that would work for me. But if that is also possible can
you suggest me what else I can try? CustomAction in C++ which maybe
allows to set Level for a feature. If not probably I would go for the
workaround.. i.e.
thanks guys,
I got rid of the user and the following worked fine:
Regards,
Asiri Wanigarathne
On 26 March 2010 11:54, Bob Arnson wrote:
> On 3/25/2010 1:46 AM, Michael Osmond wrote:
> > Error 0x80004005: failed to create to database:
> >
> > 80004005 - is Access Denied.
> >
>
> That's 0x800
On 3/25/2010 3:11 AM, Johann Taferl, T-AU wrote:
> Votive automatically generates following line(s):
>
You can change the Harvest property to false to stop automatic harvesting.
--
sig://boB
http://joyofsetup.com/
On 3/25/2010 1:43 AM, Asiri Wanigarathne wrote:
> CreateDatabase: Error 0x80004005: failed to create to database:
> 'TestDatabase', error: unknown error
>
Any error at this point should also have logged additional errors, so I
can't explain why you're not seeing them. That said, you're creating
On 3/25/2010 3:12 PM, Rohit Sharma (SIDC) wrote:
> I tried setting INSTALLLEVEL=101 from control event of next button as
> suggested in comment# 17 from Daniel in Bob's blog to trigger
> re-evaluation of feature condition but it didn't work for me.
>
I don't think it's documented to work. Feat
On 3/25/2010 7:53 PM, little.forest wrote:
> DEBUG: Error 2836: The control ChangeButton on the dialog MaintenanceTypeDlg
> can not take focus
> The installer has encountered an unexpected error installing this package.
> This may indicate a problem with this package. The error code is 2836. The
On 3/25/2010 1:46 AM, Michael Osmond wrote:
> Error 0x80004005: failed to create to database:
>
> 80004005 - is Access Denied.
>
That's 0x80040005; 0x80004005 is E_FAIL.
--
sig://boB
http://joyofsetup.com/
--
Downl
Bob Arnson-6 wrote:
>
> On 3/11/2010 9:21 PM, Tabmow wrote:
>> Sorry - i don't mean to be obtuse, but i searched around for
>> 'character map' and 'wix' and nothing jumps out at me.
>
> Character Map is a Windows tool; check your Start menu shortcuts.
>
Thanks Bob - that did the trick quit
We have an old product which uses Wix 2.0(a very stable version).
Our test engineer found a problem: if some dll file(s) is manually deleted,
then in Repair mode, we'll get "Error 2836". Here is the error message from log:
MSI (c) (B4:80) [16:22:22:313]: Note: 1: 2205 2: 3: Error
MSI (c) (B4:
OK, I found the answer looking through the bug list.
The project file name needs to appear in the command line directly after
the /project/ switch.
Thanks,
Bill
On 3/25/2010 3:22 PM, Bill McCormick (LIST) wrote:
> I made a C# test project called "Test" that is not a VSS project and now
> oth
Yes. If you see a "Stack Trace" its a bug in the tool. Can you provide as
much information as possible to help us track this one down?
On Thu, Mar 25, 2010 at 1:02 PM, Mike Rerick wrote:
> I am attempting to de-compile some old InstallShield merge modules. When I
> attempted to de-compile one of
I am attempting to de-compile some old InstallShield merge modules. When I
attempted to de-compile one of them, I got the error below. I tried it using
WiX 3.5.1519.0. In the Registry table, there are multiple entries of the
form _ISComExtract_Registryxxx and _ISComExtract_Registryxxx. in
the Regi
I made a C# test project called "Test" that is not a VSS project and now
other solution and it does not work.
Here's the complete output:
b...@engineeringhead /cygdrive/c/ace-co-devel/Aceco.NET/Test
$ ll
total 38
-rwx--+ 1 Bill None 1137 Mar 25 12:51 Form1.Designer.cs*
-rwx--+ 1 Bill No
I'd file a bug with the authoring you pasted below, and the answers to these
questions, if possible:
What's the exact error message you get (use a verbose logfile to find out)?
Does it work correctly if you install to an IIS6 machine?
Thanks,
Mike Carlson
-Original Message-
From: Ivo St
Coming back to the condition in my feature, Lets says initially I set
the Level="0" for the feature and set this condition
It doesn't enable my feature though I know that the property FEATURE2 is
being set to SUCCESS. So looks like the condition is being evaluated
before my property is set. Thi
I can't imagine why you'd consider that to be "obvious" - it's nonsense. WiX is
software, it can have knowledge of anything its authors want, and it can build
any knowledge it needs to into an msi. An msi for a 32-bit application doesn't
need any knowledge of the 64-bit environment anyway.
You
Sounds like the account used to install was not the account used to execute the
software in the perUser case. If that really was the case then the keys in HKCU
would not be available to the executing process.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 5
Hello,
Thanks for your care, but i solved the puzzle myself (as usual after i
go public with my problem).
Here's the solution:
We were trying to create keys under HKEY_CLASSES_ROOT and these attempts
are forwarded to HKCU or HKLM
(http://wix.sourceforge.net/manual-wix2/wix_xsd_registry.htm), dep
What's the OS version? I think you'll find that you don't need to install it on
any recent OS versions because it's part of the OS already - that's why you're
getting that message saying it can't replace it. The VB6 runtime isn't
supported after Windows 2000 (and not on XP either), so I find it
I hate decoding custom action types - what's the impersonation setting there?
If the custom action is running with no impersonation it's running with the
local system account, and that probably doesn't have the rights to create a
database.
Is there a good reason to create the database at insta
Guten Tag Markus Karg,
am Donnerstag, 25. März 2010 um 16:28 schrieben Sie:
> ...because I need to install a VisualBasic5 runtime, and Microsoft
> only provides a EXE but not a MSM for that. What the EXE does is
> basically replacing some DLLs in Windows\System32. So it is not *my*
> idea to do th
... and yes, the project does build without any errors, but there are
some warnings. Could that be the problem?
Thanks,
Bill
On 3/24/2010 5:21 PM, Mike Carlson (DEV DIV) wrote:
> It shouldn't be giving this message, but have you tried building the project?
> I ask because it could be a seconda
Hi,
We have two wixlibs core.wixlib and core.additional.wixlib.
If you add these to a wixproj as a reference they both appear as core in
the references list, and occasionally one will not appear even though
both are still referenced. For now I can hack the wixproj later and
change the refernce to
...because I need to install a VisualBasic5 runtime, and Microsoft only
provides a EXE but not a MSM for that. What the EXE does is basically replacing
some DLLs in Windows\System32. So it is not *my* idea to do that, but
Microsoft's...
> -Original Message-
> From: Thorsten Schöning [ma
Guten Tag Markus Karg,
am Donnerstag, 25. März 2010 um 13:37 schrieben Sie:
> Doesn't sound really promising... Maybe it's just best to run
> Microsoft's original Runtime Installer EXE then (unfortunately it's such old
> that there is no MSM).
Maybe the more preferable way is to get a solution f
Well you may ignore that line. What I meant was on "Process Always"
button, set a property and use that property as a condition on next
button of dlg1's newdialog event.
Looks like your code formatting got messed up when you replied to my
mail, can't understand anything from it.
Regards
Rohit
Please refer to the following URL:
http://msdn.microsoft.com/en-us/library/aa372855%28VS.85%29.aspx
http://windows.microsoft.com/en-IN/windows-vista/32-bit-and-64-bit-Windows-frequently-asked-questions
http://msdn.microsoft.com/en-us/library/aa384249%28VS.85%29.aspx
Microsoft supports a Emulat
yes Micheal,
there is a way around . try to find out the target machine using *
VersionNT64*
then you can actually set the condidtion to the component depending on
tht...
On Thu, Mar 25, 2010 at 6:20 PM, Michael Osmond wrote:
> Thanks Dave
>
> -Original Message-
> From: David Watson
That's a general problem with .NET binaries built for AnyCPU since Windows
Installer doesn't have an "AnyCPU" type platform (would be nice if departments
within Microsoft were aware of what each other support but I wouldn't hold my
breath).
Easy solution in that case would be to make x86 & x64 M
Well this is exactly what I would like to know! If anyone has any further
information then it would be greatly appreciated!
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: 25 March 2010 12:31
To: General discussion for Windows Installer XML toolset.
Subject:
Thanks Dave
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: Thursday, 25 March 2010 10:49 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Beginner's Question: 32 Bit MSI on 64 Bit OS
Hi,
In the past we have changed the bui
Thanks Rohit for the quick reply
I didn’t get this line:
“I am assuming that the WarningDialog is a dialog which is
from
your custom action and Process Always is MB_OK t
Hi,
In the past we have changed the build targets from any cpu to x86 in
our .net compliation, forcing the assmblies to be 32 bit.
Its also possible to detect what os you are on in the .net application and to
override any redirection in the registry access calls.
Dave
-Original Me
Sorry, my bad. Looks like I overrode the DefineConstants property from the
msbuild command line and neglected to include "Debug" in the new value.
Regards,
Ron
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Wednesday, March 24, 2010 10:05 PM
To: wix-users@lists
1 - post your WiX code for creating the Registry Entries otherwise we're
all just guessing at the problem. Also extracts from a verbose log when
the registry entries are created on the machine with the problem may
also help.
2 - Which other systems have you tested? Is it fine on x64 Vista? What
ab
Sounds good, thank you! :-)
> -Original Message-
> From: Richard Horsley [mailto:richard.hors...@eicltd.com]
> Sent: Donnerstag, 25. März 2010 13:26
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Beginner's Question: 32 Bit MSI on 64 Bit OS
>
> As
Yes just use a DirectoryRef in a Fragment to link it to your main
Directory Tree.
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 Environmental Solutions Limited.
Thanks for your help.
Doesn't sound really promising... Maybe it's just best to run Microsoft's
original Runtime Installer EXE then (unfortunately it's such old that there is
no MSM).
Thanks
Markus
> -Original Message-
> From: Pally Sandher [mailto:pally.sand...@iesve.com]
> Sent: Donn
I found one case where this doesn't work. It seems dotnet apps by default
leave it up to the framework to determine if they are 64 or 32 bit. So when
you package this as a 32 Bit MSI and install it on a 64 Bit machine the
registry settings are redirected to the Wow6432bit node, but when the co
I wouldn't give up on it just yet. As I said I don't use the WiX only
method but I'm sure there are people on this list who do & will be able
to point you in the right direction to create one MSP which targets
multiple MSI's. That'll allow you to release a single MSP in future
which updates 1.0, 1.
As I said a bit further back, installing regular x86 MSI's on x64 windows
systems works absolutely fine. It will automatically use SysWOW64 instead of
system32, Wow6432Node for registry settings and Program Files (x86) for the
actual program directory. Unless you specify otherwise, this is the d
Use a bootstrapper to install the redistributable from Microsoft which
updates that file to the version you require before you install your
MSI. Any other solution has massive potential for problems.
If you're looking for a bootstrapper I recommend dotNetInstaller ->
http://dotnetinstaller.codeple
ProductVersion is correct on both of the original MSI's (1.0 and 1.1
respectively, so they are definitely not the same!), I am using WIX only to
create these (in notepad). What I have discovered is that the patch file I am
generating will only patch the original installer (which I used in the
c
Karg,
If you get a chance to install your x86 msi on 64 bit OS, please share your
results with me. It will help me in future.
-- H
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Thursday, March 25, 2010 5:21 PM
To: General discussion for Windows Installer
Hi,
if the software is only 32bit and you want it to be installed in the 32bit
folders (e.g. "c:\Program Files (x86)") than you do not have to do anything.
Only if the program should be installed to 64bit folders, you have to change
the folders: "ProgramFilesFolder" -> "ProgramFiles64Folder"
The
That's pretty bizarre. Are you building your patches using the Windows
SDK tools or WiX only? At least it's fixed for the future but it makes
absolutely no sense. The only other thing I can think of which might
possibly cause this is if your 1.0 & 1.1 MSI's both have the same
version number set. Th
MSI's themselves are built for either x86 or x64 platforms (or Intel64 aka
Itanium but they're so rare it's not worth mentioning).
Build your MSI for x86 as you normally do & if a user tries to install it on an
x64 system msiexec/WoW will take care of it.
Ignore everything Harshil says, you don'
Well it is obvious that msi created on 32-bit machine has no knowledge of
64-bit environment and if u wont to provide support to both 64-bit and 32-bit
OS, its required man...sorry.. you can try with it..
-- H
-Original Message-
From: Markus Karg [mailto:k...@quipsy.de]
Sent: Thurs
I am assuming that the WarningDialog is a dialog which is from your custom
action and Process Always is MB_OK type button.
The click on "Proceed Anyways" button should set a property: Say GONEXT = TRUE.
Then you may use this property as a condition on DLG1's Next button's new
dialog event.
But that's weird -- it would mean that it is impossible to install a MSI on a
64 Bit machine that was created in times when there was no 64 Bit around
already... -- or that all software vendors in the past obtained 64 Bit machines
just to create their 32 Bit MSIs THERE!? Can't believe that.
>
When I have done this before, the msiexec on the machine installing the
software has always handled the package correctly (placing items in syswow on
x64 machines for files and registry as well as Program Files (x86)) on both
machines. AFAIK you only need to specify x64 folders if your package
Productcode and Upgradecode are the same in all of the generated MSI's, its so
wierd. The MSP's themselves seem to check for installed version and will only
patch the version they were created for. I have worked out a way around this
though. I have now created a 1.0 > 1.2 MSP and a separate 1.1
Well you have to do it on 64-bit machine only then and then only msi will be
fully 64-bit\32-bit compatible. I already encounter this issue in past and had
to get 64-bit OS just to solve this issue.
-- H
-Original Message-
From: Markus Karg [mailto:k...@quipsy.de]
Sent: Thursday, M
But we do not own a 64 Bit machine, so how to do it on a 32 Bit machine?
> -Original Message-
> From: Lodhiya, Harshil [mailto:harshil.lodh...@eclipsys.com]
> Sent: Donnerstag, 25. März 2010 12:14
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Begi
Just create your MSI on 64-bit machine with the DLLs created as target x86, and
it will run on both 32-bit\64-bit machine. 64-bit OS will automatically take
care of system folder.
-- H
-Original Message-
From: Markus Karg [mailto:k...@quipsy.de]
Sent: Thursday, March 25, 2010 4:41 PM
Dear WiX Community,
we need to write a MSI file that has to install a 32 Bit software. It
shall correctly install on both, Windows 32 and Windows 64.
Is it correct to do one setup that always installs into SystemFolder, or
do we have to take any special care for the Windows 64 case?
Tha
Dear WiX Community,
for one of our applications, we need to provide the latest version of a
DLL which comes with XP in an older version (e. g. ASycFilt.dll) and
lives in WINDOWS\System32.
When we try to run our MSI on XP, it says that it cannot replace this
DLL since it is protected by the
I would open the MSI's themselves in InstEd! or Orca & check the
ProductCode GUIDs (they'll be in the Property tables) just to make 100%
sure. You may also want to check the UpgradeCodes too, shouldn't make a
difference to patching though as only major upgrades should need them
but it doesn't hurt
I have two dialog box Dlg1 and Dlg2.
On the press of the next button of Dlg1, I am calling a custom action.
Now this custom action sets a property WARNING to “0” or “1”.
If warning is “0”, I need to proceed to Dlg2.
If warning is “1” , I need to shown a popup dialogbox named WarningDialog
box.
T
Thanks for the information! I am looking into this now. I generated both
versions from the same wxs file with the same product code. However, the
package ID is auto-generated, if that makes a difference? Here is the original
wxs that generated both of the MSI versions:
http://schemas.microsoft
Sounds like the 1.0 & 1.1 MSI's have different Product Codes. Did you
implement major upgrade functionality for 1.0 MSI -> 1.1 MSI? I had this
exact same problem as I'd released v1.0 & v1.1 of a product with the
same Product Code then released v1.2 with a different Product Code so I
could add major
WixUI has different modes namely Mondo, FeatureTree, Minimal, InstallDir
and Advanced. In your Wix project you just add them for reference and it
uses default UI dialogs to show. But in case you want to add a custom
dialog you need to download the source of WixUI dialog of your choice,
add it to y
Hi,
I am new to this mailing list.. so be gentle!
I am trying to create some kind of prompt for a username
and password - preferably it will let you search the domain
for a user - but i'll settle for an edit box.
Can anyone give me any pointers? I have googled it but it
is muddied by someone ask
I have a WIX patch that I need to apply to all client PC's with a particular
product installed. I generated the original MSI and have the WIX script that
was used to create it. The process has gone like this:
MSI installer v1.0 created and distributed to 50% (ish) of client machines.
MSI install
Sorry, I think I got it.
Votive automatically generates following line(s):
When removing this line(s), the msi file is created correct.
Do you know, if this is an error, or does it work like expected?
Thanks,
Johann
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sen
You are absolutely right. The msm-file can be found in the files-table.
Do you know what I can do about this?
PS: The merge module looks correct...
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Mittwoch, 24. März 2010 21:16
To: wix-users@lists.sourceforge.net
Sub
68 matches
Mail list logo
