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
