Re: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec

2012-01-26 Thread Christopher Painter
Blair,


  While I never knew you were doing it at the time, thank you soo much for 
your efforts on this sneakly little critter of a bug.   DTF has a special 
place in my heart ( I'm sure you saw all my blog posts over the years 
evangelizing the need for managed code custom actions ) and your efforts 
probably took DTF's reliability from 3 9's to 4 9's.   That is an 
accomplishment.  


 FWIW, I recall reporting a bug a few years back where an InstallUtil 
custom action was changing the environment and then DTF would break because 
sfca couldn't launch RunDll.  It was tricky because the InstallUtil CA came 
from a merge module and depending on how it got sequenced the bug would 
sometimes happen and sometimes not.   I worked with Jason on that one and 
he made a fix.   That probably took us from 2 9's to 3 9's but your bug 
above is an even bigger deal.  Good job!


Chris



From: "Blair" 

Sent: Wednesday, January 25, 2012 8:56 PM

To: chr...@iswix.com, "General discussion for Windows Installer XML 
toolset." , "Neil Sleightholm" 


Subject: RE: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec


Except for that one repeatable machine, the problem always "went away" 
upon

retry (the same behavior you all have reported). That one machine was able

to repro more than once in a row, and after about four days I even got it 
to

repro in the debugger. That's when I finally discovered exactly what was

happening, and then I was able to stage a repro at will.


I submitted the fix to WiX, and a couple of weeks later walked another 
team

through their attempts to verify the fix.


Blair


-Original Message-

From: Christopher Painter [mailto:chr...@iswix.com] 

Sent: Wednesday, January 25, 2012 11:57 AM

To: Neil Sleightholm; General discussion for Windows Installer XML 
toolset.

Subject: Re: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec


I'm going to be creating a trojan installer that serves as a health check

and deploying it daily to 2200 machines.  I'll be able to stress test the

fix made in 3.6 and see what happen.s





From: "Neil Sleightholm" 


Sent: Wednesday, January 25, 2012 1:06 PM


To: "General discussion for Windows Installer XML toolset." 

, "chr...@iswix.com" 


Subject: RE: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec


As Chris said excellent information. Mine problem was with 3.5 and this 
ties

in with what I was seeing; on my VMs running on an i7 host I never saw the

problem but the tester often got it on his lower powered host. He need 
move

to a VM on an ESX host and the problem largely went away. I think I will 
try

the newer SfxCA.dll (or I might just go for 3.6).


Thanks


Neil


-Original Message-


From: Blair [mailto:os...@live.com] 


Sent: 25 January 2012 18:14


To: 'General discussion for Windows Installer XML toolset.';

chr...@iswix.com


Subject: Re: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec


Are these problems in 3.5 or 3.6? Last year I discovered a defect in DTF

wherein a race condition upon completion of a DTF custom action call would

cause a failure return to Windows Installer, even when the managed code

custom action itself returned success. That was fixed in 3.6, but the bug

remains in 3.5. The race condition is in the native wrapper code. It tends

to manifest only when there is a heavy load (either CPU or disk) in the

machine at the moment that the custom action is completing, and thus was

very difficult to reproduce (I was fortunate enough to have exactly one 
box

that reproduced it with any (but still uncertain) regularity, out of 
dozens

of other boxes that would never reproduce it).


You can take the SfxCA.dll files from recent builds of 3.6 and use them 
with

3.5's RTM build to get that race condition fix and an unrelated memory 
leak

fix. I don't remember the bug numbers, but I do remember the investigation

and fix of the race condition.


I don't know what would cause the QuietExec issue, however.


-Blair





--


Keep Your Developer Skills Current with LearnDevNow!


The most comprehensive online learning library for Microsoft developers is

just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, 
Metro

Style Apps, more. Free future releases when you subscribe now!


http://p.sf.net/sfu/learndevnow-d2d


___


WiX-users mailing list


WiX-users@lists.sourceforge.net


https://lists.sourceforge.net/lists/listinfo/wix-users





--

Keep Your Developer Skills Current with LearnDevNow!

The most comprehensive online learning

Re: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec

