Automation email not working. HELP!!!!!...please...

Toad Data Point & Toad Intelligence Central
1

Hey everyone, I have about 20 scheduled automation jobs that email out reports (qry extracts) from Toad. This has been working fine for well over a year. But all of the sudden the other day it just stopeed working. I don;t get an error message in toad, I get a windows error that says Toad has encountered a problem and needs to close. This error msg happens every time a job tries to run on it’s schedule. So none of these reports are going out. Now, the weird thing is, if I bring up the actual automation file and run a test, it sends out the email with no problem. I have tried everything I can think of. I have done a system restore, I;ve uninstalled and reinstalled the application, I’ve tried a newer version of Toad for DA, but still the same error.
Also, I see this error in the event viewer; “.NET Runtime 2.0 Error”;"
Faulting application toad.exe, version 2.7.0.348, stamp 4cc0a3ad, faulting module kernel32.dll, version 5.1.2600.5781, stamp 49c4f482, debug? 0, fault address 0x00012afb."

Any help would be greatly appreciated!

Thanks, John

2

I think I’ve found the solution. Under services, I noticed that the .NET runtime service was set to Manual. I changed it to automatic and the jobs started working again. So hopefully this was it.

3

Very bizarre. Any idea how it got set to manual?

Anyway, glad it is working again.

Debbie

4

I also was having this problem. It became obvious that it was my pc problem rather than TDA. With this information now mine is working also! Yahooo!
My guess for me is that when I went to a new pc, the corporation default set this to Manual. Changed to Automatic. I just if I would eventually see someone else with the same problem and a fix would follow.

5

This is what was previously hampering my ability to use TDA’s automation as well.

Looks like it’s actually a result of a .NET updated from Microsoft - or a Corporate security policy. I know it really went nuts for me when we switched to Symantec Endpoint Enterprise on our desktops.

Debbie Peabody wrote:

Very bizarre. Any idea how it got set to manual?

Anyway, glad it is working again.

Debbie