Update: I installed/uninstalled the product 100 times on a particular machine (using a script) and the problem with my custom action occurred just once out of those 100 attempts....
From: Michael Bednarek Sent: 02 March 2010 08:37 To: General discussion for Windows Installer XML toolset. Subject: .NET Custom Action fails intermittently on some machines Hi all, Our product fails to install (seemingly at random) once every so often. Once this failure occurs on a given machine, it is not usually possible to reproduce the problem again (re-installing the product will work fine). The machines on which the install fails are VMs which all come from the same base image (Windows 2008 R2 x64). The install always fails during one of our custom actions, which is written in .NET using DTF. The custom action (called "SetUserLanguage") is quite simple: it detects the .NET current culture and puts the two-letter language code of the culture (e.g. "en") into a property called "UserLanguage". According to the MSI logs, this code is running successfully - we see our own log statements appearing, and we see MSI report that the "UserLanguage" property has been set. However, an error seems to occur somewhere between the .NET code completing, and the MSI continuing with the next action. Here's the pertinent part of the MSI log: --- MSI (s) (6C:08) [08:29:01:854]: Doing action: SetUserLanguage MSI (s) (6C:08) [08:29:01:886]: Creating MSIHANDLE (33847) of type 790542 for thread 4616 MSI (s) (6C:38) [08:29:01:886]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI3B7B.tmp, Entrypoint: SetUserLanguage MSI (s) (6C!40) [08:29:02:276]: Creating MSIHANDLE (33848) of type 790531 for thread 4672 Action start 8:29:01: SetUserLanguage. MSI (s) (6C!40) [08:29:02:276]: Closing MSIHANDLE (33848) of type 790531 for thread 4672 MSI (s) (6C!40) [08:29:02:525]: Creating MSIHANDLE (33849) of type 790531 for thread 4672 SFXCA: Extracting custom action to temporary directory: C:\Windows\Installer\MSI3B7B.tmp-\ MSI (s) (6C!40) [08:29:02:525]: Closing MSIHANDLE (33849) of type 790531 for thread 4672 MSI (s) (6C!40) [08:29:02:806]: Creating MSIHANDLE (33850) of type 790531 for thread 4672 SFXCA: Binding to CLR version v2.0.50727 MSI (s) (6C!40) [08:29:02:822]: Closing MSIHANDLE (33850) of type 790531 for thread 4672 MSI (s) (6C!40) [08:29:02:993]: Creating MSIHANDLE (33851) of type 790531 for thread 4672 Calling custom action CustomActions!CustomActions.CustomActions.SetUserLanguage MSI (s) (6C!40) [08:29:02:993]: Closing MSIHANDLE (33851) of type 790531 for thread 4672 MSI (s) (6C!40) [08:29:02:993]: PROPERTY CHANGE: Adding UserLanguage property. Its value is 'en'. Detected culture as en-US and converted to language en MSI (s) (6C:38) [08:29:03:024]: Closing MSIHANDLE (33847) of type 790542 for thread 4616 CustomAction SetUserLanguage returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) Action ended 8:29:03: SetUserLanguage. Return value 3. Action ended 8:29:03: INSTALL. Return value 3. --- Does anyone have any ideas why our custom action (or DTF) might be failing, and how we could investigate further? Thanks! Mike Bednarek ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