2012-01-25 Thread Blair
Except for that one repeatable machine, the problem always "went away" upon
retry (the same behavior you all have reported). That one machine was able
to repro more than once in a row, and after about four days I even got it to
repro in the debugger. That's when I finally discovered exactly what was
happening, and then I was able to stage a repro at will.

I submitted the fix to WiX, and a couple of weeks later walked another team
through their attempts to verify the fix.

Blair

-Original Message-
From: Christopher Painter [mailto:chr...@iswix.com] 
Sent: Wednesday, January 25, 2012 11:57 AM
To: Neil Sleightholm; General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec

I'm going to be creating a trojan installer that serves as a health check
and deploying it daily to 2200 machines.  I'll be able to stress test the
fix made in 3.6 and see what happen.s



From: "Neil Sleightholm" 

Sent: Wednesday, January 25, 2012 1:06 PM

To: "General discussion for Windows Installer XML toolset." 
, "chr...@iswix.com" 

Subject: RE: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec


As Chris said excellent information. Mine problem was with 3.5 and this ties
in with what I was seeing; on my VMs running on an i7 host I never saw the
problem but the tester often got it on his lower powered host. He need move
to a VM on an ESX host and the problem largely went away. I think I will try
the newer SfxCA.dll (or I might just go for 3.6).


Thanks


Neil


-Original Message-

From: Blair [mailto:os...@live.com] 

Sent: 25 January 2012 18:14

To: 'General discussion for Windows Installer XML toolset.';
chr...@iswix.com

Subject: Re: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec


Are these problems in 3.5 or 3.6? Last year I discovered a defect in DTF
wherein a race condition upon completion of a DTF custom action call would
cause a failure return to Windows Installer, even when the managed code
custom action itself returned success. That was fixed in 3.6, but the bug
remains in 3.5. The race condition is in the native wrapper code. It tends
to manifest only when there is a heavy load (either CPU or disk) in the
machine at the moment that the custom action is completing, and thus was
very difficult to reproduce (I was fortunate enough to have exactly one box
that reproduced it with any (but still uncertain) regularity, out of dozens
of other boxes that would never reproduce it).


You can take the SfxCA.dll files from recent builds of 3.6 and use them with
3.5's RTM build to get that race condition fix and an unrelated memory leak
fix. I don't remember the bug numbers, but I do remember the investigation
and fix of the race condition.


I don't know what would cause the QuietExec issue, however.


-Blair



--

Keep Your Developer Skills Current with LearnDevNow!

The most comprehensive online learning library for Microsoft developers is
just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro
Style Apps, more. Free future releases when you subscribe now!

http://p.sf.net/sfu/learndevnow-d2d

___

WiX-users mailing list

WiX-users@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/wix-users



--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers is
just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro
Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec

2012-01-25 Thread Christopher Painter
I'm going to be creating a trojan installer that serves as a health check 
and deploying it daily to 2200 machines.  I'll be able to stress test the 
fix made in 3.6 and see what happen.s



From: "Neil Sleightholm" 

Sent: Wednesday, January 25, 2012 1:06 PM

To: "General discussion for Windows Installer XML toolset." 
, "chr...@iswix.com" 

Subject: RE: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec


As Chris said excellent information. Mine problem was with 3.5 and this 
ties in with what I was seeing; on my VMs running on an i7 host I never saw 
the problem but the tester often got it on his lower powered host. He need 
move to a VM on an ESX host and the problem largely went away. I think I 
will try the newer SfxCA.dll (or I might just go for 3.6).


Thanks


Neil


-Original Message-

From: Blair [mailto:os...@live.com] 

Sent: 25 January 2012 18:14

To: 'General discussion for Windows Installer XML toolset.'; 
chr...@iswix.com

Subject: Re: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec


Are these problems in 3.5 or 3.6? Last year I discovered a defect in DTF 
wherein a race condition upon completion of a DTF custom action call would 
cause a failure return to Windows Installer, even when the managed code 
custom action itself returned success. That was fixed in 3.6, but the bug 
remains in 3.5. The race condition is in the native wrapper code. It tends 
to manifest only when there is a heavy load (either CPU or disk) in the 
machine at the moment that the custom action is completing, and thus was 
very difficult to reproduce (I was fortunate enough to have exactly one box 
that reproduced it with any (but still uncertain) regularity, out of dozens 
of other boxes that would never reproduce it).


