We've had this on a couple occasions. Basically, the scheduler via the application server tries to kick off the job and doesn't get an appropriate start reply back from the resource in the set amount of time (basically times out). It will try 10 times (default) before it gives up. You can change this default but you are best to figure out why the resource isn't reacting quickly enough, with the most probable answer being network latency.
Essentially Denis was simply saying that drag&drop in control room cannot be compared to scheduling via app server, and the fact that you can use local to d&d a process on a resource simply means that your local is connected to the resource (which is via the app server btw).
The app server will expect a much different response time in the d&d scenario than the scheduling one. Do you ever notice, when you d&d a process onto a resource, the job doesn't show up in the bottom pane for several seconds? Then when you start it, it takes yet another few seconds before the status of the job changes from pending to running? In scheduling mode, the server doesn't have the same ""patience"".
There isn't any easy ""how to detect and correct network issues"" reply. So many factors are in play. Things you need to consider, among hundreds of others ...
Are you having issues with only this one process, or are all processes that you are trying to schedule on this resource having same this issue?
Are any of your other resources experiencing this issue or just one specific resource?
Does the resource go to sleep and take time to wake up if idle for too long?
Are your app server and your resource co-located, as in, are they in the same building on the same network?
Is the pipe which they communicate dedicated or shared with other network/internet traffic? Is this process scheduled during peak bandwidth usage times on your network?
Are other processes running at the same time which have logging enabled? Logging is a major tax on the server and should really be set to errors only for all processes unless you are trying to debug an issue. Try clicking on view log on a process that has run with logging enabled and you will notice right away the system struggling.
