[WiX-users] Checking if a folder exists before setting its permission

[Ravit Shapira]

 Hi,

I'm trying to check if a directory exists before I set its permission.
The following is a snippet from my code:




  



  
  
NOT LOGS.DIR.EXISTS

  
  

  


>From the log files I see that when logs dir does not exist it exexcutes the 
>folder create op.
( "MSI (s) (18:4C) [17:35:12:122]: Executing op: 
FolderCreate(Folder=C:\MobileSearch\Logs\,Foreign=0,)" ). However, when it does 
exist, then only if I run the msi using msiexec and pass a value to LOGS_DIR 
like: LOGS_DIR=c:\VSLogs\logs then it gets the right value, if I don't pass any 
parameter it gets the value "c:\".

This behavior makes sense since the value of LOGS_DIR is not set to the right 
value at the beginning if no parameter was passed. Currently, I'm trying to 
find the right solution by trial and error.
Is there a generic solution that will enable me to check if a folder exists 
before I set its permission?

Thanks,
Ravit


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Check .NET version and bootstrapper

[Ansuya Negi]

Hi,
I can check .NET version as shown in tutorial:


Then I need to install .NET framework accordingly. As suggested by some
posts, I tried using bootstrapper dotNetInstaller. However this just gives
us an option, whether we want to install .NET or not. The condition check
that we have .NET comes after this in .msi file. Is it possible to first
check the condition in .msi file and then load .NET.
Thanks,
Ansuya

-- 
View this message in context: 
http://www.nabble.com/Check-.NET-version-and-bootstrapper-tf4246075.html#a12083627
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Run program after installation

[John Lalande]

Richard

I really appreciate your help on this but due to time constraints I have
thrown in the towel and written a custom action that works.  It simply gets
the INSTALLDIR property, concatenates the exe name and creates a new
process...works every time.

Again, thanks so much...

John

On 8/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
>
>  John,
>
>
>
> The 210 is a little misleading, I admit.
>
>
>
> Expressed in hexadecimal, 210 = 0xD2
>
>
>
> From http://msdn2.microsoft.com/en-us/library/aa368071.aspx we can see
> that this decodes as follows:
>
>
>
> 0x80 = Run operation asynchronously
>
> 0x40 = Ignore exit code
>
>
>
> That leaves us with 0X12 – i.e. 18 decimal which is what we would expect.
>
>
>
> I am seeing the same issue as you – the application launches correctly for
> the default folder, but does not launch for a different folder.
>
>
>
> For some bizarre reason I am unable to run ProcessMonitor against the
> installation, or at least I am unable to do so within Microsoft Virtual PC
> which is where I strongly prefer to test my installations (the virtual PC
> reboots without permission or any obvious reason). I'll let you know what I
> find as I learn more.
>
>
>
> Regards,
>
> Richard
>
>
>  --
>
> *From:* John Lalande [mailto:[EMAIL PROTECTED]
> *Sent:* Thursday, August 09, 2007 2:13 PM
> *To:* Foster, Richard - PAL
> *Cc:* wix-users@lists.sourceforge.net
> *Subject:* Re: [WiX-users] Run program after installation
>
>
>
> Richard
>
> As per the tutorial, my custom action is defined as:
>
>Return="asyncNoWait" />
>
> This yields a custom action of type 210.
>
> I am very curious how your experiment turns out.
>
> John
>
>
>
> --
>
> * C O N F I D E N T I A L I T Y N O T I C E *
> ---
> The content of this e-mail is intended solely for the use of the
> individual or entity to whom it is addressed. If you have received this
> communication in error, be aware that forwarding it, copying it, or in any
> way disclosing its content to any other person, is strictly prohibited.
> Quixote Traffic Corporation is neither liable for the contents, nor for the
> proper, complete and timely transmission of (the information contained in)
> this communication. If you have received this communication in error, please
> notify the author by replying to this e-mail immediately and delete the
> material from any computer.
>
>
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Voce acaba de receber um cartao!

[hotcards]

 ' CARTÕES HOTMAIL   Olá,  Você acaba de receber um CARTÃO HOTMAIL, os cartões que podem encontrar seu verdadeiro amor, enviado por Alguém que te admira muito.   Veja o cartão http://hotmail.msn.com/cartao2105/cgi-bin/getmsg  Um grande abraço de nossa equipe HOTMAIL. OBS: Este cartão tem validade de apenas 15 dias, então não esqueça de ler essa pequena e valiosa mensagem.Conheça já o MSN Mobile!
  



-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Auto-incremented versions

[Sean Li (XIN)]

Hi,

What's the best way to handle information that changes in every build?  For 
example, the assembly version of my COM registration is different every build 
because we auto-increment the minor version number.  Is there any best practice 
to handle this kind of information?

Thanks a lot,
Sean

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Registering an EXE via a Custom Action

[Richard]

You're better off extracting the registration information from the EXE
and using the COM/Registry tables to register the necessary classes.

Its *much* easier and *much* more robust to use the tables for COM
registration than it is to use custom actions.
-- 
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
  

Legalize Adulthood! 

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Registering an EXE via a Custom Action

[Tanikella, Rajanikanth (SCR US)]

After a little further investigation, let me rephrase my initial
question
and supporting details:

I'm building an MSI using WiX3, and I'm encountering a 
problem:  I've a custom action:



It is sequenced to be executed BEFORE 'InstallFinalize'.  I've confirmed
this using Orca.

The problem I encounter is that once the installer is complete the log
indicates no error, but the installed application throws a 'class not
registered' error.  The registry contains no trace of the registered EXE
either.

If, however I execute 'PckgInstllr.exe /regserver' from a DOS prompt,
then the installed app works, and the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\PckgInstllr.EXE\AppID is set
to its GUID.
 
Setting Execute to 'defer' or 'commit' makes no difference.

The new clue is that if I set Return to 'check' then MSIEXEC detects a
failure and rolls back.  But executing the same registration call from a
DOS prompt does not fail.

I've even tried removing the calls and placing them in a BAT file and
installing that instead and running it.  Again, the log shows it as done
but the installed app does not see the registered class.

I'm sure I'm missing something so stupid and minor that I'll slap my
forehead about it, but right now I haven't a clue.

Thanks for any isight you can provide.

Raj

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] EventSource element

[Brent B. Powers]

Jarrod Marshall wrote:
>
> Is anyone actively registering event sources with the EventSource element?
>
> I have a need to but the documentation isn't quite clear on the 
> required EventMessageFile argument. What exactly is that? :)
>
> Anyone have an example that works?
>
> Thanks!
>
It's the name of the DLL that contains the text of your messages. I 
generally embed them within my executable, giving (this is for a 
service, and there's a lot of unrelated stuff in here):





(etc...)


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Run program after installation

[Richard.Foster]

John,

 

The 210 is a little misleading, I admit.

 

Expressed in hexadecimal, 210 = 0xD2

 

From http://msdn2.microsoft.com/en-us/library/aa368071.aspx we can see
that this decodes as follows:

 

0x80 = Run operation asynchronously

0x40 = Ignore exit code

 

That leaves us with 0X12 - i.e. 18 decimal which is what we would
expect.

 

I am seeing the same issue as you - the application launches correctly
for the default folder, but does not launch for a different folder.

 

For some bizarre reason I am unable to run ProcessMonitor against the
installation, or at least I am unable to do so within Microsoft Virtual
PC which is where I strongly prefer to test my installations (the
virtual PC reboots without permission or any obvious reason). I'll let
you know what I find as I learn more.

 

Regards,

Richard

 



From: John Lalande [mailto:[EMAIL PROTECTED] 
Sent: Thursday, August 09, 2007 2:13 PM
To: Foster, Richard - PAL
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Run program after installation

 

Richard

As per the tutorial, my custom action is defined as:

  

This yields a custom action of type 210. 

I am very curious how your experiment turns out.

John 

 




* C O N F I D E N T I A L I T Y N O T I C E *
---
The content of this e-mail is intended solely for the use of the individual or 
entity to whom it is addressed. If you have received this communication in 
error, be aware that forwarding it, copying it, or in any way disclosing its 
content to any other person, is strictly prohibited. Quixote Traffic 
Corporation is neither liable for the contents, nor for the proper, complete 
and timely transmission of (the information contained in) this communication. 
If you have received this communication in error, please notify the author by 
replying to this e-mail immediately and delete the material from any computer.


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] EventSource element

[Jarrod Marshall]

Is anyone actively registering event sources with the EventSource element?

I have a need to but the documentation isn't quite clear on the required 
EventMessageFile argument. What exactly is that? :)

