Catching EdgeGetElementData errors

Technical support and scripting issues

Moderators: Dorian (MJT support), JRL

Post Reply
kdtrog
Junior Coder
Posts: 29
Joined: Wed Mar 28, 2007 9:36 am

Catching EdgeGetElementData errors

Post by kdtrog » Sun Jun 28, 2020 1:00 pm

I have a script which is running every 30 minutes to catch a specific status via MSEdge Webbrowser. Most of the time the compiled script is running well but once or twice a day the Execution crashes and leaves the browser window open. Via logfiles I located the problem within 3 EdgeGetElentData commands.

Code: Select all

EdgeFindElements>session_id,tag name,TD,elements4
      if>elements4_count>6
        EdgeGetElementData>session_id,elements4_3,text,r8
        EdgeGetElementData>session_id,elements4_5,text,r9
        EdgeGetElementData>session_id,elements4_7,text,r10
I guess the error is a http error (for any reason which I do not know). I tried to catch the error with an "onerror" statement but it is not working. Is there any chance to continue the script after this error occurs?

User avatar
Marcus Tettmar
Site Admin
Posts: 7210
Joined: Thu Sep 19, 2002 3:00 pm
Location: Dorset, UK
Contact:

Re: Catching EdgeGetElementData errors

Post by Marcus Tettmar » Tue Jun 30, 2020 3:54 pm

Is the error in Edge, or Macro Scheduler? Have you got a screenshot? We can trap the latter, but may not be able to trap the former.
Marcus Tettmar
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar

Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?

kdtrog
Junior Coder
Posts: 29
Joined: Wed Mar 28, 2007 9:36 am

Re: Catching EdgeGetElementData errors

Post by kdtrog » Tue Jun 30, 2020 4:42 pm

The following eventlog entry is created (DAITEM.EXE is the compiled script)
Protokollname: Application
Quelle: Application Error
Datum: 30.06.2020 14:59:25
Ereignis-ID: 1000
Aufgabenkategorie:(100)
Ebene: Fehler
Schlüsselwörter:Klassisch
Benutzer: Nicht zutreffend
Computer: xxxxxxx
Beschreibung:
Name der fehlerhaften Anwendung: Daitem.exe, Version: 1.0.0.0, Zeitstempel: 0x5e6ac394
Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.14393.3659, Zeitstempel: 0x5e9140ea
Ausnahmecode: 0x0eedfade
Fehleroffset: 0x000dc562
ID des fehlerhaften Prozesses: 0x2de4
Startzeit der fehlerhaften Anwendung: 0x01d64ede39074047
Pfad der fehlerhaften Anwendung: xxxxx\Daitem.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\KERNELBASE.dll
Berichtskennung: 998363b5-573b-4a0b-b95f-fcb79e1ca513
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-06-30T12:59:25.213832000Z" />
<EventRecordID>75985</EventRecordID>
<Channel>Application</Channel>
<Computer>xxxxxx</Computer>
<Security />
</System>
<EventData>
<Data>Daitem.exe</Data>
<Data>1.0.0.0</Data>
<Data>5e6ac394</Data>
<Data>KERNELBASE.dll</Data>
<Data>10.0.14393.3659</Data>
<Data>5e9140ea</Data>
<Data>0eedfade</Data>
<Data>000dc562</Data>
<Data>2de4</Data>
<Data>01d64ede39074047</Data>
<Data>xxxxxxx\Daitem.exe</Data>
<Data>C:\WINDOWS\System32\KERNELBASE.dll</Data>
<Data>998363b5-573b-4a0b-b95f-fcb79e1ca513</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

kdtrog
Junior Coder
Posts: 29
Joined: Wed Mar 28, 2007 9:36 am

Re: Catching EdgeGetElementData errors

Post by kdtrog » Sun Jul 05, 2020 9:40 am

I transferred the script to a Chrome version and it is running since 48 hours without any problem!

Post Reply
Sign up to our newsletter for free automation tips, tricks & discounts