Toad World® Forums

TDP crashes when attempting to query Excel

Toad Data Point 5.1.2.166 (64 bit)

Using TDP I am able to successfully connect to Excel data sources and create a visual query in the query builder, but when I attempt to execute the query I receive the following Windows error and then TDP closes:

"Toad Data Point has stopped working
A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."

I have already tried uninstalling and reinstalling with no luck. Any other ideas?

image

Can you tell me what Office version and what bitness do you have?

Also, can you describe to me a little bit more your query? Are you using some joins or some conditions?
If TDP crash without any exception you should be able to see error in Event Viewer which is part operation system.
Filip

Office 2016, 64 bit

For troubleshooting purposes, I am attempting a very simple query, no joins or filter conditions (though the more typical "real world" use case would be a cross-connection query with Oracle db).

Event Viewer lists two associated events:

.NET Runtime
Application: toad.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at Quest.Toad.NativeOdbc.OdbcAPI.SQLDriverConnectW(Quest.Toad.NativeOdbc.OdbcHandle, IntPtr, System.String, Int16, System.Text.StringBuilder, Int16, Int16 ByRef, DRIVER_COMPLETION_MODES)
at Quest.Toad.NativeOdbc.OdbcDriverManager.PerformConnectionWithCompletionMode(Quest.Toad.NativeOdbc.OdbcHandle, IntPtr, System.String, DRIVER_COMPLETION_MODES)

Exception Info: Quest.Toad.Exceptions.DatabaseException
at Quest.Toad.NativeOdbc.OdbcDriverManager.PerformConnectionWithCompletionMode(Quest.Toad.NativeOdbc.OdbcHandle, IntPtr, System.String, DRIVER_COMPLETION_MODES)
at Quest.Toad.NativeOdbc.NativeOdbcConnection.Open()
at Quest.Toad.NativeOdbc.NativeOdbcConnection.GetSupportedDataTypes()
at Quest.Toad.NativeOdbc.UnManagedColumnDescriptor.get_DatabaseType()
at Quest.Toad.Db.Connection.CreateTable(System.Data.IDataReader, Quest.FastData.FastReadOptions)
at Quest.Toad.Db.ToadDataAdapter.InternalReadBackground()
at Quest.Toad.Db.ToadDataAdapter.InternalFillBackground()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

Application Error
Faulting application name: toad.exe, version: 5.1.2.166, time stamp: 0x5dd270a3
Faulting module name: KERNELBASE.dll, version: 10.0.18362.418, time stamp: 0xfba22159
Exception code: 0xe0434352
Fault offset: 0x000000000003a839
Faulting process id: 0x2724
Faulting application start time: 0x01d5d1fae581d805
Faulting application path: C:\Program Files\Quest Software\Toad Data Point 5.1\toad.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: e26637cd-3838-46fc-bfd9-4b631d899152
Faulting package full name:
Faulting package-relative application ID:

From the error you send me it looks like there is some issue with ODBC driver. This driver is installed with your office and Toad using it for get data from your workbook.

You can check your ODBC driver in system first:
image

Then you can try Office installer and check if you check ODBC driver and .NET Programmability Support.
Filip

ODBC and .NET seemed fine as far as I could tell.

Research on KERNELBASE.dll error led me to eventually reset Windows via Recovery in Settings. This appears to have fixed the problem.