You can take the SfxCA.dll files from recent builds of 3.6 and use them 
with 3.5's RTM build to get that race condition fix and an unrelated memory 
leak fix. I don't remember the bug numbers, but I do remember the 
investigation and fix of the race condition.


I don't know what would cause the QuietExec issue, however.


-Blair



--

Keep Your Developer Skills Current with LearnDevNow!

The most comprehensive online learning library for Microsoft developers is 
just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro 
Style Apps, more. Free future releases when you subscribe now!

http://p.sf.net/sfu/learndevnow-d2d

___

WiX-users mailing list

WiX-users@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/wix-users


--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec

2012-01-25 Thread Neil Sleightholm
As Chris said excellent information. Mine problem was with 3.5 and this ties in 
with what I was seeing; on my VMs running on an i7 host I never saw the problem 
but the tester often got it on his lower powered host. He need move to a VM on 
an ESX host and the problem largely went away. I think I will try the newer 
SfxCA.dll (or I might just go for 3.6).

Thanks

Neil

-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: 25 January 2012 18:14
To: 'General discussion for Windows Installer XML toolset.'; chr...@iswix.com
Subject: Re: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec

Are these problems in 3.5 or 3.6? Last year I discovered a defect in DTF 
wherein a race condition upon completion of a DTF custom action call would 
cause a failure return to Windows Installer, even when the managed code custom 
action itself returned success. That was fixed in 3.6, but the bug remains in 
3.5. The race condition is in the native wrapper code. It tends to manifest 
only when there is a heavy load (either CPU or disk) in the machine at the 
moment that the custom action is completing, and thus was very difficult to 
reproduce (I was fortunate enough to have exactly one box that reproduced it 
with any (but still uncertain) regularity, out of dozens of other boxes that 
would never reproduce it).

You can take the SfxCA.dll files from recent builds of 3.6 and use them with 
3.5's RTM build to get that race condition fix and an unrelated memory leak 
fix. I don't remember the bug numbers, but I do remember the investigation and 
fix of the race condition.

I don't know what would cause the QuietExec issue, however.

-Blair


--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers is just 
$99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style 
Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec

2012-01-25 Thread Christopher Painter
Blair,


 That is excellent information.  Yes, I am on 3.5 currently.  I'm no longer 
with Overwatch so I can make the call to go to 3.6 much easier.  


FWIW, in this install I have 1 immed. DTF CA that costs and then 2 more 
CA's that perform uninstall and install actions.   The cost CA always works 
and then the uninstall CA fails about .5% of the time based on 800+ 
machines deployed so far.  They are all Server 2008 R2 x64 SP1  Virtual 
Machines so maybe there's a problem there in CPU handling that exposes this 
race condition.


Only problem at this point is since the work around to 1603 is to run the 
advertisement again I can't rebuilt the package to see if 3.6 fixes it or 
not.



From: "Blair" 

Sent: Wednesday, January 25, 2012 12:14 PM

To: "General discussion for Windows Installer XML toolset." 
, chr...@iswix.com

Subject: RE: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec


Are these problems in 3.5 or 3.6? Last year I discovered a defect in DTF

wherein a race condition upon completion of a DTF custom action call would

cause a failure return to Windows Installer, even when the managed code

custom action itself returned success. That was fixed in 3.6, but the bug

remains in 3.5. The race condition is in the native wrapper code. It tends

to manifest only when there is a heavy load (either CPU or disk) in the

machine at the moment that the custom action is completing, and thus was

very difficult to reproduce (I was fortunate enough to have exactly one 
box

that reproduced it with any (but still uncertain) regularity, out of 
dozens

of other boxes that would never reproduce it).


You can take the SfxCA.dll files from recent builds of 3.6 and use them 
with

3.5's RTM build to get that race condition fix and an unrelated memory 
leak

fix. I don't remember the bug numbers, but I do remember the investigation

and fix of the race condition.


I don't know what would cause the QuietExec issue, however.


-Blair


--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec

