Strange ERROR box

[pete_wilde]

Hi Guys,

I have a very, very, very long script.

Occasionally, it throws up a strange error dialogue box.
It's a standard Windows dialogue box, similar to that generated with the MsgBox ( flag, "title", "text" [, timeout = 0 [, hwnd]] ) command.

However,  it shows no line number, and the window just says "Error". There is a single Ok button, which when clicked causes the script to exit.

It's not part of my coding, so I am guessing that it is being generated by the AutoIT interpreter, but I have no idea why.

The script is hundreds of lines long, so it's not something which I can realistically trace without a line number.

I do have other scripts which also run 24/7, and none of them have this problem.

Any ideas as to why such an unknown error box gets generated.

That would at least give me a starting point.

Many thanks,
Pete



 

[Nine]

Put some log into your script to know where the error occurs.  Asking such a question is pretty much impossible to answer unless we know what the statement (and its surroundings) is.

Then create a small reproducible and runnable script that we can test ourselves. 

Edited December 27, 2022 by Nine

[Dan_555]

You could start to look if your script contains a message box with that message. 

I sometime place either a messagebox or console write lines in my script, for debugging purposes.
Then i know where exactly the error happened...

 

Edited December 28, 2022 by Dan_555

[pixelsearch]

2 hours ago, Dan_555 said:

I sometime place either a messagebox or console write lines in my script, for debugging purposes [...]

@Dan_555 I do same during the debugging phase, using an abbreviation in Scite Editor. In fact there are only 2 abbreviations (until now) in my abbrev.properties file :

1) 1st abbreviation : err

err=If @error Then ConsoleWrite("Line #" & @ScriptLineNumber & "   @error = " & @error & @crlf)\n

Typing err then Ctrl-b will replace the letters err with the following line in the script :

If @error Then ConsoleWrite("Line #" & @ScriptLineNumber & "   @error = " & @error & @crlf)

2) 2nd abbreviation : b

b=Local Static $iCounter = 0\n$iCounter += 1\nConsoleWrite("$iCounter = " & $iCounter & @crlf)\n

Typing b then Ctrl-b will replace the letter b with the following 3 lines in the script :

Local Static $iCounter = 0
$iCounter += 1
ConsoleWrite("$iCounter = " & $iCounter & @crlf)

These 3 lines are often useful for me (used "as is" or as a frame) inside a function during the debugging phase. I choosed "b" because it's the easiest abbreviation to type : as you already got a finger placed on the b key, then you just need a finger from the other hand to be placed on the Ctrl key

Guess  which abbreviation I use most 

[argumentum]

 

[water]

Which UDFs do you #include in your script?
Maybe there is a debugging MsgBox left/forgotten.
 

[JLogan3o13]

On 12/27/2022 at 2:09 PM, pete_wilde said:

The script is hundreds of lines long, so it's not something which I can realistically trace without a line number.

The only reason for this is A: It is not your script but one you copied without knowing quite what it does, or B: your script that includes zero error-checking. Either way, as suggested above, you need to put some effort into going through the script line by line so you can properly add error-checking and logging. The alternative is to continually be at a loss like this whenever something unexpected happens with it.

[pete_wilde]

21 hours ago, water said:

Which UDFs do you #include in your script?
Maybe there is a debugging MsgBox left/forgotten.
 

Good thinking.  I will check that. Thanks