Anyone have an example that works?

Thanks!

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Conditional Statement Problem

[Karthik Krishnan]

Dumb question, are the < signs causing you trouble? I use:



On 8/9/07, Rob Hamflett <[EMAIL PROTECTED]> wrote:
>
> Give your property an explicit starting value with [EMAIL PROTECTED], which
> gets overridden by the
> RegistrySearch.  Then you can base your condition against this value.
>
> Rob
>
> Schuett, Michael (VMC) wrote:
> > Hello,
> >
> > I'm reading a DWORD value from the registry using RegistrySearch. (WiX
> 3.0.2925.0)
> >
> >
> > 
> >>
> Key='SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\FooSoft 1.0' />
> > 
> >
> >
> > I understand DA_VER is an empty string if "Version" isn't found. If it
> is found, DA_VER will start with '#' followed by the value of Version.
> >
> > I want to bail out of the install if the DWORD value doesn't exist. I've
> tried the following and none of them work.
> >
> >
> >  NOT DA_VER 
> >
> >  DA_VER = "" 
> >
> >  NOT (DA_VER << "#") 
> (This doesn't even compile)
> >
> >
> > Any ideas/suggestions?
> >
> > I'm assuming all the Windows Install Conditional Statement Syntax (see:
> http://msdn2.microsoft.com/en-us/library/aa368012.aspx) is valid in WiX.
> >
> > Thanks,
> > Mike
> >
> >
> -
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >>  http://get.splunk.com/
>
>
> -
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Adding a new element using XmlFile

[Karthik Krishnan]

Might want to take a look at XmlConfig instead of XmlFile.

On 8/8/07, Ion Costco <[EMAIL PROTECTED]> wrote:
>
>  Resending. Nobody encountered this? Thought it should be common...
>
> - Original Message -
> *From:* Ion Costco <[EMAIL PROTECTED]>
> *To:* wix-users@lists.sourceforge.net
> *Sent:* Thursday, July 26, 2007 2:48 PM
> *Subject:* [WiX-users] Adding a new element using XmlFile
>
>  Hi!
>
>
>
> I have this statement below that changes a configuration string in a xml
> file:
>
>
>
>   
>File="[TARGETDIR]\Web.Config"
>
>Action="setValue"
>
>Name="value"
>
>Value="Data Source=[SQLSERVERNAME];Initial
> Catalog=[SQLDATABASENAME];Integrated Security=True"
>
>ElementPath="
> //configuration/appSettings/[EMAIL PROTECTED]'ConnectionString'[\]]"
>
>Sequence="10"/>
>
>
>
>
>
> I can't figure out how do I make it so if the *add* element with 
> *key*attribute matching the path is missing, it will create it, and it will 
> set
> the value for the attribute provided by *Name* (in this case *value*) to
> the given value. I thought using *createValue* instead of *setValue* will
> do the trick but I get the same error when the line * key="ConnectionString" value="server=localhost;Trusted_Connection=yes;
> database=PRSDB"/>* is missing.
>
>
>
> Thanks,
>
>
>
> --
>
> -
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
>
> --
>
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> -
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Error 1625

[Ravit Shapira]

Hi Bob,

>From checking the log file I see that my msi is not digitally signed.

MSI (s) (40:F4) [17:10:33:336]: SOFTWARE RESTRICTION POLICY: Verifying package 
--> 'C:\WINNT\TEMP\octtmp5\VSAddressSetup.msi' against software restriction 
policy
MSI (s) (40:F4) [17:10:33:336]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (s) (40:F4) [17:10:33:336]: SOFTWARE RESTRICTION POLICY: 
C:\WINNT\TEMP\octtmp5\VSAddressSetup.msi is not digitally signed
MSI (s) (40:F4) [17:10:33:336]: SOFTWARE RESTRICTION POLICY: SaferIdentifyLevel 
reported failure.  Assuming untrusted. . . (GetLastError returned 5)
MSI (s) (40:F4) [17:10:33:336]: The installation of 
C:\WINNT\TEMP\octtmp5\VSAddressSetup.msi is not permitted due to an error in 
software restriction policy processing. The object cannot be trusted.

MSI (s) (40:F4) [17:10:34:352]: Note: 1: 1718 2: C:\WINNT\Installer\1a21f7c9.msi
MSI (s) (40:F4) [17:10:35:914]: MainEngineThread is returning 1625
MSI (c) (80:F0) [17:10:35:914]: Decrementing counter to disable shutdown. If 
counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (80:F0) [17:10:35:914]: MainEngineThread is returning 1625

I do see that the error that I'm getting it is connected to Error 1718 and I'm 
going to run the Windows Server 2003 update 
(http://support.microsoft.com/kb/925336) and see if it fixes my problem.

Thanks,
Ravit


From: Ravit Shapira
Sent: Thursday, August 09, 2007 10:23 AM
To: 'Bob Arnson'
Cc: wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Error 1625

Thanks Bub! How can I verify that .msi package is digitally signed?

Ravit


From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 09, 2007 7:41 AM
To: Ravit Shapira
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Error 1625

Ravit Shapira wrote:
I'm trying to run a setup on a Win2k3 server and I get error no' 1625: "The 
system administrator has set the policies to prevent this installation".
When I run the same setup on Vista it works. Currently the msi size is:  1.55 
Giga Byte (I configured 5 cabs). Before that when it was 441MByte I could run 
the setup with no error.

Assuming the .msi package is digitally signed, it sounds like a SAFER problem. 
See 
http://blogs.msdn.com/heaths/archive/2007/01/11/known-issues-with-visual-studio-2005-service-pack-1.aspx
 for one discussion of the problem.


--

sig://boB

http://joyofsetup.com/
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] .Net Framework Version

[Karthik Krishnan]

Matthieu,

If I had to guess, I'd say you want to 'install' .NET 2.0 to a particular
website, while having 1.1 running on another?

You can do one of two things:

The Ugly Way(TM), run a custom action vbs that calls aspnet_regiis :

'Install .Net 2.0
  Dim objWMIService, objProcess, objCalc
Dim strShell, objProgram, strComputer, strExe
strComputer = "."
strExe =
"C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i"
' Connect to WMI
set objWMIService = getobject("winmgmts://"_
& strComputer & "/root/cimv2")

' Obtain the Win32_Process class of object.
Set objProcess = objWMIService.Get("Win32_Process")
Set objProgram = objProcess.Methods_( _
"Create").InParameters.SpawnInstance_
objProgram.CommandLine = strExe

'Execute the program now at the command line.
Set strShell = objWMIService.ExecMethod( _
"Win32_Process", "Create", objProgram)

Or a better way(I found this on Wix-Users written by Evgeny Popov, his
solution saved me some time and trouble, at
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg09414.html) :

"You should insert into WebApplication element that:











































  
where:
ASPNETISAPIDLL:
 



"



On 8/8/07, Matthieu RUNTZ <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> Does anyone know how to choose the framework version (1.1 or 2.0) during
> the creation of a new Web site.
>
> Regards,
> Matthieu
>
> -
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Votive and Project References -- RESEND

[Justin Rockwood]

Unfortunately, there's a bug right now in wixlib references. You can
manually add the reference (not a project reference) and have it work fine.
Like you said, though, I think it stores a hardcoded path, which is a bug.
Adding a .wixlib project reference, however, does not currently work as
expected. This is also a bug. Sorry about the trouble.

 

Justin

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Quattro IV
Sent: Thursday, August 09, 2007 7:17 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Votive and Project References -- RESEND

 

I didn't get a response so I'm resending this:

 

Hello, I'm having an issue referencing a WiX library from a standard WiX
module. For some reason I get "Unresolved reference to symbol..." errors
when I just reference the WiX library project directly instead of the 
referencing the output of the project (.wixlib file) Anyone get this to
work?

Also, when I reference the output file directly it creates a hardcoded path
and I have to manually update the .wixproj directly to fix it, is this a 
bug?

Any help is appreciated.

Reese 
 

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Run program after installation

[John Lalande]

Richard

As per the tutorial, my custom action is defined as:

  

This yields a custom action of type 210.

I am very curious how your experiment turns out.

John

On 8/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
>
>  Hi John,
>
>
>
> That's odd that ProcessMonitor doesn't even show a failed attempt at
> accessing the file. I would certainly expect **something** to show up.
>
>
>
> Assuming you're following the tutorial example, I believe what should be
> getting triggered is a type 18 custom action. Since you haven't mentioned
> otherwise, I also assume that there are no parameters being passed (i.e.
> the ExeCommand attribute is present, but empty). Is that correct?
>
>
>
> It is certainly possible that the path to the executable is not being
> resolved properly, although if that were the case I would expect people to
> have reported it as a bug long ago. I'm waiting for a build to finish, so
> I'm going to see if I can get a minimal example working and try to reproduce
> the problem here.
>
>
>
> Regards,
>
> Richard
>
>
>  --
>
> *From:* John Lalande [mailto:[EMAIL PROTECTED]
> *Sent:* Thursday, August 09, 2007 12:54 PM
> *To:* Foster, Richard - PAL
> *Cc:* wix-users@lists.sourceforge.net
> *Subject:* Re: [WiX-users] Run program after installation
>
>
>
> According to the tutorial, the FileKey attribute of the custom attribute
> is set to the Id of the file you wish to run so I assume that it is trying
> to run the executable directly...which I also successfully tested.
>
> But I don't really know the exact command that the installer is calling as
> it isn't being logged.  Using the ProcessMonitor does not show the program
> getting run if I change the installation directory during the install.
>
> However, I did do an experiment where I set the installation folder on the
> command line by setting INSTALLDIR to what is not defaulted in the
> installer.  At the end of the install, the program started when the checkbox
> was set.  This leads me to believe that the path to the executable is being
> resolved very early and subsequent changes are not being reflected in the
> custom action.
>
> You are certainly right about this being commonly implemented
> functionality.
>
> Thanks again
>
> John
>
> On 8/9/07, [EMAIL PROTECTED] <
> [EMAIL PROTECTED]> wrote:
>
> John,
>
>
>
> Be careful - Running from the shortcut may not be a completely valid test.
> You really need to launch it (e.g. using Start / Run) using exactly the
> same command line as Microsoft Installer will.
>
>
>
> You may want to try running the installation with ProcessMonitor running
> (you can get that from
> http://www.microsoft.com/technet/sysinternals/utilities/processmonitor.mspxif 
> you haven't encountered it before – although I haven't tried the version
> that was apparently released yesterday!). That will show you exactly what
> file(s) are being accessed etc. and may provide some hints about what is
> going wrong.
>
>
>
> What you are trying to accomplish is common enough that I think there
> would be a lot more traffic about it on the list if the tutorial was badly
> wrong. (As I said, I have used that mechanism myself to launch "readme"
> files with no trouble.)
>
>
>
> Hope you manage to get it resolved.
>
>
>
> Regards,
>
> Richard
>
>
>  --
>
> *From:* John Lalande [mailto:[EMAIL PROTECTED]
> *Sent:* Thursday, August 09, 2007 11:18 AM
> *To:* Foster, Richard - PAL
> *Cc:* wix-users@lists.sourceforge.net
> *Subject:* Re: [WiX-users] Run program after installation
>
>
>
> Richard
>
> It certainly is not a silly question and was worth checking.  I checked
> and the program does not depend on its location.  If I install to a
> non-default folder I can run the program from its shortcut.
>
> I am starting to think that perhaps this cannot be done as easily as the
> tutorial illustrates.
>
> Thanks for your response.
>
> John
>
> Richard wrote:
> >It may be a silly question (and hopefully is), but does the application
> >itself have any path-related dependencies? I.e. can you use the same
> >command line as Installer would use successfully, bearing in mind that
> >the working directory and the application's installation directory may
> >not be the same. I haven't launched an installed application using the
> >mechanism described, but I have triggered the opening of a specific file
> >from the location it was installed to without any trouble.
>   --
>
>
> * C O N F I D E N T I A L I T Y N O T I C E *
> ---
> The content of this e-mail is intended solely for the use of the
> individual or entity to whom it is addressed. If you have received this
> communication in error, be aware that forwarding it, copying it, or in any
> way disclosing its content to any other person, is strictly prohibited.
> Quixote Traffic Corporation is neither liable for the contents, nor for the
> proper, comple

[WiX-users] Publish Property functionality change b/w Wix 2 and 3?

[Steve S]

Hey guys,

I'm probably gonna have my rating nicked for this post as there are similar
topics about this but I'm struggling with a property publishing issue on a
control.

The example here is kinda silly because it's not really dependent upon the
Next here, but anyways... I upgraded from Wix 2.x to Wix 3.x and am having
an issue with the Publish Property that I used in my Wix 2.0 source.






The behavior I expect (and had before) is that the WIXUI_INSTALLPRIVILEGES
gets set for the next screen to LocalMachine or CurrentUser based on
Privileged.  The behavior I now get is that the Next button doesn't do
anything, as if it's disabled entirely :|

Appreciate the quick "Of course not dummy, here's why" answer here :)...
it's driving me nuts and I must not be looking at the right docs or
something :|

Steve
-- 
View this message in context: 
http://www.nabble.com/Publish-Property-functionality-change-b-w-Wix-2-and-3--tf4244148.html#a12077439
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Error 1625

[Wilson, Phil]

Do other MSI files install on that box?  That's useful information and
rules out policies of any kind. Somewhere in policy settings "Software
Restriction Policies" there is a list of file types that are not allowed
to run, and the MSI extension might be restricted, so whether other MSI
files install is useful data.  I don't believe the file extension
restriction is the same as the DisableMsi policy. 
 
I've seen reports that you can get this error if there have already been
failed attempts to install the product, due to left over junk in the
registry associated with the ProductCode guid. If this is the case,
changing the ProductCode guid might allow it to install. 
 

Phil Wilson 

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ravit
Shapira
Sent: Wednesday, August 08, 2007 7:54 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Error 1625



I want to add to my previous email that I searched for the value
"DisableMSI" and it doesn't exist in the registry, which means that the
Installer is always enabled.

So, I think that "DisableMSI" is not the cause of my problem.

 

Thanks,

Ravit



From: Ravit Shapira 
Sent: Wednesday, August 08, 2007 7:36 PM
To: 'wix-users@lists.sourceforge.net'
Subject: Error 1625

 

Hi,

 

I'm trying to run a setup on a Win2k3 server and I get error no' 1625:
"The system administrator has set the policies to prevent this
installation".

When I run the same setup on Vista it works. Currently the msi size is:
1.55 Giga Byte (I configured 5 cabs). Before that when it was 441MByte I
could run the setup with no error.

 

I have an administrator account on the Win2k3 server that I use.

 

When I searched online I found information about DisableMSI in:

http://msdn2.microsoft.com/en-us/library/Aa368304.aspx

http://blogs.msdn.com/windows_installer_team/archive/2005/07/18/442753.a
spx

 

Therefore, I checked the registry key:

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer  and I
saw that "EnableAdminTSRemote"  is equal to 1.

1.  Do you have any idea why I get this error? 
2.  If you think that it is caused by the value DisableMSI then what
should be the right value for win2k3 server. How can I change this
value?
How is it that I could run the msi when it was 0.5Giga, but when
I changed it to 1.5Giga I started to get error 1625? 

 

Thanks,

Ravit

 

 

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] KeyPath problem

[Patrice Lamarche]

Hello Peter,

 

Thanks you again for your answer. Worked if I deleted an file other 
than the first one :-)

 

