If I create a service with sc, it works. I can go in the Services interface and start it, and it will work. If I create the service from ASP.NET, from the Services interfaces, I cannot start it. When I compare what sc created and what the same command created from the Web site, all the parameters are the same. So, visually, the EXE path and the log on privilege are the same. But, if it was created from the Web site, when clicking on Start, I get: "The service did not start due to a logon failure."

As I said, no matter the method to create the service, when I check what was created, it is exactly the same. I double checked several times. So, my guess is that I assume there is something that I do not see in the background of a creation of a service which differs from the approach I take in creating them. And, this seems to have an impact here.

Anyone can confirm that there are non visible settings related to a service which might explain all this?