At least once a week I have to reboot my Windows server running the remote loader. This is because the remote loader instances sometimes do not always close properly. If I attempt to restart the instance, I get the application screen, the server's CPU utlization increases dramatically as remote loader uses most of it, and the remote loader instance screen.

Is there a resolution for this? I can't even kill the process and it doesn't shop up in tcpview, yet obviously the communication or local port(s) is in use.

In the trace log I see:
Message = Error initializing command connection: socket error: permission denied

repeated over and over unit I reboot the server.

Suggestions?

Tom