Author Topic: TERMINAL WIL ERROR=>9999 (User requested Cancel)  (Read 51 times)

mcvpjd3

  • Newbie
  • *
  • Posts: 41
TERMINAL WIL ERROR=>9999 (User requested Cancel)
« on: July 31, 2017, 08:58:05 am »
Hi all, I'm hoping someone here will see this and know immediately what's going on, otherwise this may get messy....

I've got a winbatch exe that we use for a login script for all users in our domain which runs fine. We are about to migrate all our users to a new domain and are testing the script in the new domain, and guess what...

So in the source domain is pops up a little window to show you what it's doing, when we run it in the new domain, the window pops up, but then it stops. If I run it with debugtrace at the end I get these lines:

[ Dialog Callback Triggered ]
ButtonPushed=Dialog("MyDialog")
(47) CALLING UDF (mydialogcallbackproc)
RETURNING FROM UDF (mydialogcallbackproc)
[ Dialog Callback Triggered ]
ButtonPushed=Dialog("MyDialog")
(1061) CALLING UDF (mydialogcallbackproc)
RETURNING FROM UDF (mydialogcallbackproc)
ButtonPushed=Dialog("MyDialog")
(1108) STATEMENT SKIPPED

TERMINAL WIL ERROR=>9999 (User requested Cancel)


If I run it in the source domain it works fine and I get this at the end:

[ Dialog Callback Triggered ]
ButtonPushed=Dialog("MyDialog")
(219) CALLING UDF (mydialogcallbackproc)
RETURNING FROM UDF (mydialogcallbackproc)
[ Dialog Callback Triggered ]
ButtonPushed=Dialog("MyDialog")
(1233) CALLING UDF (mydialogcallbackproc)
RETURNING FROM UDF (mydialogcallbackproc)

WIL ERROR SUPPRESSED =>9000

ButtonPushed=Dialog("MyDialog")
(3947) ==>FALSE=> (skipped)
--- Normal termination ---
;;;END OF JOB;;;


The obvious difference is the WIL ERROR SUPPRESSED and TERMINAL WIL ERROR messages, but I'm not sure why I'm getting these? Any ideas?

Thanks

td

  • Tech Support
  • *****
  • Posts: 2114
    • WinBatch
Re: TERMINAL WIL ERROR=>9999 (User requested Cancel)
« Reply #1 on: July 31, 2017, 01:51:39 pm »
9000 is the normal termination.  9999 means that WinBatch received a cancel or close command in it's message loop.  Cancel and close command Windows messages are generally but not always the result of some user interaction with the UI.  For example, user the mouse to press the Cancel button in a message box.  Neither number is an errors and both are part of normal processing.

Without a lot more information it difficult to speculate in a useful way about what is causing the difference in behavior in this case.     
"le succès est une terrible maîtresse"
(French translation), Bill Gates