I have a Toad automation job that runs daily… The initial job will run/complete successfully however a window pops up with the Stack Trace Error: “The calling thread cannot access this object because a different thread owns it.”. If I don’t close out the stack trace window the same job that is scheduled for the next day will not fire. I am having to manually clear out the Stack trace errors daily so that the subsequent jobs will run as intended which defeats the whole purpose of automation. Any help on this is appreciated as I have not found a resolution and spent countless hours looking for one - still perplexed…Thanks John
Toad Automation Stack Trace Error: Calling thread cannot access this object because a different thread owns it.
I have the same problem in this new Beta posted on Apr 9. I had to use the 3.4 trial.