In the last post I showed how to use sc.exe to add a dependency to a Windows service; the first time I added the dependency to the eOne and eConnect services, I got the service name wrong. This was because the server I was working on had a SQL Server Named instance rather than the default name.
I had to do some searching around how to remove the incorrect dependency, as it was preventing…
