<div>
<div class="content wysiwyg-content">
Hello All.<br />
<br />
A few months back I created a user-defined service on a Windows 2k3 server to run an old serial file transfer application called Phoenix Link. This file communicates with a piece of machinery on the production floor via a wireless ethernet to serial RS-232 adapter. Normally the system works well until a day or two in when the server stops answering requests from the machine (when attempting to download a file from the server to the machine). During this failed state I have confirmed that the wireless link is still functioning and the machine's serial connection to the adapter is running. A restart of the service will cure the problem, so I'm fairly certain the problem is limited to the service. I am monitoring the service via a WMI probe in PRTG Network Monitor which interstingly shows the service as still responding although there is in fact a problem. Any suggestions on how to prevent this service from going non-responsive, or as a band-aid, how to have the service restart automatically after a given period?
</div>
</div>


Hello All.

A few months back I created a user-defined service on a Windows 2k3 server to run an old serial file transfer application called Phoenix Link. This file communicates with a piece of machinery on the production floor via a wireless ethernet to serial RS-232 adapter. Normally the system works well until a day or two in when the server stops answering requests from the machine (when attempting to download a file from the server to the machine). During this failed state I have confirmed that the wireless link is still functioning and the machine's serial connection to the adapter is running. A restart of the service will cure the problem, so I'm fairly certain the problem is limited to the service. I am monitoring the service via a WMI probe in PRTG Network Monitor which interstingly shows the service as still responding although there is in fact a problem. Any suggestions on how to prevent this service from going non-responsive, or as a band-aid, how to have the service restart automatically after a given period?

User Defined Service stops responding after some time

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Microsoft server applications are those applications developed specifically, but not necessarily exclusively, on the Windows Server platform. In addition to well-known products like SQL Server, Exchange, Internet Information Services (IIS), Microsoft Dynamics, Forefront, Lync and Sharepoint, they include applications like Skype, BizTalk, Hyper-V, Groove and Commerce Server. Server applications are managed with the Microsoft System Center.