Ghost21 Posted August 20, 2009 Posted August 20, 2009 --> IE.au3 V2.4-0 Warning from function _IEFormGetObjByName, $_IEStatus_NoMatch --> IE.au3 V2.4-0 Error from function _IEFormElementGetObjByName, $_IEStatus_InvalidDataType --> IE.au3 V2.4-0 Error from function _IEFormElementGetObjByName, $_IEStatus_InvalidDataType --> IE.au3 V2.4-0 Error from function _IEFormElementGetValue, $_IEStatus_InvalidDataType --> IE.au3 V2.4-0 Error from function _IEFormElementGetValue, $_IEStatus_InvalidDataType C:\Program Files\AutoIt3\Include\IE.au3 (4246) : ==> Recursion level has been exceeded - AutoIt will quit to prevent stack overflow.: Local $status = __IEInternalErrorHandlerRegister() ->06:06:44 AutoIT3.exe ended.rc:1 +>06:06:45 AutoIt3Wrapper Finished >Exit code: 1 Time: 31492.856 I have had this quite a few times when this crashes. The program that I'm running runs all night long and is I'm sure very hard on the computer. Any Ideas people ?
Valuater Posted August 20, 2009 Posted August 20, 2009 this..._IEFormGetObjByName, $_IEStatus_NoMatchand the few below it are the real error and the real problem. The error handler..._IEInternalErrorHandlerRegister()can only handle those errors just so many times (recursion) then before the memory gets to full (stack-over flow) a message is sent by Autoit to exit the scriptAFAIK8)
DaleHohm Posted August 20, 2009 Posted August 20, 2009 Hmmm... have never seen this before. I would like to understand more about what your code is doing to that I can diagnose how this recusion is happening. You can likely work around this by breaking the error handling rule I have in the helpfile (that being if you have your own error handler, name it $oIEErrorHandler) Put this near the top of your code: $oMyErrorHandler = ObjEvent("AutoIt.Error", "__IEInternalErrorHandler") This will cause IE.au3 to fail to assign and deassign it's internal handler, but will still give you the benefit of the internal handler. Dale Free Internet Tools: DebugBar, AutoIt IE Builder, HTTP UDF, MODIV2, IE Developer Toolbar, IEDocMon, Fiddler, HTML Validator, WGet, curl MSDN docs: InternetExplorer Object, Document Object, Overviews and Tutorials, DHTML Objects, DHTML Events, WinHttpRequest, XmlHttpRequest, Cross-Frame Scripting, Office object model Automate input type=file (Related) Alternative to _IECreateEmbedded? better: _IECreatePseudoEmbedded Better Better? IE.au3 issues with Vista - Workarounds SciTe Debug mode - it's magic: #AutoIt3Wrapper_run_debug_mode=Y Doesn't work needs to be ripped out of the troubleshooting lexicon. It means that what you tried did not produce the results you expected. It begs the questions 1) what did you try?, 2) what did you expect? and 3) what happened instead? Reproducer: a small (the smallest?) piece of stand-alone code that demonstrates your trouble
Ghost21 Posted August 20, 2009 Author Posted August 20, 2009 $oIE = _IECreate($Website, "", 0, 1, 1) $oForm = _IEFormGetObjByName($oIE, $form) $oQuery = _IEFormElementGetObjByName($oForm, $Data1) $oQuery2 = _IEFormElementGetObjByName($oForm, $Data2) $CheckData1 = _IEFormElementGetValue($oQuery) $CheckData2 = _IEFormElementGetValue($oQuery2) Does the above well a few thousand times over the course of a night. It starts by getting data it needs from the web for the rest of the program if it finds anything it goes on. Then when its done or doesn't find anything it clears all the varibles and starts over.
DaleHohm Posted August 21, 2009 Posted August 21, 2009 There is no sense in calling functions you know will fail: $oForm = _IEFormGetObjByName($oIE, $form) If IsObj($oForm) Then ; do more IE stuff Else ; forget it, do something else EndIf Dale Free Internet Tools: DebugBar, AutoIt IE Builder, HTTP UDF, MODIV2, IE Developer Toolbar, IEDocMon, Fiddler, HTML Validator, WGet, curl MSDN docs: InternetExplorer Object, Document Object, Overviews and Tutorials, DHTML Objects, DHTML Events, WinHttpRequest, XmlHttpRequest, Cross-Frame Scripting, Office object model Automate input type=file (Related) Alternative to _IECreateEmbedded? better: _IECreatePseudoEmbedded Better Better? IE.au3 issues with Vista - Workarounds SciTe Debug mode - it's magic: #AutoIt3Wrapper_run_debug_mode=Y Doesn't work needs to be ripped out of the troubleshooting lexicon. It means that what you tried did not produce the results you expected. It begs the questions 1) what did you try?, 2) what did you expect? and 3) what happened instead? Reproducer: a small (the smallest?) piece of stand-alone code that demonstrates your trouble
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now