Toad version: is getting crashed due to below error. Any suggestion is really helpful

Faulting application name: Toad.exe, version:, time stamp: 0x6412279d
Faulting module name: ConnPoolLib.dll_unloaded, version:, time stamp: 0x613584c4
Exception code: 0xc0000005
Fault offset: 0x00000000000884c9
Faulting process id: 0x16ec
Faulting application start time: 0x01d9bee816c1c759
Faulting application path: C:\Program Files\Quest Software\Toad for Oracle 2023 R1 Trial Edition\Toad for Oracle 16.3 Trial\Toad.exe
Faulting module path: ConnPoolLib.dll
Report Id: bfb775a4-d310-494b-baaa-fecd9c893bf3
Faulting package full name:
Faulting package-relative application ID:

Hi Piyush,

What are you doing in Toad when that error happens? If you can give steps to make the error happen, that will help. The error above doesn't tell me much. Can you give a screen shot of the error shown by Toad?



Toad Version:
Toad Menu -> Database -> Diagnose -> Code Analysis -> Load Any PL/SQL Object (procedure) and Run Analyzed Code for all the selected Items.

Are you connected without using an Oracle client? or using an Oracle Proxy user when you connect (such as: User1[USER2] )?

Both of these are bugs in Code Analysis that were recently fixed for the next Toad version.

You can work around by not connecting in the ways mentioned above, or if you are using "SQL Scan" here, change to just "run review"


Thanks John for your response.

I am connected using Oracle client with User1.
I am getting this on "Run SQL Scan" and "Run Review and SQL Scan".

Also I will try work around and share my findings.

Are you using External Authentication? We also noticed that doesn't work either with SQL Scan, but I don't have a solution for it. (other than don't use SQL Scan)

I am using Oracle 19c client to connect Oracle 12c server using Toad version: (Trial Version).
Actually I am doing POC around some PL/SQL objects due to which I will be needing both the options working. - "Run SQL Scan" and "Run Review and SQL Scan"

"Both of these are bugs in Code Analysis that were recently fixed for the next Toad version." -
Could you please help me with Stable of Toad where these issues has been fixed. Also I have to proposed the stable toad version.

Ok, but are you using external authentication or proxy connection? Because if you're not, then whatever you are experiencing may be a different bug than what we fixed.

On the login window, External authentication looks like this:


Proxy connection looks like this:


If you are logging in with Proxy then bug is fixed in beta.
If you are logging in with External Authentication, then the bug is not fixed in beta.

If neither of these describe your problem, then I am not sure yet why you are having the problem and it is likely not fixed in beta.

The fix is in a beta version, which doesn't have a trial. The beta version only works when you have the latest licensed version.

So all I can suggest at this point is:

  1. Don't use SQL Scan
  2. Don't log in as proxy or external
  3. Make sure that "connect using Oracle client" is checked on the login window.