Symptoms

When you run a script using a Script Task, adTempus may abort the script and log a message that it has exceeded its allowed runtime, even if you have set the time limit for the script to "0," which is documented to mean "no limit."

Cause

A time limit of "0" is interpreted by the Windows scripting host to mean "no time limit unless the script appears to be hung." This is intended to prevent "runaway" scripts (such as scripts with programming errors that lead to infinite loops or other issues). In some cases other operations (such as the creation of ActiveX objects) cause the scripting host to think that the script is misbehaving, and the host aborts the script when it shouldn't.

Resolution

Set the time limit to "-1". This tells the scripting host to allow the script to run as long as it wants, regardless of how it behaves.