Hey thanks for this information!

Here is the sdshow result for the service i.e. if I am reading it right 
localsystem, built-in admins, interactive users, service logon user has 
permissions on it, right? Don't see the SID trusted installer (please correct 
me if I am missing anything here). 

D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;IU)(A;;CCLCSWLOCRRC;;;SU)S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)

Thanks,
Sandip

-----Original Message-----
From: Heath Stewart 
Sent: Tuesday, June 11, 2013 2:42 PM
To: Sandip Shahane; General discussion for Windows Installer XML toolset.
Cc: Marc Reyhner; Doug Bradley; Vitaly Voloshin
Subject: RE: [WiX-users] Error 1923 - Service fails to install during upgrade

Run: sc sdshow HealthService

If SID S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464 owns the 
service, it can only be updated by TrustedInstaller (Windows update system).

Heath Stewart
VS Pro Deployment Experience, Microsoft
http://blogs.msdn.com/heaths

-----Original Message-----
From: Sandip Shahane 
Sent: Monday, June 10, 2013 1:55 PM
To: General discussion for Windows Installer XML toolset.
Cc: Marc Reyhner; Doug Bradley; Vitaly Voloshin; Heath Stewart
Subject: RE: [WiX-users] Error 1923 - Service fails to install during upgrade

That's what I also suspected earlier but cannot point finger to any such 
errors. StopServices action doesn't give any indication of failure. We are 
noticing this issue sometimes even when the service is stopped manually before 
running upgrade. Is there anything particular in the setup log that could tell 
if the service was marked for deletion and disabled while uninstalling?

I have also copied Heath who thinks it could be related to the MSI not able to 
write to TrustedInstaller resources. Heath, is there a way to identify if this 
indeed is the case?

Thanks,
Sandip

-----Original Message-----
From: Phil Wilson [mailto:phil.wil...@mvps.org] 
Sent: Friday, June 07, 2013 8:47 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Error 1923 - Service fails to install during upgrade

What does the StopServices action say about stopping the failing service?
There may be something useful there. 

If you have any code in your apps that starts, stops, reconfigures these 
services, then take a close look at it. One of the reasons for this issue is 
that somebody had a handle open to the service when it was being uninstalled, 
so it gets marked for deletion and disabled. Windows can't install it when it's 
in that state. I think the MMC services snapin had that bug for a while, and if 
it's still there them monitoring the situation using that snapin is probably 
making it worse ;) 

I'd expect an authoring issue to affect all the services, and be more 
consistent across machines.

Phil  

-----Original Message-----
From: Sandip Shahane [mailto:sandi...@microsoft.com]
Sent: Thursday, June 06, 2013 2:46 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Error 1923 - Service fails to install during upgrade

Hi WIX experts,
We are noticing error 1923 as below during upgrade of our product. The repro is 
not consistent but hitting it with very high frequency. So far, we are seeing 
it happening on both Win2012 and Win2012 R2 machines. The service installs fine 
during fresh and repair installation, but fails only during upgrade.

The MSI package runs as per-machine and user running upgrade is an 
administrator on the machine. I don't find any apparent errors about service 
install failure in the event log, so no clue what the problem is.

Heath Stewart mentioned on another forum that this looks to be to do with MSI 
not able to write to TrustedInstaller resources and is a WIX authoring issue. 
Could you kindly let me know what the issue with WIX authoring it is and how to 
fix it? Is this a known issue or if a bug needs to be opened for this issue for 
this issue? I am using WIX 3.7 and below is the WIX code snippet.

Log snippets:
MSI (s) (F0:20) [04:25:45:682]: MSI_LUA: Credential prompt not required, user 
is an admin

MSI (s) (F0:20) [04:26:09:073]: Executing op:
ProgressTotal(Total=3,Type=1,ByteEquivalent=1300000)
MSI (s) (F0:20) [04:26:09:073]: Executing op:
ServiceInstall(Name=HealthService,DisplayName=@C:\Program Files\Monitoring 
Agent\Agent\HealthService.dll,-10500,ImagePath="C:\Program Files\Monitoring 
Agent\Agent\HealthService.exe",ServiceType=32,StartType=2,ErrorControl=0,,De
pendencies=rpcss[~][~][~],,,Password=**********,Description=@C:\Program
Files\Monitoring Agent\Agent\HealthService.dll,-10501,,)
MSI (s) (F0:20) [04:26:09:088]: Executing op:
ServiceInstall(Name=AdtAgent,DisplayName=@C:\Windows\system32\AdtAgent.exe,-
500,ImagePath=C:\Windows\system32\AdtAgent.exe,ServiceType=16,StartType=4,Er
rorControl=1,,Dependencies=eventlog[~]dnscache[~][~][~],,StartName=NT
AUTHORITY\NetworkService,Password=**********,Description=@C:\Windows\system3
2\AdtAgent.exe,-501,,)
Information 1923.Service '@C:\Program Files\Monitoring 
Agent\Agent\HealthService.dll,-10500' (HealthService) could not be installed. 
Verify that you have sufficient privileges to install system services.
MSI (s) (F0:20) [04:26:09:088]: Executing op: ServiceInstall(Name=System Center 
Management APM,DisplayName=@C:\Program Files\Monitoring 
Agent\Agent\APMDOTNETAgent\InterceptSvc.exe,-100,ImagePath="C:\Program
Files\Monitoring
Agent\Agent\APMDOTNETAgent\InterceptSvc.exe",ServiceType=16,StartType=4,Erro
rControl=1,,Dependencies=RPCSS[~][~][~],,StartName=LocalSystem,Password=****
******,Description=@C:\Program Files\Monitoring
Agent\Agent\APMDOTNETAgent\InterceptSvc.exe,-501,,)
...
...
...
Property(N): AdminUser = 1
Property(N): MsiTrueAdminUser = 1

ServiceInstall and ServiceControl entries in WIX source for this service looks 
like below:

          <ServiceInstall
       Id="MOMHealthServiceInstall"
              Name="HealthService"
       DisplayName="[HEALTH_SERVICE_DISPLAY_NAME]"
              Type="shareProcess"
Start="auto"
ErrorControl="ignore"
Description="[HEALTH_SERVICE_DESCRIPTION]">
         <ServiceDependency Id="rpcss" />
          </ServiceInstall>
          <ServiceControl Id="HealthServiceRemoveUninstall"
Name="HealthService" Remove="uninstall" Wait="yes" />
          <ServiceControl Id="HealthServiceStopBoth" Name="HealthService"
Stop="both" Wait="yes" />

Thanks,
Sandip
----------------------------------------------------------------------------
--
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations 2.
Dashboards that offer high-level views of enterprise services 3. A single 
system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations 2. 
Dashboards that offer high-level views of enterprise services 3. A single 
system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to