Best regards,

 

Patrice Lamarche

 



De : Peter Marcu [mailto:[EMAIL PROTECTED] 
Envoyé : 8 août 2007 11:48
À : Patrice Lamarche; wix-users@lists.sourceforge.net
Objet : RE: [WiX-users] KeyPath problem

 

When no keypath is specified, it uses the first resource in the component. In 
your case it was the first file. In order to remove that file you need to 
remove the entire component. Note, that if you remove a component, you have to 
remove the entire feature. Removing a keypath file using a patch can be very 
tricky...

 



From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Patrice Lamarche
Sent: Wednesday, August 08, 2007 8:42 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] KeyPath problem

 

Hello,



I'm working with a patch. I receive this error

 

D:\Disk_X\Setup1.wxs(23) : error PYRO0243 : Component 
'comment_protect_once.pl_1' has a changed keypath

. Patches cannot change the keypath of a component.

 

Here my wxs 

 



 
  

 
  





   



 


  















 

I tried with keypath=false every where to and still have the problem. I thought 
when no keypath where specified, it use the directory.

 

Thanks 

 

Best Regards,

 

Patrice Lamarche

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Error 1625

[Ravit Shapira]

Thanks Bub! How can I verify that .msi package is digitally signed?

Ravit


From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 09, 2007 7:41 AM
To: Ravit Shapira
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Error 1625

