Is logged to the trace file or it is not created when the service attempts to start, no TSM code is being run yet and the issue is outside of the TSM code.Ħ.
Try getting service trace when scheduler starts, if nothing If no PID is available then it should not be running and TSM code would not be executed yet, so it would be a windows issue to at least find out what is happening up to the point of execution. Try using the dsmtrace utility, dsmtrace query pid, to get the PID.ĥ. If they are running kill them and see if this allow the "starting" status to goĪway, even if a restart fails again, this should make it easier to get troubleshooting info if it works.Ĥ. The scheduler should be dsmsvc but look for others. Check again for any PID, try using tasklist or sc queryex to find any TSM/dsm processes running on the system. If you cannot get a client trace then this is likely the case.ģ. If its not yet in starting as it looks to be pre-starting status, it may not be running TSM code yet and likely something else on the system or in windows is preventing it from running. If the service is stopping for reasons other than someone stopping it or the CAD, look into why this is happening and what else may be going on with the system when you see this occur (look for a trend).Ģ. Do you know why the service is stopped in the first place? Is there something that is stopping it or is it stopped because of the CAD and cannot restart when needed?
0 kommentar(er)
