Yes, this bug was reported directly to me by two other people in the past week. 
I should have made sure there was bug logged on SF, but there hasn't been so 
far.

I have already checked in the fix, so tomorrow's WiX build will resolve the 
issue.

Anyway thanks for reporting it.

-Jason-

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher 
Karper
Sent: Thursday, June 05, 2008 2:21 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] DTF Mystery Issues

I've been having DTF bomb out from time to time on an otherwise alright
installer.  If I rerun the installer immediately, it works fine.  I have 3
managed CA's in this installer, and once about every 10 times I run it, one
of them fails.

For instance, I have a CA that builds up SQL queries with formatted strings,
and instead of running successfully as it should, it blew up and I got this
in the log:
--------------------------------------------------------------------------------
MSI (s) (4C:EC) [17:13:48:656]: Doing action: FormatSqlScript
Action 17:13:48: FormatSqlScript.
Action start 17:13:48: FormatSqlScript.
MSI (s) (4C:00) [17:13:48:683]: Invoking remote custom action. DLL:
C:\Windows\Installer\MSID38E.tmp, Entrypoint: FormatSqlScript
MSI (s) (4C:A0) [17:13:48:683]: Generating random cookie.
MSI (s) (4C:A0) [17:13:48:693]: Created Custom Action Server with PID 4060
(0xFDC).
MSI (s) (4C:04) [17:13:48:733]: Running as a service.
MSI (s) (4C:04) [17:13:48:735]: Hello, I'm your 64bit Impersonated custom
action server.
SFXCA: Extracting custom action to temporary directory:
C:\Windows\Installer\MSID38E.tmp-\
SFXCA: Binding to CLR version v2.0.50727
Calling custom action
triCerat.Installer.CustomActions!triCerat.Installer.CustomActions.SqlFormattedScript.FormatSqlScript
Entering FormatSqlScript(...)
MSI (s) (4C!50) [17:13:49:679]: Note: 1: 2262 2: SqlFormattedScript 3:
-2147287038
MSI (s) (4C!50) [17:13:49:691]: PROPERTY CHANGE: Modifying
SqlScriptsFormatted property. Its current value is '0'. Its new value:
'lDb_`, `Component_`, `SQL`, `User_`, `Attributes`, `Sequence` FROM
`SqlString`'.
Action ended 17:13:54: FormatSqlScript. Return value 3.
--------------------------------------------------------------------------------

Most times, I won't see anything in the log, other than "Return value 3."
even though I wrapped my entire method in a try-catch statement.   To me, it
looks like the native wrapper is getting confused about the data going
across it's named pipe and crashes out, but I'm hardly an expert on the
inner workings.

Just thought I'd bring it up, and see if anyone had any thoughts on this,
and how to reduce the number of times it happens.


Chris
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to