Ravit Shapira wrote:
I'm trying to run a setup on a Win2k3 server and I get error no' 1625: "The 
system administrator has set the policies to prevent this installation".
When I run the same setup on Vista it works. Currently the msi size is:  1.55 
Giga Byte (I configured 5 cabs). Before that when it was 441MByte I could run 
the setup with no error.

Assuming the .msi package is digitally signed, it sounds like a SAFER problem. 
See 
http://blogs.msdn.com/heaths/archive/2007/01/11/known-issues-with-visual-studio-2005-service-pack-1.aspx
 for one discussion of the problem.



--

sig://boB

http://joyofsetup.com/
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Run program after installation

[John Lalande]

According to the tutorial, the FileKey attribute of the custom attribute is
set to the Id of the file you wish to run so I assume that it is trying to
run the executable directly...which I also successfully tested.

But I don't really know the exact command that the installer is calling as
it isn't being logged.  Using the ProcessMonitor does not show the program
getting run if I change the installation directory during the install.

However, I did do an experiment where I set the installation folder on the
command line by setting INSTALLDIR to what is not defaulted in the
installer.  At the end of the install, the program started when the checkbox
was set.  This leads me to believe that the path to the executable is being
resolved very early and subsequent changes are not being reflected in the
custom action.

You are certainly right about this being commonly implemented functionality.

