Per your link... The issue with Windows Installer 5.0 is that the
SeBackupPrivilege permission is missing altogether. It is necessary to add
it to the service permission value in the registry
(HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msiserver\RequiredPrivileges).
If you use process ex
Ahh, cool. I was temporarily keying off of "ProgramFiles(x86)", but this is
another option, thanks.
On Sat, Jan 22, 2011 at 5:50 PM, Blair wrote:
> If you happen to need to know what the base OS architecture is you can
> check
> for the presence/value of PROCESSOR_ARCHITEW6432.
>
> http://msdn.m
I didn't look at your link but, yes, if I add SeBackupPrivilege to the
service privileges in the registry (and restart the service) it works as
expected. This might be an option, but it is a bit of a chicken and egg
scenario for this particular product.
The other option is to set Impersonate="yes"
Hi, I'm new to using Wix and I'm having some problems trying to control a
Next button I have. I took WixUI_Mondo.wxs and renamed it as well as
modified it to include a dialog for checking a database connection. Below is
a snippet of my modified WixUI_Mondo.wxs:
1
2
Now within my CheckDbConnection
Just curious: do you need to "enable" SeBackupPrivilege? Something like
http://msdn.microsoft.com/en-us/library/aa387705(VS.85).aspx
-Original Message-
From: Andy Clugston [mailto:clug...@gmail.com]
Sent: Saturday, January 22, 2011 6:54 AM
To: General discussion for Windows Installer XML
If you wish to install your AnyCPU binaries in 64-bit spaces, you need a
64-bit MSI (yes, use the -arch switch, that is the correct approach).
Realize that an MSI marked 64-bit cannot be installed on a 32-bit system, so
you will need another MSI for your 32-bit customers.
You can build both MSIs f
If you happen to need to know what the base OS architecture is you can check
for the presence/value of PROCESSOR_ARCHITEW6432.
http://msdn.microsoft.com/library/aa384274.aspx
-Blair
-Original Message-
From: Andy Clugston [mailto:clug...@gmail.com]
Sent: Saturday, January 22, 2011 9:26 A
You still had a chance at resolving this if you hadn't removed the "extra"
entries (they would have given us a clue where to look) but now that's done,
you'll truly get back to a working state faster by reinstalling the OS and
all your tools/etc. then by messing with it further...
-Original Me
I've been receiving the following error during installation
---snip---
ComPlusInstallExecuteCommit: Registering assembly, key:
PasswordFilterServerCOMAssembly
MSI (s) (EC!E4) [22:13:20:296]: Closing MSIHANDLE (163) of type 790531
for thread 3300
MSI (s) (EC!E4) [22:13:22:375]: Creating MSIHANDLE
Yep. Thanks for the reply.
On Sat, Jan 22, 2011 at 11:31 AM, Rob Mensching wrote:
> Yeah, 32-bit processes on 64-bit Windows get PROCESSOR_ARCHITECTURE=x86.
> Start up a 32-bit cmd.exe and you'll see the same thing.
>
> On Sat, Jan 22, 2011 at 3:58 AM, Andy Clugston wrote:
>
> > Hi Users,
> >
>
On Fri, Jan 21, 2011 at 4:47 PM, Rob Mensching wrote:
> Actually, for Package/@Platform, it is better to use the -arch switch on the
> command-line. That will flip your entire package to x64 as needed.
Related question (I hope): Is this the proper approach if your .Net
application targets AnyCPU?
Thom is correct.
On Fri, Jan 21, 2011 at 8:46 AM, Thom Leigh wrote:
> Have you tried Component/@Win64="yes" for that component?
>
> Not sure if that's needed if you're following robmen's advice and using
> -arch, as that switch should set Win64="yes" for you (I think?)
>
>
> -Original Messag
One more vote for never using VBScript CustomActions.
http://blogs.msdn.com/b/robmen/archive/2004/05/20/136530.aspx
On Fri, Jan 21, 2011 at 12:20 PM, Brownfield, Cory wrote:
> It *was* a vbscript.dll registration issue. I followed the instructions
> here http://blogs.msdn.com/b/astebner/archive
Yeah, 32-bit processes on 64-bit Windows get PROCESSOR_ARCHITECTURE=x86.
Start up a 32-bit cmd.exe and you'll see the same thing.
On Sat, Jan 22, 2011 at 3:58 AM, Andy Clugston wrote:
> Hi Users,
>
> I am working the kinks out of an MSI to support 64 bit. This is an x86 MSI
> that will run in WO
Yeah, that "chainer" is quite simplistic.
On Fri, Jan 21, 2011 at 7:41 PM, vivekanandan balaguru wrote:
> Hi,
> We are using setupbld.exe to chain two msi and it works fine first time,
> but
> the output integrated exe does not let us do the change mode during next
> time install but goes to rein
A bit but ends up being very convenient given how important paths are to an
installer.
On Sat, Jan 22, 2011 at 5:38 AM, Wilbert van Dolleweerd <
wilb...@arentheym.com> wrote:
> 2011/1/21 Rob Mensching :
>
> > It's kinda' tricky. Properties can be treated like Directories. So name a
> > Directory/
This MSI documentation will explain Minor Upgrade:
http://msdn.microsoft.com/en-us/library/aa367575(v=VS.85).aspx.
You might also read through:
http://robmensching.com/blog/posts/2007/1/4/Doing-a-small-update-or-minor-upgrade-in-MSI-Use
However, it sounds like you really want a Major Upgrade. Why
Isn't WI v4 where the UAC was introduced and the Privileged property became
useless? If so, then you should be able to use both properties to get what
you want downlevel and uplevel.
On Fri, Jan 21, 2011 at 8:51 AM, Alex Ivanoff wrote:
> Unfortunately, MSIUSEREALADMINDETECTION requires Windows In
Phil, I am running Win7 and 5.0 of msiexec is on the system (shipped with
it), and I still see the issue.
Thanks.
On Fri, Jan 21, 2011 at 4:08 PM, wix user wrote:
> Hi Phil,
>
> How is the WIX support for MSI 4.5 features? We are planning to use
> Multiple
> transaction features.
> Are there so
Hiya all,
Hope this messages goes thru... Tis my very first mailing list message :)
I am getting the dreaded "Another version of this application is already
installed" blah when trying to install a newer version of our software.
Its a minor upgrade, but it is in Beta so we prefer a reinstall, at
2011/1/21 Rob Mensching :
> It's kinda' tricky. Properties can be treated like Directories. So name a
> Directory/@Id the same as your Property/@Id for the search. This might be
> useful:
> http://blogs.msdn.com/b/robmen/archive/2006/10/17/deciphering-the-msi-directory-table-part-7-directories-are
Hiya all,
Hope this messages goes thru... Tis my very first mailing list message :)
I am getting the dreaded "Another version of this application is already
installed" blah when trying to install a newer version of our software.
Its a minor upgrade, but it is in Beta so we prefer a reinstall, at
Hi Users,
I am working the kinks out of an MSI to support 64 bit. This is an x86 MSI
that will run in WOW64 on x64 systems.
The issue I am seeing is that the PROCESSOR_ARCHITECTURE is set to x86
(rather than what the base OS architecture is; i.e. AMD64) within a custom
action that is running. Thi
23 matches
Mail list logo
