windows-services

I have a Windows Service that I install and upgrade with WiX, and this works great (it's very fast!). The only problem is that if I upgrade from, say, 1.0 to 1.1, both copies still have entries in the Add/Remove Programs list. So how can I make sure WiX removes its old/outdated entries in the Add/Remove Programs list when I perform an update? Create a major upgrade. For example, use the MajorUpgrade element in WiX v3.5. http://www.joyofsetup.com/2010/01/16/major-upgrades-now-easier-than-ever/ An addendum to this - if the RemoveFeatures attribute of MajorUpgrade is included, and names specific

I have tired to uninstall a disabled windows service through registry It is removed from registry but it is still showing in Services.msc with Description: Failed to read description error code 2 Intuition/How you got there - I am assuming you did either or both of these to land in this error message. a.Deleted the key manually from registry by HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and deleted the service from here) b.This service was in "automatic" start - so on deleting the service was somehow mislead in "starting automatically" - and hence produced this code Failed to read

Starting with a csharp-example and duly noting related SO questions ( Restart a windows services from C# and Cannot restart a Service ) and various other questions relating to restarting just one service , I'm wondering what the best method is for restarting a service with dependent services (e.g. Message Queuing , on which Message Queuing Triggers depends, or IIS , on which FTP Publishing and World Wide Web Publishing depend). The mmc snap-in does this automagically, but the code doesn't seem to provide the same functionality (at least not as easily). MSDN documentation for Stop says "If any

This question already has answers here : Closed 6 years ago . “A timeout was reached while waiting for the service to connect” error after rebooting (6 answers) My automatically starting windows service fails to start only on reboot. I have a windows service created in C# and installed via a Wix created installer. The service is set up to start automatically. The service is installed and run under the NT AUTHORITY\NETWORK SERVICE. When the service is started, it first makes an external web services call. In Windows 7 I can set the service to be Automatic - Delayed start and the service will

I have seen countless articles on how to use NSSM ( http://nssm.cc/ ) to start a NodeJS process. So, I have the following simple NodeJS file: var http = require('http'); http.createServer(function (req, res) { res.writeHead(200, { 'Content-Type': 'text/html' }); res.end('<p>Hello World</p>'); }).listen(8000); console.log('Server running on http://localhost:8000/'); I am using this command to install the NodeJS file as a windows service: "C:\Program Files\SimpleNode\nssm.exe" install SimpleNode "C:\Program Files\SimpleNode\node.exe" "C:\Program Files\SimpleNode\simple.js" The service is

This issue seems to be widely discussed, but I have problems with finding the solution in my particular case. My service is set up to be running under Local System account. On my first machine with Windows 7 SP1 (64-bit) installed, everything works as expected. But, just after I try to start the service on my second machine with Windows Server 2008 R2 SP1 (64-bit) , not even a second passes, and I'm facing this annoying error: Windows could not start the ProService service on Local Computer Error 1053: The service did not respond to the start or control request in a timely fashion The System