Thanks again

John

On 8/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
>
>  John,
>
>
>
> Be careful - Running from the shortcut may not be a completely valid test.
> You really need to launch it (e.g. using Start / Run) using exactly the
> same command line as Microsoft Installer will.
>
>
>
> You may want to try running the installation with ProcessMonitor running
> (you can get that from
> http://www.microsoft.com/technet/sysinternals/utilities/processmonitor.mspxif 
> you haven't encountered it before – although I haven't tried the version
> that was apparently released yesterday!). That will show you exactly what
> file(s) are being accessed etc. and may provide some hints about what is
> going wrong.
>
>
>
> What you are trying to accomplish is common enough that I think there
> would be a lot more traffic about it on the list if the tutorial was badly
> wrong. (As I said, I have used that mechanism myself to launch "readme"
> files with no trouble.)
>
>
>
> Hope you manage to get it resolved.
>
>
>
> Regards,
>
> Richard
>
>
>  --
>
> *From:* John Lalande [mailto:[EMAIL PROTECTED]
> *Sent:* Thursday, August 09, 2007 11:18 AM
> *To:* Foster, Richard - PAL
> *Cc:* wix-users@lists.sourceforge.net
> *Subject:* Re: [WiX-users] Run program after installation
>
>
>
> Richard
>
> It certainly is not a silly question and was worth checking.  I checked
> and the program does not depend on its location.  If I install to a
> non-default folder I can run the program from its shortcut.
>
> I am starting to think that perhaps this cannot be done as easily as the
> tutorial illustrates.
>
> Thanks for your response.
>
> John
>
> Richard wrote:
> >It may be a silly question (and hopefully is), but does the application
> >itself have any path-related dependencies? I.e. can you use the same
> >command line as Installer would use successfully, bearing in mind that
> >the working directory and the application's installation directory may
> >not be the same. I haven't launched an installed application using the
> >mechanism described, but I have triggered the opening of a specific file
> >from the location it was installed to without any trouble.
>
> --
>
> * C O N F I D E N T I A L I T Y N O T I C E *
> ---
> The content of this e-mail is intended solely for the use of the
> individual or entity to whom it is addressed. If you have received this
> communication in error, be aware that forwarding it, copying it, or in any
> way disclosing its content to any other person, is strictly prohibited.
> Quixote Traffic Corporation is neither liable for the contents, nor for the
> proper, complete and timely transmission of (the information contained in)
> this communication. If you have received this communication in error, please
> notify the author by replying to this e-mail immediately and delete the
> material from any computer.
>
>
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Registering an EXE via a Custom Action

[Tanikella, Rajanikanth (SCR US)]

Running msiexec with '/log installationLog.txt' the log file contains:

EXEREG_PckgInstllr
Action 17:17:03: EXEREG_PckgInstllr.
Action start 17:17:03: EXEREG_PckgInstllr.
EXEREG_PckgInstllr: 
Action ended 17:17:03: EXEREG_PckgInstllr. Return value 1. 

I take this to mean it ran and succeeded.  Still, the app that depends
upon it does not find it, nor does it exist in the registry until I
manually register it.

Any further suggestions?  I'm going to try Orca to see if it reveals
anything.  Any suggestions of what to look for?

I love inheriting code... =)

Raj

> -Original Message-
> From: Brian Simoneau [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, August 09, 2007 11:04 AM
> To: Tanikella, Rajanikanth (SCR US); wix-users@lists.sourceforge.net
> Subject: RE: [WiX-users] Registering an EXE via a Custom Action
> 
> That would imply a different issue.  I would look for your 
> custom action
> in the log to see if it is being run.
> 
> -Brian Simoneau 
> 
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of 
> Tanikella,
> Rajanikanth (SCR US)
> Sent: Thursday, August 09, 2007 9:56 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Registering an EXE via a Custom Action
> 
> Thanks Brian,
> 
> Upon closer examination, I realize I misspoke:  My custom action is
> scheduled after an action that is scheduled BEFORE InstallFinalize.  I
> recall that scheduling mine to run after InstallFinalize results in an
> error which indicates that mine is an 'in-script' action and 
> can only be
> scheduled between InstallInitialize and InstallFinalize.
> 
> Does that suggest that my failure is due to a different issue?
> 
> Raj
> 
> > -Original Message-
> > From: Brian Simoneau [mailto:[EMAIL PROTECTED] 
> > Sent: Thursday, August 09, 2007 9:28 AM
> > To: Tanikella, Rajanikanth (SCR US); wix-users@lists.sourceforge.net
> > Subject: RE: [WiX-users] Registering an EXE via a Custom Action
> > 
> > If your custom action is sequenced after InstallFinalize, 
> > then it should
> > be immediate.  The commit and deferred types can only be 
> used between
> > InstallInitialize and InstallFinalize.
> > 
> > -Brian Simoneau
> ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> > 
> 
> --
> --
> -
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and 
> a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Run program after installation

[John Lalande]

Richard

It certainly is not a silly question and was worth checking.  I checked and
the program does not depend on its location.  If I install to a non-default
folder I can run the program from its shortcut.

I am starting to think that perhaps this cannot be done as easily as the
tutorial illustrates.

Thanks for your response.

John

Richard wrote:
>It may be a silly question (and hopefully is), but does the application
>itself have any path-related dependencies? I.e. can you use the same
>command line as Installer would use successfully, bearing in mind that
>the working directory and the application's installation directory may
>not be the same. I haven't launched an installed application using the
>mechanism described, but I have triggered the opening of a specific file
>from the location it was installed to without any trouble.
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Registering an EXE via a Custom Action

[Brian Simoneau]

That would imply a different issue.  I would look for your custom action
in the log to see if it is being run.

-Brian Simoneau 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tanikella,
Rajanikanth (SCR US)
Sent: Thursday, August 09, 2007 9:56 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Registering an EXE via a Custom Action

Thanks Brian,

Upon closer examination, I realize I misspoke:  My custom action is
scheduled after an action that is scheduled BEFORE InstallFinalize.  I
recall that scheduling mine to run after InstallFinalize results in an
error which indicates that mine is an 'in-script' action and can only be
scheduled between InstallInitialize and InstallFinalize.

Does that suggest that my failure is due to a different issue?

Raj

> -Original Message-
> From: Brian Simoneau [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, August 09, 2007 9:28 AM
> To: Tanikella, Rajanikanth (SCR US); wix-users@lists.sourceforge.net
> Subject: RE: [WiX-users] Registering an EXE via a Custom Action
> 
> If your custom action is sequenced after InstallFinalize, 
> then it should
> be immediate.  The commit and deferred types can only be used between
> InstallInitialize and InstallFinalize.
> 
> -Brian Simoneau
___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] checking registry entry

[Frédéric Viollet]

Bob Arnson a écrit :

Frédéric Viollet wrote:
Guid="924B3E41-7157-4927-B892-8D52D8A392BD">

 MAXHEAPSIZE AND (MAXHEAPSIZE< 256)
 
   Type="integer" Action="write" />

 


I get the error : Name cannot begin with the ' ' character, 
hexadecimal value 0x20


You can't use a "bare" < character in an XML document. You need to use 
CDATA or < instead.



Yes indeed. I tries with CDATA, it works fine.
Thanks a lot for your help.

Fred
begin:vcard
fn;quoted-printable:Fr=C3=A9d=C3=A9ric Viollet
n;quoted-printable:Viollet;Fr=C3=A9d=C3=A9ric
org:Bull, Architect of an Open World (TM);Evidian S.A.
adr;quoted-printable:;;Rue Jean Jaur=C3=A8s;Les Clayes Sous Bois;;78340;France
email;internet:[EMAIL PROTECTED]
title:Software Engineer
tel;work:01 30 80 77 34
url:http://www.evidian.com - http://www.bull.com
version:2.1
end:vcard

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] scheduleReboot

[Bob Arnson]

Mark Line wrote:
hopefully be my last question! my installer prompts for a reboot after 
install, however i am not coding this, for example 


MSI will prompt for a reboot if it had to replace in-use files. Check a 
verbose log; MSI will detail when it schedules a reboot.


--
sig://boB
http://joyofsetup.com/

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] checking registry entry

