I think what you need is a deferred custom action scheduled in between StopServices and DeleteServices actions. This deferred custom action must call ChangeServiceConfig api (http://msdn.microsoft.com/en-us/library/ms681987(VS.85).aspx) to reset lpServiceStartName and lpPassword to LocalSystem account.
Suggestion to WIX team: maybe ServiceInstall/ServiceControl can be updated so that resetting of Account/Password to original values before uninstall? Alex -----Original Message----- From: Jordan McCulty [mailto:[EMAIL PROTECTED] Sent: Monday, October 13, 2008 10:06 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Access denied messages during minor upgrades related to service process Does anyone have any ideas for this problem? Would prompting for the account at install time necessarily solve this issue? On Wed, Sep 24, 2008 at 4:55 PM, Jordan McCulty <[EMAIL PROTECTED]>wrote: > I have a WiX MSI setup that installs a service process using ServiceInstall > and ServiceControl thusly: > > <ServiceInstall Id="ServiceId" Name="ServiceName" DisplayName="Display > Name" Description="Description" ErrorControl="normal" Start="auto" > Type="ownProcess" Vital="yes" Account="LocalSystem" /> > <ServiceControl Id="ServiceId" Name="ServiceName" Start="install" > Stop="both" Remove="uninstall" Wait="yes" /> > > This configuration works great, and I even have upgrades working > seamlessly, with one exception. Some of my customers choose to run the > service under a different user than LocalSystem (this choice is almost > always made after the fact, otherwise I could prompt during installation). > When this happens, the upgrade will fail with an access denied error > message. If the customer changes the service back to LocalSystem and tries > the upgrade again, it works fine. Has anyone else run into this? Is there > a way to workaround this issue? Ideally, the user under which the service > is currently running should be transparent to the installer. Since the user > is running the installation as administrator I wouldn't expect any > permission problems. > > I'm running an older 3.0 build of WiX (3.0.3829.0). I may be able to > upgrade to a more current version if necessary in order to solve the > problem. > > Thanks in advance. > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
