In Toad for Oracle 25r3 (and r2) there is a minor crash bug that we’ve encountered. The reproducible sequence of steps is as follows:
- Click Additional Home Properties ellipsis.
- Hit Escape.
- Repeat steps 1 and 2.
- Toad crashes:
- sometimes with an error box, and
- sometimes without but the whole program just disappears.
Occasionally, the crash occurs at step 2 above on the first try.
Note: We have an invalid Oracle Home that we cannot seem to get rid of which may be behind the crashes.
This is on Windows 2022 Datacenter Edition.
Cheers,
Russ
Hi Russ,
I can't reproduce this. I can open/close that dialog several times without error.
Can you send me the Toad.el file from your C:\Users\YOUR_WINDOWS_USERNAME\AppData\Roaming\Quest Software\Toad for Oracle\25.3\Logs\ folder?
Also, maybe a screen shot of what's in the "additional home properties" dialog when it opens successfully?
Feel free to email it if you don't want to post it here. john.dorlon@quest.com
Thanks
John
Artifacts email sent.
We can discuss the matter here.
Cheers,
Russ
Got it, thanks. I've got a few other irons in the fire at the moment. I'll try to reproduce this later and update when I have something to say.
1 Like
Thank you sir. There is no hurry. It is just something we noticed with r2 that I had never mentioned so that when it was still happening in r3, I decided to point it out.
I am going to try again to get rid of that invalid Oracle Home and see if that is the culprit.
Cheers,
Russ
Hi Russ,
The error does seem to be related to your invalid Oracle home, but I haven't been able to reproduce it yet.
I have a few thoughts on removing it.
- If you have made path changes, sometimes windows needs to be restarted for Toad to notice. That could be the reason for the invalid home (if you believe that it is actually valid)
- If you want to just get rid of that home I would:
a) remove it from the registry
b) remove it from the disk
c) restart windows
...the only gotcha here is that I am not sure if your Oracle clients have to be numbered starting from 1. Because if you follow these steps, they'll start with 2. I guess if that's a problem you could always remove that home also and then reinstall it.
I'll keep playing with it.
If the problem still exists for you, could you export your registry for HKEY_LOCAL_MACHINE\SOFTWARE\Oracle and email it to me? You'll have to rename the file as .txt, I'm sure.
Thank you so much John for your usual excellent support.
These goofy Windows Datacenter environments are a DOD VDI thing within AWS. I think that invalid home is an artifact of how the environments were templated and provisioned. That 23ai client that I asked VDI admins to provide with these was dorked up by them and cannot seem to be undorked except by a complete rebuild of the baseline image. We may not be able to get rid of that any other way.
Unfortunately, I have no perms to export or even look at the Windows Registry.
This issue may just have to be something we will have put up with.
Cheers,
Russ
Unfortunately, this issue is worse that we thought. On two occasions now, hitting Escape to close Toad Options caused Toad to crash without an error dialog. Bummer.
ugh, man...rough.
So, what's the problem with this client? Do the files no longer exist? If so, can you solve it by copying the good client files to the bad client location?
I tried a few differing things to reproduce it but didn't get anywhere.
We were able to cleanup that invalid Oracle Home so that now Toad just shows one Oracle Home and says it is valid. It works for making connections to databases. We fixed the Registry and the inventory.xml file to make sure everything is aligned with paths and names and home index number. We made sure the index was right in the inventory and confirmed that the Windows environment variables are set correctly pointing to that home. We have triple-checked all the various files and keys and have confirmed that everything is aligned for that one Oracle Home. (It is a full client.)
The problem is still occurring both in that Additional Home Properties dialog and Toad Options. When it crashes, sometimes Toad just disappears and sometimes it presents a “Toad(R) for Oracle has encountered a problem.” message box.
Cheers,
Russ
Can you email me the info that you have in the registry and inventory.xml? Maybe I can reproduce it with that.
Also, or at least, an updated Toad.el with the error after your changes. I saw a few different call stacks in there, just want to know which one I should be looking at.
Do you have Windows Narrator or any other kind of screen reader enabled?
One of your call stacks includes some code that only runs (on my end, at least) when Microsoft Narrator is enabled.
If you have that turned on and don't need it, try turning it off and see if that prevents the access violations - specifically the one that happens when you go into Additional Home Properties.
To be clear: I tested Toad 2025R3 on Windows Server 2022 with Narrator turned on and didn't experience any problems. I'm just saying that's what's in your call stacks.