2012-01-25 Thread Blair
Are these problems in 3.5 or 3.6? Last year I discovered a defect in DTF
wherein a race condition upon completion of a DTF custom action call would
cause a failure return to Windows Installer, even when the managed code
custom action itself returned success. That was fixed in 3.6, but the bug
remains in 3.5. The race condition is in the native wrapper code. It tends
to manifest only when there is a heavy load (either CPU or disk) in the
machine at the moment that the custom action is completing, and thus was
very difficult to reproduce (I was fortunate enough to have exactly one box
that reproduced it with any (but still uncertain) regularity, out of dozens
of other boxes that would never reproduce it).

You can take the SfxCA.dll files from recent builds of 3.6 and use them with
3.5's RTM build to get that race condition fix and an unrelated memory leak
fix. I don't remember the bug numbers, but I do remember the investigation
and fix of the race condition.

I don't know what would cause the QuietExec issue, however.

-Blair


--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec

2012-01-24 Thread Neil Sleightholm
This is my log:

MSI (s) (D8:E8) [10:34:00:250]: Doing action: ReadSqlBinPath
Action 10:34:00: ReadSqlBinPath.
Action start 10:34:00: ReadSqlBinPath.
MSI (s) (D8:E8) [10:34:00:343]: Creating MSIHANDLE (31) of type 790542 for 
thread 3048
MSI (s) (D8:B0) [10:34:00:421]: Invoking remote custom action. DLL: 
C:\WINDOWS\Installer\MSIE0.tmp, Entrypoint: ReadSqlBinPath
MSI (s) (D8!24) [10:34:01:031]: Creating MSIHANDLE (32) of type 790531 for 
thread 2084
SFXCA: Extracting custom action to temporary directory: 
C:\WINDOWS\Installer\MSIE0.tmp-\
MSI (s) (D8!24) [10:34:01:031]: Closing MSIHANDLE (32) of type 790531 for 
thread 2084
MSI (s) (D8!24) [10:34:01:078]: Creating MSIHANDLE (33) of type 790531 for 
thread 2084
SFXCA: Binding to CLR version v4.0.30319
MSI (s) (D8!24) [10:34:01:078]: Closing MSIHANDLE (33) of type 790531 for 
thread 2084
MSI (s) (D8!24) [10:34:01:281]: Creating MSIHANDLE (34) of type 790531 for 
thread 2084
Calling custom action 
Gendis.ProSync.CustomAction!zzz.zzz.CustomAction.SqlCustomActions.ReadSqlBinPath
MSI (s) (D8!24) [10:34:01:296]: Closing MSIHANDLE (34) of type 790531 for 
thread 2084
MSI (s) (D8!24) [10:34:01:328]: Creating MSIHANDLE (35) of type 790531 for 
thread 2084
ReadSqlBinPath: Begin
MSI (s) (D8!24) [10:34:01:328]: Closing MSIHANDLE (35) of type 790531 for 
thread 2084
MSI (s) (D8!24) [10:34:01:328]: PROPERTY CHANGE: Adding SqlBinPath property. 
Its value is 'c:\Program Files\Microsoft SQL Server\100\Tools\Binn\'.
MSI (s) (D8:B0) [10:34:01:343]: Closing MSIHANDLE (31) of type 790542 for 
thread 3048
Action ended 10:34:01: ReadSqlBinPath. Return value 3.

Slightly different I believe.

Neil

From: Christopher Painter [mailto:chr...@iswix.com]
Sent: 24 January 2012 19:41
To: Neil Sleightholm; General discussion for Windows Installer XML toolset.
Subject: RE: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec

Neil,

 I think you're spot on with what I'm seeing.  My static method entry point 
instantiates a class which then logs that it's been created and then nothing.  
Run it again and it's fine.  Here are some snippets from the log:

PS- FWIW, I plan on making a fake MSI that just does some infrastructure tests 
and run it regularly through SCCM across the enterprise to try to get some 
metrics.

-

// Setting up the CustomActionData during the costing action

MSI (s) (94!70) [00:00:12:479]: PROPERTY CHANGE: Adding 
UninstallPrinterDrivers.A2D45838_79FA_464A_AC38_8A203E43C3A4 property. Its 
value is '[]'.

..

// Script Generation Phase...

MSI (s) (94:18) [00:00:13:151]: Doing action: 
UninstallPrinterDrivers.A2D45838_79FA_464A_AC38_8A203E43C3A4
Action start 0:00:13: 
UninstallPrinterDrivers.A2D45838_79FA_464A_AC38_8A203E43C3A4.

