Application process turns into background process on "Shutdown"

[RyuKyu567]

Here is an interesting little one which may be just the way the operating system works but figured I would ask the question anyway. For testing purposes I started a test server to fiddle around with a few server tools and modifications and I realized that during the shutdown process the dedicated server would convert itself to a background process which will require manually killing the task. I have no idea how to prevent this or what the cause even is. Current OS the test dedicated server is on is Windows Server 2012 R2. The public server is on Windows 10 which when needed to shut down it does what its told. Again, I am uncertain if this is an OS thing or if there is a custom startup/shutdown script that may need to be implemented. I have included screen shots to paint a better picture.

For additional information, when conducting a restart of the server the same issue occurs which is the primary problem. When the application gets placed into a "background" service it is unable to complete the restart task. Any ideas would be greatly appreciated!

Thanks!

 

[Trekkan]

There isn't anything that should/would change that as far as I'm aware. The best way to stop the server is to make sure the Telnet connection is working. As the normal way your server shuts down is that the "shutdown" command is issued and the server does a clean shutdown. Depending on server usage, uptime, etc... this can sometimes take a minute or two, but... shouldn't be long at all normally (20ish seconds is kind of normal). So... Sorry I don't have any good answers, but I can confirm that what you are seeing, isn't normal.

 

[RyuKyu567]

There isn't anything that should/would change that as far as I'm aware. The best way to stop the server is to make sure the Telnet connection is working. As the normal way your server shuts down is that the "shutdown" command is issued and the server does a clean shutdown. Depending on server usage, uptime, etc... this can sometimes take a minute or two, but... shouldn't be long at all normally (20ish seconds is kind of normal). So... Sorry I don't have any good answers, but I can confirm that what you are seeing, isn't normal.

Thanks for the reply Trekkan, I figured that something wasn't quite right and this is at no fault of RAT 4. I've just never seen it do that before which I gotta tell ya, makes the scheduled restarts a bit of a pain lol. I have a few alternatives but wanted to see if anyone has encountered this. I do appreciate it!