Skip to main content
P
ptc-51739971-Visitor
1-Visitor
July 10, 2013
Solved

Windows Task Scheduler

  • July 10, 2013
  • 1 reply
  • 2435 views

I am using windows 2008 Server to schedule some tasks to run on a certain time. Installed on this Server I have Integrity client 2009/SP6.

I have a smal batch si commands which can not be excuted from the windows scheduler. Any othe CMD Batchfiles are working just fine. MKS Batch files are not. I have tried many settings, nothing worked. Do anyboday have an idea?

      Best answer by dhegland

      The hanging symptom in batch jobs is indeed very tricky! It's caused by the fact that the Integrity client stays running unless you proactively shut it down. A subsequent instance of the batch job may be unable to connect to a client started by a prior instance. To prevent this kind of thing, you need to design your batch jobs to begin with "si.exe connect" and end with "si.exe exit --shutdown". I have done so and found it to work very well.

      1 reply

      D
      dhegland1-Visitor
      1-Visitor
      July 10, 2013

      I've done lots of successful scripting with 2009sp6. I am very sure that it works and works well. Perhaps you could elaborate on what command you are running and what error you are seeing.

      P
      ptc-51739971-VisitorAuthor
      1-Visitor
      July 10, 2013

      I `ve found the reason, when the integrity run`s in the background it hangs some times I do not know why

      The secound time the client want`s to start it crasches cause of the existing client in the background. Know it works fine.

      D
      dhegland1-VisitorAnswer
      1-Visitor
      July 10, 2013

      The hanging symptom in batch jobs is indeed very tricky! It's caused by the fact that the Integrity client stays running unless you proactively shut it down. A subsequent instance of the batch job may be unable to connect to a client started by a prior instance. To prevent this kind of thing, you need to design your batch jobs to begin with "si.exe connect" and end with "si.exe exit --shutdown". I have done so and found it to work very well.

        Terms & ConditionsAccessibility statement