Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Installer can fail to install service if the system hasn't completely removed it yet #2869

Closed
nvaccessAuto opened this issue Dec 14, 2012 · 1 comment
Closed

Installer can fail to install service if the system hasn't completely removed it yet #2869

nvaccessAuto opened this issue Dec 14, 2012 · 1 comment
Labels
bug close/cantfix component/installer
Milestone
2013.1

Comments

@nvaccessAuto
Copy link

Reported by jteh on 2012-12-14 04:25
From a private email:

If you are interested I tried the update dialog that appeared today and the install failed with the following in the log file:

ERROR - RPC process 3384 (nvda_slave.exe) (21:04:34):
nvda_slave.main:
slave error
Traceback (most recent call last):
  File "nvda_slave.pyw", line 27, in main
  File "installer.pyo", line 341, in install
  File "installer.pyo", line 151, in registerInstallation
  File "nvda_service.pyo", line 330, in installService
  File "win32serviceutil.pyo", line 170, in InstallService
error: (1072, 'CreateService', 'The specified service has been marked for deletion.')
ERROR - gui.installerGui.doInstall (21:04:34):
Installation failed: 1

This suggests that !RemoveService doesn't completely remove the service, but only marks it for deletion and it is cleaned up later. The question is when it is cleaned up and how we wait for it to be cleaned up.

Marking as minor initially because I've never heard of this happening before, but it should be investigated nevertheless.
@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2013-02-04 16:34
According to multiple sources, this can happen if services.msc is running, in which case there's nothing we can do about it. There could be other reasons, but this is the only concrete reason I can find and I suspect the reporter won't remember specific details. Therefore, I'm closing as cantfix. This should be reopened if this issue can definitely be reproduced without services.msc and/or mmc.exe running.

References:

@nvaccessAuto nvaccessAuto added this to the 2013.1 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug close/cantfix component/installer
Projects
None yet
Milestone
2013.1
Development

No branches or pull requests
1 participant
@nvaccessAuto