Timers in ITScriptNet are handled asynchronously, which means that a timer can fire while an OMNI connection attempt is in progress. If the timer handler also makes a communications attempt, the second attempt will be made on the already established connection. The OMNI server will reject the second attempt, resulting in an error message on the terminal.

To prevent this problem, you should disable any timers before making an OMNI connection attempt, and re-enable them afterward. This will prevent the timer from expiring while the first attempt is in progress.