Great addition Chris. Some time back I found the support note that suggested stopping the various servers, copying the SAS.EXEs to new names and restarting so you could see which of N SAS executables was doing what.

Sadly it still hasn't helped me resolve the occasional appearance of a SAS exe which draws up to 100% CPU and has to be killed of the task manager.

Good advice, I think this might give me a running start for finding the errant task.

Kind regards

David