Why are you setting TARGETDIR with a custom action?    This is not usually a 
good practice, and overriding TARGETDIR is usually reserved for activities like 
admin installs.  If you want to set up a variable InstallLocation, there are 
much better patterns to follow to achieve this.

--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.®
Shawnee Mission, KS  66227
Office:  913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com 



-----Original Message-----
From: Tony White [mailto:twh...@ent.com] 
Sent: Wednesday, July 31, 2013 5:24 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] adding event source during install

>From the log file it seems my custom action that sets the TARGETDIR is the 
>thing throwing the error:

Action 16:03:18: SetTARGETDIR.
Action start 16:03:18: SetTARGETDIR.
MSI (c) (58:18) [16:03:18:241]: PROPERTY CHANGE: Modifying TARGETDIR property. 
Its current value is 'C:\'. Its new value: 'C:\Program Files\Ent Federal Credit 
Union\'.
MSI (c) (58:18) [16:03:18:241]: Note: 1: 1324 2: ? 3: 1 MSI (c) (58:18) 
[16:03:18:241]: Note: 1: 2205 2:  3: Error MSI (c) (58:18) [16:03:18:241]: 
Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 
1324 Error 1324. The folder path '?' contains an invalid character.
MSI (c) (58:18) [16:03:23:420]: Note: 1: 2205 2:  3: Error MSI (c) (58:18) 
[16:03:23:420]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` 
WHERE `Error` = 1709 MSI (c) (58:18) [16:03:23:420]: Product: LogonTimerService 
-- Error 1324. The folder path '?' contains an invalid character.

Action ended 16:03:23: SetTARGETDIR. Return value 3.
MSI (c) (58:18) [16:03:23:422]: Doing action: FatalError


                <CustomAction Id="SetTARGETDIR" Directory="TARGETDIR" 
Value="[ProgramFiles64Folder][Manufacturer]" Return="check" />
                <InstallUISequence>
                        <Custom Action="SetTARGETDIR" After="CostFinalize" />
                </InstallUISequence>

So then the question is. Why does adding the EventSource node cause the custom 
action to fail?
I'm going to get another log with the EventSource removed and see what is 
different.

Thanks,

Tony
-----Original Message-----
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Wednesday, July 31, 2013 3:45 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] adding event source during install

So, what does NETFRAMEWORK20INSTALLROOTDIR64 evaluate to from the install log?

--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.®
Shawnee Mission, KS  66227
Office:  913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com




-----Original Message-----
From: Tony White [mailto:twh...@ent.com]
Sent: Wednesday, July 31, 2013 4:37 PM
To: 'wix-users@lists.sourceforge.net'
Subject: [WiX-users] adding event source during install

I would like to add this node to my component, to make sure a specific event 
source exists:
<util:EventSource
Log="Application"
       Name="LogonTimer"
       EventMessageFile="[NETFRAMEWORK20INSTALLROOTDIR64]EventLogMessages.dll" 
/>

I have these also:
<PropertyRef Id="NETFRAMEWORK20" />
<PropertyRef Id="NETFRAMEWORK20INSTALLROOTDIR64" /> <PropertyRef 
Id="NETFRAMEWORK40FULL" /> <PropertyRef Id="NETFRAMEWORK40FULLINSTALLROOTDIR64" 
/>

Just in case adding more of them would make the problem go away.
And this:
xmlns:util="https://urldefense.proofpoint.com/v1/url?u=http://schemas.microsoft.com/wix/UtilExtension&k=B%2B6yjDIOl%2FIBFdn7TPTJ1w%3D%3D%0A&r=YFkUslLBsKTVopesyo1A5w%3D%3D%0A&m=i9T88zrG0Ae6T%2BrQJNzojxCMwh8Zn88M36g7zy93G4c%3D%0A&s=d4af28933ca92a0227b24ff2b3b8cfc56b3211014a888e74f31ef5f020c14fc4";

The project builds, but as soon as the msi runs it throws an error "The folder 
path '?' has an invalid character" (well duh, ? is invalid) If I comment this 
EventSource node out, the installer runs just fine.
I have tried 
EventMessageFile="C:\Windows\Microsoft.NET\Framework64\v4.0.30319\EventLogMessages.dll",
 but even that gives the same message.
I've googled until my googler is sore, can't discover what is wrong.

Thanks,

Tony



This Email is covered by the Electronic Communication Privacy Act, 18 U.S.C 
2510-2521 and may be legally privileged. The information contained in this 
Email is intended only for the use of the individual or entity named above. If 
the reader of this message is not the intended recipient, or the employee or 
agent responsible to deliver it to the intended recipient, you are hereby 
notified that any dissemination, distribution or copying of this communication 
is strictly prohibited. If you have received this communication in error please 
immediately notify us by telephone and destroy the original message.
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent caught 
up. So what steps can you take to put your SQL databases under version control? 
Why should you start doing it? Read more to find out.
https://urldefense.proofpoint.com/v1/url?u=http://pubads.g.doubleclick.net/gampad/clk?id%3D49501711%26iu%3D/4140/ostg.clktrk&k=B%2B6yjDIOl%2FIBFdn7TPTJ1w%3D%3D%0A&r=YFkUslLBsKTVopesyo1A5w%3D%3D%0A&m=i9T88zrG0Ae6T%2BrQJNzojxCMwh8Zn88M36g7zy93G4c%3D%0A&s=f2bd5c86266ab7f684db698e1f8f0767e577f26c8611423aefea801191142b53
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://urldefense.proofpoint.com/v1/url?u=https://lists.sourceforge.net/lists/listinfo/wix-users&k=B%2B6yjDIOl%2FIBFdn7TPTJ1w%3D%3D%0A&r=YFkUslLBsKTVopesyo1A5w%3D%3D%0A&m=i9T88zrG0Ae6T%2BrQJNzojxCMwh8Zn88M36g7zy93G4c%3D%0A&s=68218b7001788b0269a748059c466cd9ab04496b64651e1d91cc0453416bff08
NOTICE: This electronic mail message and any files transmitted with it are 
intended exclusively for the individual or entity to which it is addressed. The 
message, together with any attachment, may contain confidential and/or 
privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution is strictly prohibited. If you have received this message in 
error, please immediately advise the sender by reply email and delete all 
copies.


------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent caught 
up. So what steps can you take to put your SQL databases under version control? 
Why should you start doing it? Read more to find out.
https://urldefense.proofpoint.com/v1/url?u=http://pubads.g.doubleclick.net/gampad/clk?id%3D49501711%26iu%3D/4140/ostg.clktrk&k=B%2B6yjDIOl%2FIBFdn7TPTJ1w%3D%3D%0A&r=YFkUslLBsKTVopesyo1A5w%3D%3D%0A&m=i9T88zrG0Ae6T%2BrQJNzojxCMwh8Zn88M36g7zy93G4c%3D%0A&s=f2bd5c86266ab7f684db698e1f8f0767e577f26c8611423aefea801191142b53
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://urldefense.proofpoint.com/v1/url?u=https://lists.sourceforge.net/lists/listinfo/wix-users&k=B%2B6yjDIOl%2FIBFdn7TPTJ1w%3D%3D%0A&r=YFkUslLBsKTVopesyo1A5w%3D%3D%0A&m=i9T88zrG0Ae6T%2BrQJNzojxCMwh8Zn88M36g7zy93G4c%3D%0A&s=68218b7001788b0269a748059c466cd9ab04496b64651e1d91cc0453416bff08


This Email is covered by the Electronic Communication Privacy Act, 18 U.S.C 
2510-2521 and may be legally privileged. The information contained in this 
Email is intended only for the use of the individual or entity named above. If 
the reader of this message is not the intended recipient, or the employee or 
agent responsible to deliver it to the intended recipient, you are hereby 
notified that any dissemination, distribution or copying of this communication 
is strictly prohibited. If you have received this communication in error please 
immediately notify us by telephone and destroy the original message.

------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent caught 
up. So what steps can you take to put your SQL databases under version control? 
Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.


------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to