Hi, my Question is - Does the NetTalk Errortrap reset the timer to zero? If so, this might stop timer events in my service.
- Subsequent found ErrorTrap - after parent, if an abort is issued (or indeed if it is not issued) then post event:CloseWindow - leaves the window open. Is there some other interrupt required after the Event:Closewindow to give control to the window so it may close?
Situation
A SOAP client service that has been running 24/7 has begun trapping an open timeout error
"Errorcode:-53 - The requested connection could not be opened. The Open command timed out or failed to connect NetSimple.TakeEvent" which then seems to prevent timer events.
The basic logic in Main (Service with Winevent) is
Session=No
Set timer to 10 secs
In Timer Event
If session = No - - set session = yes - Call Session - set session to no
else ignore timer event.
end
Session Procedure using Nettalk Web Client
Open URL - Async
net.AsyncOpenUse = 1 ! Use AsyncOpen 12 seconds (recommended)
net.AsyncOpenTimeOut = 1200 ! Up to 12 seconds to connect
net.InActiveTimeout = 6000 ! Set IdleTimeout 60 seconds
Check for Post error - NONE
PageReceived - does necessary stuff
ErrorTrap Proc
SaveErr = net.error()
Log error - logs OK
Call Proc to Email error using Nettalk Email - never turns up
ErrorTrap.Parent
If SaveError =53 - Open timeout
self.abort
end
Post Event:CloseWindow
-------
Window remains open.
Thanks