[Bob Arnson]

Frédéric Viollet wrote:
>  Guid="924B3E41-7157-4927-B892-8D52D8A392BD">
>  MAXHEAPSIZE AND (MAXHEAPSIZE< 256)
>  
> Type="integer" Action="write" />
>  
> 
>
> I get the error : Name cannot begin with the ' ' character, 
> hexadecimal value 0x20

You can't use a "bare" < character in an XML document. You need to use 
CDATA or < instead.

-- 
sig://boB
http://joyofsetup.com/



-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Error 1625

[Bob Arnson]

Ravit Shapira wrote:


I'm trying to run a setup on a Win2k3 server and I get error no' 
*1625*: *"The system administrator has set the policies to prevent 
this installation".*


When I run the same setup on Vista it works. Currently the msi size 
is:  1.55 Giga Byte (I configured 5 cabs). Before that when it was 
441MByte I could run the setup with no error.




Assuming the .msi package is digitally signed, it sounds like a SAFER 
problem. See 
http://blogs.msdn.com/heaths/archive/2007/01/11/known-issues-with-visual-studio-2005-service-pack-1.aspx 
for one discussion of the problem.


--
sig://boB
http://joyofsetup.com/

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] looking for a less time consuming Multilanguage installer

[Bob Arnson]

Magus wrote:
> Right now it doens't because the people I work with don't seem to realize
> that a file greater than 2 gb is a bad idea.
>   

If it's just laying out files, it's probably just disk i/o that causes 
long build times. Can you verify that with -v?

-- 
sig://boB
http://joyofsetup.com/



-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Votive and Project References -- RESEND

[Quattro IV]

I didn't get a response so I'm resending this:

Hello, I'm having an issue referencing a WiX library from a standard WiX
module. For some reason I get "Unresolved reference to symbol..." errors
when I just reference the WiX library project directly instead of the
referencing the output of the project (.wixlib file) Anyone get this to
work?

Also, when I reference the output file directly it creates a hardcoded path
and I have to manually update the .wixproj directly to fix it, is this a
bug?

Any help is appreciated.

Reese
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] HKLM - purposely persistent

[Simon Topley]

Thanks for the tip Stefan. Is this a tried and tested method? My keys
still seem to disappear.

Simon

-Original Message-
From: Stefan Pavlik [mailto:[EMAIL PROTECTED] 
Sent: 09 August 2007 12:08
To: Simon Topley
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] HKLM - purposely persistent

Hi Simon

You can place the registry key to one Component and add
[EMAIL PROTECTED]"yes".

It will ensure that the component (and thus the  registry key) wil not
be removed during uninstall.

regards

Stefan

Simon Topley wrote:
> Greetings one and all!
> 
> It's been a while but I have returned once again to conquer the land 
> of installers. I have a pretty simple problem with my registry 
> settings. I create keys all over the LM and CU hives in the registry 
> however I wish to leave something behind in "LM\software\company
name\product version".
> I have used "createkey" to make this key and not 
> "createKeyAndRemoveKeyOnUninstall". Sadly my key is still removed. I 
> know it's not exactly good manners to leave things in the registry but

> my hand is being forced here. Obviously there are many other keys in 
> the same place that do need to be removed on uninstall.
> 
> Any help would be good. 
> 
> Simon
> The information contained in this e-mail is likely to be confidential 
> and may be legally privileged. It is intended only for the addressee. 
> If you have received this message in error please notify the sender 
> immediately at the above address. The disclosure, copying or 
> distribution of this message or its contents without the prior 
> approval of Wallingford Software is strictly prohibited. Wallingford 
> Software is not liable for unauthorised disclosures nor for subsequent

> actions or omissions in reliance upon them.
> 
> Registered in the UK, company no: 02288719 Wallingford Software 
> Limited, Howbery Park, Wallingford, Oxfordshire, OX10 8BA
> 
> --
> --- This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a
browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/ 
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 

--
Stefan Pavlik | [EMAIL PROTECTED]
Whitestein Technologies s.r.o. | www.whitestein.com Panenska 28 | 811 03
Bratislava | Slovak Republic Main +421 2 5443-5502 | Direct +421 2
5930-0735
The information contained in this e-mail is likely to be confidential and
may be legally privileged. It is intended only for the addressee. If you
have received this message in error please notify the sender immediately at
the above address. The disclosure, copying or distribution of this message
or its contents without the prior approval of Wallingford Software is
strictly prohibited. Wallingford Software is not liable for
unauthorised disclosures nor for subsequent actions or omissions in reliance
upon them.

