A repair is basically a reinstall, and it can't do that unless you can arrange 
to supply those credentials again. They're not remembered on your behalf.  

Phil Wilson 
949-639-1680 

-----Original Message-----
From: Sameer Arora [mailto:[email protected]] 
Sent: Thursday, July 07, 2011 9:49 AM
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users


*** Confidentiality Notice: This e-mail, including any associated or attached 
files, is intended solely for the individual or entity to which it is 
addressed. This e-mail is confidential and may well also be legally privileged. 
If you have received it in error, you are on notice of its status. Please 
notify the sender immediately by reply e-mail and then delete this message from 
your system. Please do not copy it or use it for any purposes, or disclose its 
contents to any other person. This email comes from a division of the Invensys 
Group, owned by Invensys plc, which is a company registered in England and 
Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 
7AW (Registered number 166023). For a list of European legal entities within 
the Invensys Group, please go to 
http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77.

You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail 
[email protected]. This e-mail and any attachments thereto may be subject 
to the terms of any agreements between Invensys (and/or its subsidiaries and 
affiliates) and the recipient (and/or its subsidiaries and affiliates).



------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to