I'm not sure if it is applicable in your case, but I seem to remember that when debugging both our service and our installer for it that if you crash the OnStart method or the constructor you'll also get error 1923. So it might be useful to "instrument" your service too and see if you can figure out if it gets to anywhere useful. (We are using a managed service, so it might be different if you are not.)
Keith Douglas Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6 keith.doug...@statcan.gc.ca Telephone | Téléphone 613-854-5589 Facsimile | Télécopieur 613-951-4674 Government of Canada | Gouvernement du Canada -----Original Message----- From: Gábor Zoltán Tamás [mailto:tamas.gabor.zol...@gmail.com] Sent: August-05-14 5:11 AM To: wix-users@lists.sourceforge.net Subject: [Released Spam | pourriel affranchi] [WiX-users] Debugging installer Hi all, We have a solution with a WIX installer project that should install a Windows service and start it right away. Now the issue is that the WIX project outputs MSIs that sometimes fail on some, but not all of our environments. After enabling verbose logging and looking at the log files msiexec.exe, we can see, that each time the installation fails after aquiring the 32 bit elevated custom action server, right when the installer tries the following: Executing op: ServiceInstall(Name=___,DisplayName=_____,ImagePath=_____,ServiceType=16,StartType=2,ErrorControl=32768,,Dependencies=[~],,StartName=NT AUTHORITY\SYSTEM,Password=**********,Description=_____,,) The following log entry is: Error 1923. Service '_____' (___) could not be installed. Verify that you have sufficient privileges to install system services. The privileges - of course - are not the issue. Comparing logs of failed and successful installs reveal no relevant difference up until the point when the ServiceInstall custom action fails. All differences are timestamps, random character sequences (GUIDS, temporary file names, etc) or PIDs. We are completely puzzled why one MSI fails and the next one does not (no code changes at all, the files seem to be of the same size). Can someone here give us advice what the best course of action would be that would let us closer to the underlying issue? Is there any way to debug the ServiceInstall action? Thank you, Gabor ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
