| Data source QBs verification failed using ColdFusion MX 7. Driver not capable. |
| Author |
Message |
|
|
| Posted : 2006-10-27 10:06:21 |
Hey, I'm trying to run an UPDATE query on ItemInventory table, but even if I only try to update the Name, it throws this error...
Data source QBs verification failed.
|
|
The root cause was that: java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket][QODBC] Driver not capable
|
The Query: <cfquery name="UpdateItem" datasource="QBs"> UPDATE ItemInventory SET Name = "TestName" WHERE ListID = '172-blahblah-000' </cfquery>
I'm using: ColdFusion MX 7 QODBC 7.0.00.199 Web Server Edition (not trial) QuickBooks Enterprise 6.0
Thanks, Marty |
|
|
|
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-10-27 10:29:44 |
What is the actual error in the Review QODBC Messages log at the bottom of the QODBCLOG.TXT file in the QODBC Setup Screen?
See also: Does QODBC work with Coldfusion? |
|
|
|
|
|
| Posted : 2006-10-27 11:25:05 |
Hello, thanks for the quick response,
MY SOLUTION: I restarted Quickbooks and this "Driver not capable" error went away.
NOTES: I cannot read the log file. I get this message every time... File: QODBCLOG.TXT is empty
Thanks - Marty |
|
|
|
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-10-27 14:51:03 |
That's good news. Since your last post I found a bug when doing UPDATEs using QODBC v7.00.00.194, so please update to v7.00.00.199 if you haven't already done so.
The log file only contains errors from SQL statements and it looks like you didn't get that far because the connection failed. |
|
|
|
|
|
| Posted : 2006-10-28 02:15:52 |
Hello,
SYMPTOM: Data source QBs verification failed. The root cause was that: java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket][QODBC] Driver not capable.
I thought that by restarting QuickBooks and/or the QODBC Remote Connector had fixed this issue, but yesterday's temporary fix was just a fluke.
This error occurs any time I try to use an UPDATE statement using the QODBC Remote Connector with ColdFusion MX 7. SELECT and INSERT INTO statements work just fine. Also, using the VB Demo, ALL statements work just fine (UPDATE, SELECT, and INSERT INTO), so I know it's just when trying to UPDATE through the Remote Connector.
I have tried uninstalling and reinstalling the QODBC driver, but that didn't work either. I've noticed this "Driver not capable" error on other forums with regards to connecting to Oracle and Sybase databases and other ODBC database connections - thought this might help when troubleshooting this issue.
Thanks, Marty |
|
|
|
|
|
| Posted : 2006-10-28 05:10:05 |
It turns out that simple INSERT INTO statements do not work either. Running the following query produced the same error...
<cfquery name="insertMainCategory" datasource="QBs"> INSERT INTO Account ( Name, AccountType ) VALUES ( 'TEST', 'Income' ) </cfquery>
However, this INSERT INTO statement worked just fine using the VB Demo program...
INSERT INTO Account ( Name, AccountType ) VALUES ( 'TEST', 'Income' )
Thanks, Marty |
|
|
|
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-10-28 08:08:21 |
The error, "Driver not capable" is not a QODBC Error. You will need to contact the Macromedia - ColdFusion Support Center directly at: http://www.adobe.com/support/coldfusion/ for further clarification.
It seems to suggest the error can also be caused by specifying a password when you don't need one or using an incorrect password. |
|
|
|
|
|
| Posted : 2006-10-29 04:35:05 |
Ya, that seems right.
To narrow it down for everyone reading, we have an error-reporting issue with using ColdFusion MX 7 and the QODBC Remote Connector -- Data source QBs verification failed. The root cause was that: java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket][QODBC] Driver not capable. --
At this point, we have moved over to the DCOM Server way of connecting ColdFusion to QuickBooks using the QODBC Driver Web Server Edition. The DCOM approach is working flawlessly without errors popping up for INSERT INTO and UPDATE queries. This is a workaround for now until we can find out why ColdFusion has issues with the QODBC Remote Connector (IBiz Integrator for QuickBooks, a program by nsoftware, is more precisely what the issue is with between ColdFusion). We'll get ColdFusion MX 7 working with QuickBooks using the QODBC Remote Connector and report our findings here.
Thanks, Marty |
|
|
|
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-10-29 13:06:22 |
| Thanks, I look forward to seeing further posts. Just so everyone else knows, the use of the QODBC DCOMs using the QODBC Server Edition to connect with applications running as, or through system services is our preferred method. The use of the QODBC Remote Connector and the iBiz Remote Connector was designed to connect QODBC to QuickBooks running on another machine, not connect QODBC to services which it just happens to do. |
|
|
|
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-12-20 10:22:36 |
| This problem could be caused by SQL_SLONG types. In QODBC v7.00.00.204 we have added conversion support for SQL_C_SLONG, SQL_C_ULONG, and SQL_C_SSHORT. See: QODBC v7.0.0.204 Released for more. |
|
|
|