Config: Windows Server 2016, x64, 1GB of RAM. Created a service according to the manual. Placing ASP.NET Core in the Windows service installed on the house. pc, everything was fine and worked. I produce everything in the same way, I install the service on the server, but I cannot start it; the error 1053 cannot be started. What could be the problem?

UPD

Here is what 2 errors in EventLog

1- A timeout was reached (30000 milliseconds) while service was connect to myService.

2).

  • one
    And in the event log then what he writes? - AK ♦
  • @AK added description, but there is nothing useful - Unnamed:
  • Security Question. Do you hope to launch any heavy operations on the service initialization? The timeout can be caused by this. I can also try to recommend to build a new empty application and gradually add to it more real features of the application - and watch when it stops running. - AK ♦
  • The @AK standard start-up application of the ASP.NET CORE API is generally empty, purely outputting two values ​​for verification. And at the start, even 30 seconds the service does not go down - Unnamed:
  • (in the assumption, not sure, but suddenly?) What is the version of the framework? On the developer's machine, it’s probably installed with the studio, but is there such a version on the server? What writes dotnet -info . Well, just run it once on the server, not as a service, but as a console application, removing RunAsService. - AK ♦

0