One day someone should implement a @Persist on the property element, it could even have ="yes" or ="encrypted".
-----Original Message----- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: 08 July 2011 09:59 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Windows Service Repair failing on lack ofpermissions + how to detecting repair mode ? As you guessed, if you don't store and retrieve property values during installation, they will be set to defaults during maintenance. The repair probably fails because it's trying to log on the service using the defaults. You'll need to save the values entered by the user. http://robmensching.com/blog/posts/2010/5/2/The-WiX-toolsets-Remember-Propert y-pattern -----Original Message----- From: Sameer Arora [mailto:arora...@gmail.com] Sent: 07 July 2011 17:49 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Windows Service Repair failing on lack of permissions + how to detecting repair mode ? Hello, Our WIX setup installs a windows service after asking logon account through a custom UI dialog.. The service starts after installation succeeds. Entire setup requires elevated privileges. Hoping for any pointers regarding couple of questions: *Question 1* On attempting "Repair" from "Add/Remove Programs", UAC prompts for privilege elevation. After allowing so, the repair still fails with message: "Service <service name> could not be installed. Verify that you have sufficient privileges to install system services". Here's excerpt from code: <Product Id="$(var.productCode)" Codepage="1252" Language="1033" Manufacturer="Microsoft" Name="$(var.productReleaseName)" UpgradeCode="$(var.upgradeCode)" Version="$(var.productVersion)"> ... <Condition Message="$(var.adminPrivilegesRequired)">Privileged</Condition> ... <Component Id="C_ServiceEXE" Guid="{105F9C86-BF07-43C8-8C78-DF30F012CD68}"> <File Id="$(var.TargetFileName)" Name="$(var.TargetFileName)" KeyPath="yes" Assembly=".net" AssemblyManifest="$(var.TargetFileName)" AssemblyApplication="$(var.TargetFileName)" DiskId="1" Source="$(var.TargetDir)\$(var.TargetFileName)" /> <Condition>Privileged</Condition> <ServiceInstall Id="Id_ServiceInstall" Name ="$(var.ServiceName)" Description="$(var.ServiceDescription)" DisplayName="$(var.ServiceName)" Account="[SERVICEACCOUNT]" Password="[SERVICEPASSWORD]" Start="auto" ErrorControl="normal" Type="ownProcess" Vital="yes" Interactive="no" /> <ServiceControl Id="Id_ServiceControl" Name ="$(var.ServiceName)" Remove="uninstall" Start="install" Stop="both" Wait="yes" /> </Component> ... </Product> I not quite sure why this is happening, since I admin am on on my Win7 dev box and have marked both the setup and speicifically the service install component to be run in privileged mode. I suspect I might be missing scheduling repair inside an AdminInstallExecute sequence but not quite sure if that will fix this. *Question 2* Also, related question is - if repair does succeed, would it again require user to enter logon account via the UI. I'd rather suppress all interactive UIs during repair or upgrade. I realize that UPGRADINGPRODUCTCODE to detect upgrade.* * * * But how is repair detected ? Appreciate any help or pointers. Sameer ----------------------------------------------------------------------------- - All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. ----------------------------------------------------------------------------- - All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
