Page 1 of 1

Error in AddItem2() under 64bit Windows 8 and some Win7

Posted: Sat Apr 04, 2015 4:58 am
by edwinsi
Hi,

I'm using vcl scheduling agent Version 2.0.11.0, and it seems to have problems in some cases under 64bit Windows, see call stack produced by madExcept:

--------------------------------------------------------------------------------------------------
system language : Danish
processors : 8x Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz
physical memory : 4300/8151 MB (free/total)
free disk space : (C:) 49.85 GB
display mode : 1920x1080, 32 bit
largest free block : 912.02 MB
compiled with : Delphi XE4
madExcept version : 4.0.11
callstack crc : $8b66f938, $320a8912, $b8678d17
exception number : 1
exception class : EOleException
exception message : The task image is corrupt or has been tampered with.

main thread ($19f4):
00b9b2e7 OwnMyCopy.exe saTask 1182 TTaskScheduler.AddItem2
00b9ab80 OwnMyCopy.exe saTask 987 TTaskScheduler.Refresh
--------------------------------------------------------------------------------------------------

Any idea? Thanks.

Posted: Tue Apr 07, 2015 4:09 pm
by edwinsi
Hi, I'm a paid user and my Order Number: 447805065.

Would you help me? Thanks.

Posted: Mon Apr 13, 2015 8:12 am
by isiticov
Hello,


Sorry for the delay with reply. I've missed this post. It looks like the EXE file specified in some task item is invalid and OS raises this error. Could you please check if this happens only on specific EXEs and in this case if these EXEs are valid?

Posted: Mon Apr 13, 2015 2:04 pm
by edwinsi
Thanks for your reply.

The .EXE is valid, otherwise I wouldn't be able to getting the stack tracing messages I posted - the .EXE being scheduled is the one that reported this error message to the user and the user sent it to me.

Posted: Tue Apr 14, 2015 2:19 am
by isiticov
Do you mean that the same EXE file is scheduled in task scheduler and is "running" when error appears?

Posted: Tue Apr 14, 2015 4:51 am
by edwinsi
Yes, there is only one EXE involved in question, but it's not scheduling itself when the error happened, as you can see in the stack trace, it calls the .Refresh() to list all scheduled tasks in the system and finds the one that it manages.

Posted: Tue Apr 14, 2015 12:37 pm
by isiticov