Toad Closes while attempting to Connect to Database

[mojoala]

When I click the "Connect" button, TOAD immediately closes.
It closes randomly on FACTSTT3 and FACTSUAT.
In order to open any of the others, I have to connect to one of the two listed above and then connect to the desired one IE FACTSSIC

10/25 started to have problems and got a hint on how to fix this by renaming the Roaming folder. Renamed the folder and relaunched Toad and things were fine.

This morning 11/5/2024 it started doing it again. So I did the same thing again.
Lasted about 30 minutes before it started to do it again

**

**

What are your suggestions?

[Gita.Sharifi]

Have you tried the latest edition of Toad Version 7.4.1?
It might be best to open a open a Support ticket if issue persists.

[mojoala]

We are a state government organization.
We are not at liberty to try a newer version.

And how do I get a ticket started.

[Gita.Sharifi]

You should be able to get a ticket started using this page: Create Technical Case

[mojoala]

Tickets are not allowed for 6.5 version.
Only for the 7 versions.

[mojoala]

And when I can get a connect to work.
I have to continuously hit "Save" because at any moment it will arbitrarily close.

[mojoala]

Well we did an uninstall and reinstalled the program.
This worked for a few days.
The problem is back.

Also when I right click on a selected code, the program closes.

[mojoala]

Well I found out what is causing it.
In the "Open on New Connection" and having "Database Explorer" checked:

I uncheck it and the problem goes away.

In addition when I have none of these checked and I have connected to a database, then I go to Tools | Explorer, the program immediately closes.

Now if do Tools | Query Builder first then Tools | Explorer it does not close the program.

The question now is why?

[mojoala]

Okay, finally updated to 7.4.1 version of Toad.
It is doing the same thing.

I tried submitting a ticket but am getting an error on clicking the submit button.

clicking on "Customer Service" takes you to here: ( which is worthless )

[Gita.Sharifi]

Perhaps we can help you in opening a support ticket. I will message you privately for additional details.

[mojoala]

Finally opened a support ticket after calling Quest Software directly after discovering our license is a permanent license and our service contract is permanent.

An Engineer called me back within 5 minutes as this was a "level 1" issue as Toad is 70% of my daily work load during a job as a Software Engineer.

He established a Teams session and spent an hour and fifteen minutes watching me duplicate this issue. We even discovered a new issue. The program would close trying to open an Sql file.

We placed Toad in debug mode by adding " /log=all" at the end of the target. The logs did not report anything at all. He requested I send him my event viewer logs after we filtered them. At the end of the session, he agreed with our IT staff that my Laptop would need to be re-imaged as he believed it was an OS issue. At that point we terminated the Teams session.

I was highly disappointed in the outcome.

About 30 minutes later the Engineer emailed me after he had reviewed the Event Viewer logs.

He found this:

It was only 110KB in size.
I replied that it did exist and it was small.
at which poiint the Engineer replied:

I backed it up and deleted it.

This solved the problem. It did not try to re-create the log file.

Being a Software Engineer myself I can speculate there is code in the Toad program that does something like this:

Procedure WriteTodb2diagLog(Information: String);
Begin
FileName = "C:\ProgramData\IBM\DB2\DB2COPY1\DB2\db2diag.log";
If Exists(FileName )
Try
FileName.Append(Information)
Except
Application.Terminate;
End;
End;

So in Summary, db2diag.log became corrupt and no longer was able to be written to and deleting it solved the problem.

[Julie_Hyman]

Thank you for helping us diagnose this and for the time you spent on this. We have forwarded the case to dev