.

// Script Execution Phase...

MSI (s) (94:18) [00:00:15:869]: Executing op: 
ActionStart(Name=UninstallPrinterDrivers.A2D45838_79FA_464A_AC38_8A203E43C3A4,,)
MSI (s) (94:18) [00:00:15:869]: Executing op: 
CustomActionSchedule(Action=UninstallPrinterDrivers.A2D45838_79FA_464A_AC38_8A203E43C3A4,ActionType=1025,Source=BinaryData,Target=UninstallPrinterDrivers,CustomActionData=[])
MSI (s) (94:38) [00:00:15:885]: Invoking remote custom action. DLL: 
C:\Windows\Installer\MSI981C.tmp, Entrypoint: UninstallPrinterDrivers
SFXCA: Extracting custom action to temporary directory: 
C:\Windows\Installer\MSI981C.tmp-\
SFXCA: Binding to CLR version v2.0.50727
Calling custom action 
PrinterDriverCA!PrinterDriverCA.RemovePrinterDrivers.UninstallPrinterDrivers
Class Constructed ( Logged from Base )
CustomAction UninstallPrinterDrivers.A2D45838_79FA_464A_AC38_8A203E43C3A4 
returned actual error code 1603 (note this may not be 100% accurate if 
translation happened inside sandbox)
MSI (s) (94:18) [00:00:16:494]: User policy value 'DisableRollback' is 0
MSI (s) (94:18) [00:00:16:494]: Machine policy value 'DisableRollback' is 0
Action ended 0:00:16: InstallFinalize. Return value 3


From: "Neil Sleightholm" mailto:n...@x2systems.com>>
Sent: Tuesday, January 24, 2012 11:38 AM
To: "chr...@iswix.com<mailto:chr...@iswix.com>" 
mailto:chr...@iswix.com>>, "General discussion for Windows 
Installer XML toolset." 
mailto:wix-users@lists.sourceforge.net>>
Subject: RE: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec

I can't help but I have seen something similar to 1 - my DTF action is an 
immediate action that just reads the registry and sets a property, 99% of the 
time it is fine. The tracing all indicates it is ok but on exit it returns 
"value 3", no logs, exception or anything useful - run again and it is fine. I 
started to think the problem was in DTF but I never got a good enough repro to 
debug it.

Neil

-Original Message-
From: Christopher Painter 
[mailto:chr...@iswix.com]<mailto:[mailto:chr...@iswix.com]>

Re: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec

2012-01-24 Thread Christopher Painter
I read through that and yes I see a similarity.  In my situation another 
ManagedCA  ( the part the does the costing and sets the CAD property ) ran 
successfully.   Then along comes the deferred CA and while it does start 
executing it mysteriously dies.


Very interesting.  And I'm sure Jason has long moved on.  Looks like it's 
time to get my ex-Microsoft developer down the row to help me out with some 
C++ debugging.



From: "jhennessey" 

Sent: Tuesday, January 24, 2012 1:47 PM

To: wix-users@lists.sourceforge.net

Subject: Re: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec


Although I wrote this bug up for a different reason ( 

https://sourceforge.net/tracker/?func=detail&aid=2013944&group_id=105970&ati
d=642714

https://sourceforge.net/tracker/?func=detail&aid=2013944&group_id=105970&ati
d=642714 

), if you read the comments you'll see that I was getting a similar issue. 
I

think I was only seeing the issue on Windows 2000 at the time though.

Nonetheless, you could try building sfxca.dll in debug mode and use it to

build your CAs to see if that helps.


--

View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Two-Wierd-Inst
aller-Problems-DTF-and-QuietExec-tp7220939p7221537.html

Sent from the wix-users mailing list archive at Nabble.com.



--

Keep Your Developer Skills Current with LearnDevNow!

The most comprehensive online learning library for Microsoft developers

is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,

Metro Style Apps, more. Free future releases when you subscribe now!

http://p.sf.net/sfu/learndevnow-d2d

___

WiX-users mailing list

WiX-users@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/wix-users


--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec

