stephnane1
Technical User
Hello.
We have a strange problem :
A scheduled script (every 5 minutes) has this instruction :
"C:\WINDOWS\system32\cmd.exe" /c c:\batchs\MyTest.cmd
This script is launched by a workload manager but they are stucked with this problem. The Workload Manager take the process ID launched by "C:\WINDOWS\system32\cmd.exe".
It seems that the process is created, but windows say that the job completed successfully. In fact, the script has never been launched (we check this by writing a log in the first line of this script).
This problem doesn't happen every time, I would say 1 time / 2 ou 1 time / 3.
Exemple :
Is there any limitation with launching script/processes which could explain this behaviour ?
Any idées to check (windows side) what's happen ?
Thank you
We have a strange problem :
A scheduled script (every 5 minutes) has this instruction :
"C:\WINDOWS\system32\cmd.exe" /c c:\batchs\MyTest.cmd
This script is launched by a workload manager but they are stucked with this problem. The Workload Manager take the process ID launched by "C:\WINDOWS\system32\cmd.exe".
It seems that the process is created, but windows say that the job completed successfully. In fact, the script has never been launched (we check this by writing a log in the first line of this script).
This problem doesn't happen every time, I would say 1 time / 2 ou 1 time / 3.
Exemple :
Code:
Process created with pid: 9772
Job completed successfully. Exit code 0Is there any limitation with launching script/processes which could explain this behaviour ?
Any idées to check (windows side) what's happen ?
Thank you