This question is not answered

TDP 3.3.0.1526 - All Automation Tasks Give Result 0xc0000005

Follow / 8 Aug 2013 at 8:39pm

I've built a number of new automation scripts - from scratch - using TDP 3.3.0.1526, and I've noticed that despite them completing successfully, they all report a "Last Result" of 0xc0000005 to the Windows Task Scheduler, instead of the previous 0x0 that versions prior to 3.3.0.1526 reported.

Is this a bug?  All the tasks that report this result code actually do complete just fine so far as we're able to tell, so it's just a bit odd.

All tasks are running on a Windows XP SP3 box, and it occurs on more than one machine.

Replies

All Replies
  • Follow / 9 Aug 2013 at 1:26am
    That is a tough one. I have a few scheduled tasks that have that return code too. They run fine. When I look into the return code it says “Access Denied” but I don’t see how that applies in this case.
     
    There is a log file for the windows scheduler but when I look at mine I don’t see anything useful. I don’t really know how else to track this down. Let me know if you have any other insights into this.
     
    Debbie
     
    From: N.B. [mailto:bounce-NB@toadworld.com]
    Sent: Thursday, August 08, 2013 12:40 PM
    To: toaddatapoint@toadworld.com
    Subject: [Toad Data Point - Discussion Forum] TDP 3.3.0.1526 - All Automation Tasks Give Result 0xc0000005
     
    Thread created by N.B.

    I've built a number of new automation scripts - from scratch - using TDP 3.3.0.1526, and I've noticed that despite them completing successfully, they all report a "Last Result" of 0xc0000005 to the Windows Task Scheduler, instead of the previous 0x0 that versions prior to 3.3.0.1526 reported.

    Is this a bug?  All the tasks that report this result code actually do complete just fine so far as we're able to tell, so it's just a bit odd.

    All tasks are running on a Windows XP SP3 box, and it occurs on more than one machine.

    To reply, please reply-all to this email.

    Stop receiving emails on this subject.
    Or Unsubscribe from Toad Data Point - General notifications altogether.
    Toad Data Point - Discussion Forum

    Flag this post as spam/abuse.


  • Follow / 12 Aug 2013 at 4:31pm

    The only thing I can think of is that TDP - or Windows - is trying to access a resource that it's not allowed to access when the application closes - is there a way to enable an application-level log file to determine if that's occurring?

    We've finally got a Windows 7 Pro test box spun up for me and I'm going to switch one of the automation's that gives this return code to it and see if the enhanced Task Manager in Win 7 gives any additional insight - or if it goes away entirely.

  • Follow / 14 Aug 2013 at 12:35am

    Try this: support.quest.com/SolutionDetail.aspx

    It worked for me.

    After installing Microsoft .NET Framework 4.5, go into the Task Scheduler and re-apply the username and password.

  • Follow / 14 Aug 2013 at 5:23am

    I don't really have any other logging level to turn on within TDP. But you might look at the event log. This might turn up something.

  • Follow / 14 Aug 2013 at 2:21pm

    TDP_OWL - that's not the error message that I'm getting, in fact, there is no error message, and the automation's run just fine; it's just the odd result code.  Also, .NET 4.5 is already installed on both systems, as it's required for a different application.

    Debbie Peabody
    I don't really have any other logging level to turn on within TDP. But you might look at the event log. This might turn up something.

    If you're referring to the Toad section of the System Event Viewer, there's nothing there, and there's nothing in the log files.

  • Follow / 17 Aug 2013 at 2:42am
    I am afraid I am stumped on this one. I’ll ask Igor if he has any ideas.
     
    Debbie
     
    From: N.B. [mailto:bounce-NB@toadworld.com]
    Sent: Wednesday, August 14, 2013 6:22 AM
    To: toaddatapoint@toadworld.com
    Subject: RE: [Toad Data Point - Discussion Forum] TDP 3.3.0.1526 - All Automation Tasks Give Result 0xc0000005
     
    Reply by N.B.

    TDP_OWL - that's not the error message that I'm getting, in fact, there is no error message, and the automation's run just fine; it's just the odd result code.  Also, .NET 4.5 is already installed on both systems, as it's required for a different application.

    Debbie Peabody
    I don't really have any other logging level to turn on within TDP. But you might look at the event log. This might turn up something.

    If you're referring to the Toad section of the System Event Viewer, there's nothing there, and there's nothing in the log files.

    To reply, please reply-all to this email.

    Stop receiving emails on this subject.
    Or Unsubscribe from Toad Data Point - General notifications altogether.
    Toad Data Point - Discussion Forum

    Flag this post as spam/abuse.


  • Follow / 23 Jan 2014 at 10:04pm

    Has this ever been figured out?  I'm getting the same issue for TDP 3.4.  Running on a XP machine.

  • Follow / 24 Jan 2014 at 2:44am

    I still think this is a .net issue and does not occur with .net 4.5 on Win 7. Windows does not have a fix for it for XP.