Process running on an account logged into console periodically becoming non responsive.
-
Hi, Sorry if this gets a little confusing. I have a application that runs on windows server 2003 that serves up files as a web server. It runs not as a windows service but as a process that minimizes to the task bar. To start the application I will connect to the server via RDP as console using a local admin account. I will start the application and minimize it and then disconnect the RDP session (without logging out). This leaves the application running under the local admin account and everything seems to work fine. The issue is periodically the web pages the application provides become unavailable (could happen once a month or 5 times a day, its comepletely random). I assume the application has crashed so I will rdp back to the server. As soon as I log in the application starts responding again for everyone. When I check the task bar it is running and still responding fine. Is this just the application being weird or is windows server somehow sleeping or timing this application out and when I relog it starts it up again? Any insight would be great, thanks for reading -Drew
-
Hi, Sorry if this gets a little confusing. I have a application that runs on windows server 2003 that serves up files as a web server. It runs not as a windows service but as a process that minimizes to the task bar. To start the application I will connect to the server via RDP as console using a local admin account. I will start the application and minimize it and then disconnect the RDP session (without logging out). This leaves the application running under the local admin account and everything seems to work fine. The issue is periodically the web pages the application provides become unavailable (could happen once a month or 5 times a day, its comepletely random). I assume the application has crashed so I will rdp back to the server. As soon as I log in the application starts responding again for everyone. When I check the task bar it is running and still responding fine. Is this just the application being weird or is windows server somehow sleeping or timing this application out and when I relog it starts it up again? Any insight would be great, thanks for reading -Drew
Is there a screensaver? If so, disable it. <Anecdote> I guy I knew (about ten years ago) said he had a similar problem with a client of his who kept setting the server's screensaver to Pipes with maximum everything and then complained when the printer wouldn't work -- the server was too busy drawing pipes! </Anecdote>