I run several automated tasks on a desktop machine, and many of the toad.exe processes are not ending on their own. The result is multiple .exe files showing up, chewing up memory, even though there are no tasks hung on my scheduler. Any advice? I'm needing for these tasks to end the .exe occurrence after it is done running. I've attached a screen shot.
To Tony Byrnes:
Thank you for posting in Toad World!
In order to best diagnose this issue, we would appreciate the following items:
* The Automation log files
* Your .tas files that are executing on your machine
Location of Automation Log Files:
C:\Users[YourUserName]\AppData\Roaming\Quest Software\Toad Data Point 3.6\Automation
Feel free to post them in a reply or send them to me directly at Joshua.Liong@quest.com. We will analyze those files and then reply to this thread on the next course of action.
We apologize for any inconvenience.
Software Developer I,
-Joshua Liong
Do any of your jobs call another program (like Excel)? For Excel if you are running a macro you need to include an application.Quit statement at the end so control returns to the Toad job running or the job will continue to run until that step times out. Any other program called has to end or send a return value indicating success or failure back to the Toad job.
Most of these do end up being outputs in excel, but none use any macros or programming functions of excel. What could cause the return value indicating a return value for success if not an excel macro? To answer Josh’s questions, I’m not sure which log file to submit since I was not able to tell which tasks are being hung up in the system.
From: bounce-GregDavis11009@toadworld.com
To: toaddatapoint@toadworld.com
Subject: RE: [Toad Data Point - Discussion Forum] Automations Killing my Memory
Date: Fri, 1 May 2015 09:08:17 -0700
RE: Automations Killing my Memory
Reply by GregDavis11009
Do any of your jobs call another program (like Excel)? For Excel if you are running a macro you need to include an application.Quit statement at the end so control returns to the Toad job running or the job will continue to run until that step times out. Any other program called has to end or send a return value indicating success or failure back to the Toad job.
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.
I am not talking about writing out to a file. Are you using a Run Program step to; call a DOS batch job (command window), launch an application (Excel, Access, etc.)? The Run Program step waits for the called program to end which returns a zero (normal end of program) or an error value (if something went wrong) when that called application or job ends. It is possible to just leave that window open and not end (and therefore not return anyghing) so the Toad job just waits. If you do use the Run Program set a timeout value.
I follow. No, I do not call it that way.
On Fri, May 1, 2015 at 9:38 AM -0700, “GregDavis11009”
bounce-GregDavis11009@toadworld.com wrote:
RE: Automations Killing my Memory
Reply by GregDavis11009
I am not talking about writing out to a file. Are you using a Run Program step to; call a DOS batch job (command window), launch an application (Excel, Access, etc.)? The Run Program step waits for the called program to end which returns a zero (normal
end of program) or an error value (if something went wrong) when that called application or job ends. It is possible to just leave that window open and not end (and therefore not return anyghing) so the Toad job just waits. If you do use the Run Program
set a timeout value.
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.
Are you scheduling processes that might be running at the same time? In some earlier versions of TDP there was an issue when you had two many scripts starting at the same time. Upgrade to TDP 3.6.1 or spread your scripts apart.
A few do overlap, but I don’t think that is the issue. The issue is that some of the tasks are not ending, leaving the executable open.
Also, you guys said you had the overlap schedule issue in 3.5, but 3.6 would fix that.
From: bounce-Debbie_Peabody@toadworld.com
To: toaddatapoint@toadworld.com
Subject: RE: [Toad Data Point - Discussion Forum] Automations Killing my Memory
Date: Tue, 5 May 2015 19:54:41 -0700
RE: Automations Killing my Memory
Reply by Debbie Peabody
Are you scheduling processes that might be running at the same time? In some earlier versions of TDP there was an issue when you had two many scripts starting at the same time. Upgrade to TDP 3.6.1 or spread your scripts apart.
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.
I’m in agreement with Tony. We’ve seen, even on 3.6 that running a handful of tasks at the same time using TDP (We’re not even using the task scheduler in Toad, but rather the Task Scheduler in Windows) and the tasks are locking up if you have more than about 3 or 4. Its a concern of ours, because we were wanting this ability due to the high amounts of reports we run each morning. Is there a maximum amount of schedules that TDP can handle at the same time?
TDP scheduling is Windows Task Scheduler. It just makes setting up a scheduling package easier and passed the scheduling info to Windows Task Scheduler. One thing you need to be careful of is how much memory your tasks are using. Toad + Excel + large extracts can easily consume all of a PC’s memory. Try not to run multiple extracts to Excel at the same time or put TDP on a server with tons of memory and processors and schedule your jobs to run there. Extracting to a csv or pipe delimited file takes a lot less resources (if that can fit into your needs).
The first thing that an automation script does is compile the script. This is done in a different app domain and if there are not enough resources the app will hang. I found this in a earlier version of TDP and entered a fix. You should have this fix but your symptoms still sound like this issue. Spreading out the schedules would help the compile resource issue.
Another thing that can cause an app to hang is if a message box is displayed and the app is waiting for user input. We really should have handled all of these types of errors but perhaps you found a new one. To check this out, look at the right hand tray. Are there any current Toad icons? If so click on them and wait for the app to display in visual mode(It takes awhile). This should display the message box or at a minimum show what script is hanging.
I believe you sent in log files. All of those show successful closer. So the ones we are looking for are not those.
Thank you. Josh asked for the TAS files as well but before going that route, I’ll click the icon. I tried to do it from home last night but it appears to be frozen from my RDP connection, so I’ll send a screen shot of what i see when I get in the office this morning.
From: bounce-Debbie_Peabody@toadworld.com
To: toaddatapoint@toadworld.com
Subject: RE: [Toad Data Point - Discussion Forum] Automations Killing my Memory
Date: Mon, 11 May 2015 14:47:23 -0700
RE: Automations Killing my Memory
Reply by Debbie Peabody
The first thing that an automation script does is compile the script. This is done in a different app domain and if there are not enough resources the app will hang. I found this in a earlier version of TDP and entered a fix. You should have this fix but your symptoms still sound like this issue. Spreading out the schedules would help the compile resource issue.
Another thing that can cause an app to hang is if a message box is displayed and the app is waiting for user input. We really should have handled all of these types of errors but perhaps you found a new one. To check this out, look at the right hand tray. Are there any current Toad icons? If so click on them and wait for the app to display in visual mode(It takes awhile). This should display the message box or at a minimum show what script is hanging.
I believe you sent in log files. All of those show successful closer. So the ones we are looking for are not those.
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.
I think it might be faster to open a support ticket and set up a webex. I think we could gather data on what might be happening faster.
Thanks Debbie. Is that something I need to submit on my end or do you submit? Just let me know next steps and I will make myself available.
From: bounce-Debbie_Peabody@toadworld.com
To: toaddatapoint@toadworld.com
Subject: RE: [Toad Data Point - Discussion Forum] Automations Killing my Memory
Date: Mon, 18 May 2015 12:16:16 -0700
RE: Automations Killing my Memory
Reply by Debbie Peabody
I think it might be faster to open a support ticket and set up a webex. I think we could gather data on what might be happening faster.
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.
On the Help menu there is Product Support link. On that page it should say how to make a support ticket.