Registered in the UK, company no: 02288719
Wallingford Software Limited, Howbery Park, Wallingford, Oxfordshire, OX10 8BA

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Registering an EXE via a Custom Action

[Tanikella, Rajanikanth (SCR US)]

Thanks Brian,

Upon closer examination, I realize I misspoke:  My custom action is
scheduled after an action that is scheduled BEFORE InstallFinalize.  I
recall that scheduling mine to run after InstallFinalize results in an
error which indicates that mine is an 'in-script' action and can only be
scheduled between InstallInitialize and InstallFinalize.

Does that suggest that my failure is due to a different issue?

Raj

> -Original Message-
> From: Brian Simoneau [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, August 09, 2007 9:28 AM
> To: Tanikella, Rajanikanth (SCR US); wix-users@lists.sourceforge.net
> Subject: RE: [WiX-users] Registering an EXE via a Custom Action
> 
> If your custom action is sequenced after InstallFinalize, 
> then it should
> be immediate.  The commit and deferred types can only be used between
> InstallInitialize and InstallFinalize.
> 
> -Brian Simoneau
___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Registering an EXE via a Custom Action

[Brian Simoneau]

If your custom action is sequenced after InstallFinalize, then it should
be immediate.  The commit and deferred types can only be used between
InstallInitialize and InstallFinalize.

-Brian Simoneau

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tanikella,
Rajanikanth (SCR US)
Sent: Wednesday, August 08, 2007 6:36 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Registering an EXE via a Custom Action

Hello All,

I'm building an MSI using WiX3, and I'm encountering a problem:  I've a
custom action:



It is sequenced to be executed after 'InstallFinalize'.  (Actually, it
is sequenced before another custom action that is sequenced to run after
'InstallFinalize'.)

The problem I encounter is that once the installer is complete the log
indicates no error, but the installed application throws a 'class not
registered' error.  The registry contains no trace of the registered EXE
either.

If, however I execute 'PckgInstllr.exe /regserver' from a DOS prompt,
then the installed app works, and the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\PckgInstllr.EXE\AppID is set
to its GUID.

I have tried setting the CustomAction's Execute attribute to 'deferred'
as well, but I get the same result.  Can anyone shed some light on this
for me?

Thanks.

Raj


Rajanikanth Tanikella 
Member of Technical Staff
Siemens Corporate Research
Email: rajanikanth dot tanikella at siemens dot com 



-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] scheduleReboot

[Mark Line]

hopefully be my last question! my installer prompts for a reboot after install, 
however i am not coding this, for example 


  



it seems to think that it needs one? however it doesn't! i am moving some files 
into system32, is this why it prompts for a reboot? however the software works 
correctly without an reboot, is there anyway i can stop the promt appearing?-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Run program after installation

[Richard.Foster]

John,

 

It may be a silly question (and hopefully is), but does the application
itself have any path-related dependencies? I.e. can you use the same
command line as Installer would use successfully, bearing in mind that
the working directory and the application's installation directory may
not be the same. I haven't launched an installed application using the
mechanism described, but I have triggered the opening of a specific file
from the location it was installed to without any trouble.

 

Regards,

Richard

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John
Lalande
Sent: Wednesday, August 08, 2007 7:11 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Run program after installation

 

Following the steps outlined at the excellent tutorial at
http://www.tramontana.co.hu/wix/lesson8.php#8.6 works great unless the
user changes the installation directory from the default. 

When going down the happy path the log says that the LaunchFile custom
action returns 0 and the program starts.  If the installation directory
is changed during installation the log says that LaunchFile returns 1631
and the program does not start. 

Is there a way around this problem or another way to run a newly
installed program from the installer.

John




* C O N F I D E N T I A L I T Y N O T I C E *
---
The content of this e-mail is intended solely for the use of the individual or 
entity to whom it is addressed. If you have received this communication in 
error, be aware that forwarding it, copying it, or in any way disclosing its 
content to any other person, is strictly prohibited. Quixote Traffic 
Corporation is neither liable for the contents, nor for the proper, complete 
and timely transmission of (the information contained in) this communication. 
If you have received this communication in error, please notify the author by 
replying to this e-mail immediately and delete the material from any computer.


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Problems with shortcuts

[Alexei]

Seems to me you need a custom action in order to specify which exact program
you wish to use to open the file.

So try setting up a custom action to open the file in IE, or whatever.

 C:\Program Files\Internet Explorer\IEXPLORE.EXE



Then you need to schedule it:

  


Have a look on  http://www.tramontana.co.hu/wix/lesson3.php#3.2 here , they
probably do a much better job of explaining that then me.

You may encounter the problem of the action being executed too early and
thus it may be unable to locate the file you wish to open (presuming this
file is installed by the installer).
To get around this I think you need a deffered custom action, but I'm not
100% on that.
Anyone else got any ideas?

Regards, Alexei
-- 
View this message in context: 
http://www.nabble.com/Problems-with-shortcuts-tf4240759.html#a12071249
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] HKLM - purposely persistent

[Stefan Pavlik]

Hi Simon

You can place the registry key to one Component and add
[EMAIL PROTECTED]"yes".

It will ensure that the component (and thus the  registry key) wil
not be removed during uninstall.

regards

Stefan

Simon Topley wrote:
> Greetings one and all!
> 
> It's been a while but I have returned once again to conquer the land of
> installers. I have a pretty simple problem with my registry settings. I
> create keys all over the LM and CU hives in the registry however I wish
> to leave something behind in "LM\software\company name\product version".
> I have used "createkey" to make this key and not
> "createKeyAndRemoveKeyOnUninstall". Sadly my key is still removed. I
> know it's not exactly good manners to leave things in the registry but
> my hand is being forced here. Obviously there are many other keys in the
> same place that do need to be removed on uninstall.
> 
> Any help would be good. 
> 
> Simon
> The information contained in this e-mail is likely to be confidential and
> may be legally privileged. It is intended only for the addressee. If you
> have received this message in error please notify the sender immediately at
> the above address. The disclosure, copying or distribution of this message
> or its contents without the prior approval of Wallingford Software is
> strictly prohibited. Wallingford Software is not liable for
> unauthorised disclosures nor for subsequent actions or omissions in reliance
> upon them.
> 
> Registered in the UK, company no: 02288719
> Wallingford Software Limited, Howbery Park, Wallingford, Oxfordshire, OX10 8BA
> 
> -
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 