2012-01-24 Thread jhennessey
Although I wrote this bug up for a different reason ( 
https://sourceforge.net/tracker/?func=detail&aid=2013944&group_id=105970&atid=642714
https://sourceforge.net/tracker/?func=detail&aid=2013944&group_id=105970&atid=642714
 
), if you read the comments you'll see that I was getting a similar issue. I
think I was only seeing the issue on Windows 2000 at the time though.
Nonetheless, you could try building sfxca.dll in debug mode and use it to
build your CAs to see if that helps.

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Two-Wierd-Installer-Problems-DTF-and-QuietExec-tp7220939p7221537.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec

2012-01-24 Thread Christopher Painter
Neil,


 I think you're spot on with what I'm seeing.  My static method entry point 
instantiates a class which then logs that it's been created and then 
nothing.  Run it again and it's fine.  Here are some snippets from the 
log:


PS- FWIW, I plan on making a fake MSI that just does some infrastructure 
tests and run it regularly through SCCM across the enterprise to try to get 
some metrics.


-


// Setting up the CustomActionData during the costing action


MSI (s) (94!70) [00:00:12:479]: PROPERTY CHANGE: Adding 
UninstallPrinterDrivers.A2D45838_79FA_464A_AC38_8A203E43C3A4 property. Its 
value is '[]'.


..


// Script Generation Phase...


MSI (s) (94:18) [00:00:13:151]: Doing action: 
UninstallPrinterDrivers.A2D45838_79FA_464A_AC38_8A203E43C3A4

Action start 0:00:13: 
UninstallPrinterDrivers.A2D45838_79FA_464A_AC38_8A203E43C3A4.


.


// Script Execution Phase...


MSI (s) (94:18) [00:00:15:869]: Executing op: 
ActionStart(Name=UninstallPrinterDrivers.A2D45838_79FA_464A_AC38_8A203E43C3A
4,,)

MSI (s) (94:18) [00:00:15:869]: Executing op: 
CustomActionSchedule(Action=UninstallPrinterDrivers.A2D45838_79FA_464A_AC38_
8A203E43C3A4,ActionType=1025,Source=BinaryData,Target=UninstallPrinterDriver
s,CustomActionData=[])

MSI (s) (94:38) [00:00:15:885]: Invoking remote custom action. DLL: 
C:\Windows\Installer\MSI981C.tmp, Entrypoint: UninstallPrinterDrivers

SFXCA: Extracting custom action to temporary directory: 
C:\Windows\Installer\MSI981C.tmp-\

SFXCA: Binding to CLR version v2.0.50727

Calling custom action 
PrinterDriverCA!PrinterDriverCA.RemovePrinterDrivers.UninstallPrinterDrivers


Class Constructed ( Logged from Base )

CustomAction UninstallPrinterDrivers.A2D45838_79FA_464A_AC38_8A203E43C3A4 
returned actual error code 1603 (note this may not be 100% accurate if 
translation happened inside sandbox)

MSI (s) (94:18) [00:00:16:494]: User policy value 'DisableRollback' is 0

MSI (s) (94:18) [00:00:16:494]: Machine policy value 'DisableRollback' is 
0

Action ended 0:00:16: InstallFinalize. Return value 3



From: "Neil Sleightholm" 

Sent: Tuesday, January 24, 2012 11:38 AM

To: "chr...@iswix.com" , "General discussion for Windows 
Installer XML toolset." 

Subject: RE: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec


I can't help but I have seen something similar to 1 - my DTF action is an 
immediate action that just reads the registry and sets a property, 99% of 
the time it is fine. The tracing all indicates it is ok but on exit it 
returns "value 3", no logs, exception or anything useful - run again and it 
is fine. I started to think the problem was in DTF but I never got a good 
enough repro to debug it.


Neil


-Original Message-

From: Christopher Painter [mailto:chr...@iswix.com] 

Sent: 24 January 2012 16:35

To: wix-users@lists.sourceforge.net

Subject: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec


I have an installer that I wrote that I've been pushing out through SCCM. 

We have deployed to about 600 servers so far and so far I've seen 6 
failures. There are 3 of one failure mode and 3 of another.


1) C# DTF terminates with 1603


This one is wierd. It's a deferred CA that get's it's CustomActionData 

property and then does something for each record in the collection. 

