[QODBC-Desktop] Troubleshooting - QODBC Driver crashes QuickBooks 2017 on Close
Posted by Jack - QODBC Support on 03 August 2017 12:42 PM
Troubleshooting - QODBC Driver crashes QuickBooks 2017 on Close
QODBC crashes QB Desktop 2017 after completing all SQL transactions. Here are the details.
1. SQL command is sent to the QODBC connector
2. QODBC connector opens up a QuickBooks instance in the background on the server. i.e., View through Task Manager QBW32.exe
3. QODBC connector executes all SQL statements successfully. i.e., SELECT and INSERT statements
4. QODBC goes into a listening mode for about 30 seconds. i.e., SLQFreeStmt
5. QODBC sends the final command to close all connections. i.e., SQLDisconnect
6. Upon the SQLDisconnect command, the QODBC connector successfully disconnects from SQL.
7. Upon the SQLDisconnect command, the QODBC connector crashes QuickBooks Desktop 2017 in an attempt to close the QuickBooks instance in the background. i.e., QBW32.exe sends a critical error that it hit.
8. We must manually close the critical error box to send another SQL command to the QODBC connector. Very cumbersome to our process.
The issue is related to Microsoft .NET Framework.
QuickBooks 2017 installs Microsoft .NET Framework 4.6. If your machine is already updated to 4.7, you may face this issue.
To resolve this issue, You need to uninstall QuickBooks 2017 and Microsoft .NET Framework 4.7 & Reinstall QuickBooks 2017, which installs .NET Framework 4.6. After that, you can upgrade from Microsoft .NET Framework 4.6 to Microsoft .NET Framework 4.7.
This will fix the unexpected crash errors on the QuickBooks connector closing QuickBooks.