-- 
Stefan Pavlik | [EMAIL PROTECTED]
Whitestein Technologies s.r.o. | www.whitestein.com
Panenska 28 | 811 03 Bratislava | Slovak Republic
Main +421 2 5443-5502 | Direct +421 2 5930-0735

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] HKLM - purposely persistent

[Simon Topley]

Greetings one and all!

It's been a while but I have returned once again to conquer the land of
installers. I have a pretty simple problem with my registry settings. I
create keys all over the LM and CU hives in the registry however I wish
to leave something behind in "LM\software\company name\product version".
I have used "createkey" to make this key and not
"createKeyAndRemoveKeyOnUninstall". Sadly my key is still removed. I
know it's not exactly good manners to leave things in the registry but
my hand is being forced here. Obviously there are many other keys in the
same place that do need to be removed on uninstall.

Any help would be good. 

Simon
The information contained in this e-mail is likely to be confidential and
may be legally privileged. It is intended only for the addressee. If you
have received this message in error please notify the sender immediately at
the above address. The disclosure, copying or distribution of this message
or its contents without the prior approval of Wallingford Software is
strictly prohibited. Wallingford Software is not liable for
unauthorised disclosures nor for subsequent actions or omissions in reliance
upon them.

Registered in the UK, company no: 02288719
Wallingford Software Limited, Howbery Park, Wallingford, Oxfordshire, OX10 8BA

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] DLLs and uninstalls

[Alexei]

Phil Wilson wrote:
> 
> See if the log contains any of this type of thing:
> 
> MSI (s) (CC:24) [13:58:42:909]: Disallowing uninstallation of component:
> {15239D33-DAE9-46F3-BD59-264A2068B3BC} since another client exists
> 
> They'll be before those Action: Null reports (which is why they might be
> saying null).
> 
I've done a number of searches through the uninstall log and there is
nowhere that says anything like that.
There ARE a bunch of lines that say:
MSI (s) (3C:D8) [17:52:54:296]: Using cached product context: User
non-assigned for product: FBF1218549BD3C74A8A8A9D31F7ED7C1
The last of these being just before the TARGETDIR property is set.

There is also a slightly disturbing fragment which says:
MSI (s) (3C:D8) [17:52:54:265]: Using cached product context: User
non-assigned for product: FBF1218549BD3C74A8A8A9D31F7ED7C1
MSI (s) (3C:D8) [17:52:54:265]: Using cached product context: User
non-assigned for product: FBF1218549BD3C74A8A8A9D31F7ED7C1
MSI (s) (3C:D8) [17:52:54:265]: Package name retrieved from configuration
data: 'LanMon Extractor v2.5.msi'
MSI (s) (3C:D8) [17:52:54:265]: Using cached product context: User
non-assigned for product: FBF1218549BD3C74A8A8A9D31F7ED7C1
MSI (s) (3C:D8) [17:52:54:265]: Determined that existing product (either
this product or the product being upgraded with a patch) is installed
per-user.
MSI (s) (3C:D8) [17:52:54:265]: Note: 1: 2205 2:  3: Error 
MSI (s) (3C:D8) [17:52:54:265]: Note: 1: 2729 
MSI (s) (3C:D8) [17:52:54:265]: Note: 1: 2729 
MSI (s) (3C:D8) [17:52:54:265]: Note: 1: 2729 
MSI (s) (3C:D8) [17:52:54:265]: Note: 1: 2729 
MSI (s) (3C:D8) [17:52:54:265]: Note: 1: 2729 
MSI (s) (3C:D8) [17:52:54:265]: Note: 1: 2729 
MSI (s) (3C:D8) [17:52:54:265]: Note: 1: 2729 
MSI (s) (3C:D8) [17:52:54:265]: Note: 1: 2729 
MSI (s) (3C:D8) [17:52:54:265]: Note: 1: 2729 
MSI (s) (3C:D8) [17:52:54:265]: Note: 1: 2729 
MSI (s) (3C:D8) [17:52:54:265]: Note: 1: 2729 
MSI (s) (3C:D8) [17:52:54:265]: Note: 1: 2729 
MSI (s) (3C:D8) [17:52:54:265]: Note: 1: 2729 
MSI (s) (3C:D8) [17:52:54:265]: Note: 1: 2729 
MSI (s) (3C:D8) [17:52:54:265]: Note: 1: 2729 
MSI (s) (3C:D8) [17:52:54:265]: Note: 1: 2729 
MSI (s) (3C:D8) [17:52:54:265]: Note: 1: 2262 2: AdminProperties 3:
-2147287038  

Is this something else to be concerned about?
-- 
View this message in context: 
http://www.nabble.com/DLLs-and-uninstalls-tf4229019.html#a12069204
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Conditional Statement Problem

[Rob Hamflett]

Give your property an explicit starting value with [EMAIL PROTECTED], which 
gets overridden by the 
RegistrySearch.  Then you can base your condition against this value.

Rob

Schuett, Michael (VMC) wrote:
> Hello,
> 
> I'm reading a DWORD value from the registry using RegistrySearch. (WiX 
> 3.0.2925.0)
> 
> 
> 
>  
> Key='SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\FooSoft 1.0' />
> 
> 
> 
> I understand DA_VER is an empty string if "Version" isn't found. If it is 
> found, DA_VER will start with '#' followed by the value of Version.
> 
> I want to bail out of the install if the DWORD value doesn't exist. I've 
> tried the following and none of them work.
> 
> 
>  NOT DA_VER 
> 
>  DA_VER = "" 
> 
>  NOT (DA_VER << "#")  (This 
> doesn't even compile)
> 
> 
> Any ideas/suggestions?
> 
> I'm assuming all the Windows Install Conditional Statement Syntax (see: 
> http://msdn2.microsoft.com/en-us/library/aa368012.aspx) is valid in WiX.
> 
> Thanks,
> Mike
> 
> -
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] McAfee GroupShield Alert (INSAD OFFICE)

[admin]

McAfee GroupShield™ Alert 

McAfee GroupShield discovered a problem with the following email. See
your system administrator for further information. 

Date/Time sent: 09 Aug 2007 09:32:42
Subject line: [WiX-users] You've received a greeting card from a Mate!
From: [EMAIL PROTECTED]
To: wix-users@lists.sourceforge.net
Action taken: Deleted Message
Reason: Anti-Virus
Rule Group: 


Copyright © 1993-2003, Networks Associates Technology, Inc.
All Rights Reserved.
http://www.mcafeesecurity.com   

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users