There's actually no records in the collection so therefore nothing to do. 

I don't get any kind of .NET stack dump it just simply logs that it started 


and then poof the CA returns with a 1603. On the other 597 servers it 

works ( i.e. does nothing ) just fine. ( Trivia: it's really an uninstall 

custom action that can be instructed to remove something during an install 


I just haven't neeed to yet. ) If I run this install again on the same 

machine it works. 


2) I use a QuietExecCA64 to call dism to install a Windows feature. I see 

in the log that DISM added the feature and completed successfully but then 


that's the end of my MSI log. It's like either DISM didn't actually 

terminate of the C++ code didn't terminate and it hung MSI. SCCM then 

waited a period of time ( 20 minutes ) and decided that the MSI was 

orphaned and killed it followed by a reboot. 


All of these machines are Server 2008 R2 SP1.


Does anyone have any thoughts about this? I could redo #1 as a C++ CA and 

I could factor the DISM call out of the MSI and into the SCCM task sequence 


but I think at this point people are willing to take their changes since we 


are already 25% into the deployment. I'm wondering if there are any bugs 

in DTF and or the QuietExec patterns that need to be investigated.


--

Keep Your Developer Skills Current with LearnDe

Re: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec

2012-01-24 Thread Castro, Edwin G. (Hillsboro)
I have noticed a weird scenario similar to 1). In my case, I'm using the IIs 
custom actions in WiX 3.5. Sometimes the package fails with a 1603 error during 
WriteIIs7ConfigChanges. Rerunning the package succeeds. The error information I 
see in the log is always consistent and looks like this:

MSI (s) (04:48) [10:20:12:899]: Executing op: 
CustomActionSchedule(Action=WriteIIS7ConfigChanges,ActionType=11265,Source=BinaryData,Target=**,CustomActionData=**)
MSI (s) (04:30) [10:20:12:906]: Invoking remote custom action. DLL: 
C:\Windows\Installer\MSI259A.tmp, Entrypoint: WriteIIS7ConfigChanges
WriteIIS7ConfigChanges:  Error 0x80070103: Failed read webDir webkey
WriteIIS7ConfigChanges:  Error 0x80070103: Failed to configure IIS web svc ext.
WriteIIS7ConfigChanges:  Error 0x80070103: WriteIIS7ConfigChanges Failed.
CustomAction WriteIIS7ConfigChanges returned actual error code 1603 (note this 
may not be 100% accurate if translation happened inside sandbox)
Action ended 10:20:13: InstallFinalize. Return value 3.

I looked through the WiX code to try to identify what might generated the 
"Failed read webDir webkey" message and found a few locations. I think the 
error occurs when the custom action is trying to parse the data out of 
CustomActionData but when I try to follow the data back to its source (I 
struggled here...) it seemed to me that CustomActionData should not have had 
anything in it for that particular piece of code because the source table does 
not exist in my package.

I don't know whether this is a bug in the WiX IIs custom actions or something 
more sinister, like a Windows Installer API bug!

Edwin G. Castro
Software Developer - Staff
Digital Channels
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail


-Original Message-
From: Christopher Painter [mailto:chr...@iswix.com] 
Sent: Tuesday, January 24, 2012 8:35 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec

I have an installer that I wrote that I've been pushing out through SCCM.  
We have deployed to about 600 servers so far and so far I've seen 6 failures.  
There are 3 of one failure mode and 3 of another.


1) C# DTF terminates with 1603

   This one is wierd.  It's a deferred CA that get's it's CustomActionData 
property and then does something for each record in the collection.  
There's actually no records in the collection so therefore nothing to do.  
I don't get any kind of .NET stack dump it just simply logs that it started 
and then poof the CA returns with a 1603.  On the other 597 servers it 
works ( i.e. does nothing ) just fine.  ( Trivia: it's really an uninstall 
custom action  that can be instructed to remove something during an install 
I just haven't neeed to yet. )   If I run this install again on the same 
machine it works. 


2) I use a QuietExecCA64  to call dism to install a Windows feature.  I see 
in the log that DISM added the feature and completed successfully but then 
that's the end of my MSI log.  It's like either DISM didn't actually 
terminate of the C++ code didn't terminate and it hung MSI.   SCCM then 
waited a period of time ( 20 minutes ) and decided that the MSI was 
orphaned and killed it followed by a reboot.  


All of these machines are Server 2008 R2 SP1.


Does anyone have any thoughts about this?  I could redo #1 as a C++ CA and 
I could factor the DISM call out of the MSI and into the SCCM task sequence 
but I think at this point people are willing to take their changes since we 
are already 25% into the deployment.   I'm wondering if there are any bugs 
in DTF and or the QuietExec patterns that need to be investigated.
--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec

2012-01-24 Thread Neil Sleightholm
I can't help but I have seen something similar to 1 - my DTF action is an 
immediate action that just reads the registry and sets a property, 99% of the 
time it is fine. The tracing all indicates it is ok but on exit it returns 
"value 3", no logs, exception or anything useful - run again and it is fine. I 
started to think the problem was in DTF but I never got a good enough repro to 
debug it.

Neil

-Original Message-
From: Christopher Painter [mailto:chr...@iswix.com] 
Sent: 24 January 2012 16:35
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Two Wierd Installer Problems - DTF and QuietExec

I have an installer that I wrote that I've been pushing out through SCCM.  
We have deployed to about 600 servers so far and so far I've seen 6 failures.  
There are 3 of one failure mode and 3 of another.


1) C# DTF terminates with 1603

   This one is wierd.  It's a deferred CA that get's it's CustomActionData 
property and then does something for each record in the collection.  
There's actually no records in the collection so therefore nothing to do.  
I don't get any kind of .NET stack dump it just simply logs that it started 
and then poof the CA returns with a 1603.  On the other 597 servers it 
works ( i.e. does nothing ) just fine.  ( Trivia: it's really an uninstall 
custom action  that can be instructed to remove something during an install 
I just haven't neeed to yet. )   If I run this install again on the same 
machine it works. 


2) I use a QuietExecCA64  to call dism to install a Windows feature.  I see 
in the log that DISM added the feature and completed successfully but then 
that's the end of my MSI log.  It's like either DISM didn't actually 
terminate of the C++ code didn't terminate and it hung MSI.   SCCM then 
waited a period of time ( 20 minutes ) and decided that the MSI was 
orphaned and killed it followed by a reboot.  


All of these machines are Server 2008 R2 SP1.


Does anyone have any thoughts about this?  I could redo #1 as a C++ CA and 
I could factor the DISM call out of the MSI and into the SCCM task sequence 
but I think at this point people are willing to take their changes since we 
are already 25% into the deployment.   I'm wondering if there are any bugs 
in DTF and or the QuietExec patterns that need to be investigated.
--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Two Wierd Installer Problems - DTF and QuietExec

2012-01-24 Thread Christopher Painter
I have an installer that I wrote that I've been pushing out through SCCM.  
We have deployed to about 600 servers so far and so far I've seen 6 
failures.  There are 3 of one failure mode and 3 of another.


1) C# DTF terminates with 1603

   This one is wierd.  It's a deferred CA that get's it's CustomActionData 
property and then does something for each record in the collection.  
There's actually no records in the collection so therefore nothing to do.  
I don't get any kind of .NET stack dump it just simply logs that it started 
and then poof the CA returns with a 1603.  On the other 597 servers it 
works ( i.e. does nothing ) just fine.  ( Trivia: it's really an uninstall 
custom action  that can be instructed to remove something during an install 
I just haven't neeed to yet. )   If I run this install again on the same 
machine it works. 


2) I use a QuietExecCA64  to call dism to install a Windows feature.  I see 
in the log that DISM added the feature and completed successfully but then 
that's the end of my MSI log.  It's like either DISM didn't actually 
terminate of the C++ code didn't terminate and it hung MSI.   SCCM then 
waited a period of time ( 20 minutes ) and decided that the MSI was 
orphaned and killed it followed by a reboot.  


All of these machines are Server 2008 R2 SP1.


Does anyone have any thoughts about this?  I could redo #1 as a C++ CA and 
I could factor the DISM call out of the MSI and into the SCCM task sequence 
but I think at this point people are willing to take their changes since we 
are already 25% into the deployment.   I'm wondering if there are any bugs 
in DTF and or the QuietExec patterns that need to be investigated.
--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users