Cannot fetch a row from OLE DB provider.. using QuickBooks 2003 |
Author |
Message |
|
Posted : 2007-03-30 07:18:18 |
Hello, I am evaluating the Server Edition on a WinXP Pro, QB2003, SQL2005 machine.
I set up the software, QODBC connection, etc....and i can run Queries in the VB Demo app. I set up a linked server as described in other posts. I setup the dcom using the auto-decom utility, and i can run the TestDCOM.asp page with successfull replies. When i open up SQL2005 managment studio, i can run certain queries like :
SELECT * FROM ISO_GROUP_QB...HostSupportedVersions
but I receive the following error when I try to query other tables like
SELECT ListID, Name FROM ISO_GROUP_QB...Customer
the error returned is:
OLE DB provider "MSDASQL" for linked server "ISO_GROUP_QB" returned message "[QODBC] Error".
Msg 7330, Level 16, State 2, Line 1
Cannot fetch a row from OLE DB provider "MSDASQL" for linked server "ISO_GROUP_QB"
I have tried with DCOM checked, without it checked, and with Optimized checked/unchecked but still the same error. Does anyone out htere have any idea how I can get this stuff working? Any Help is greatly appreicated.
Thanks, Mike
|
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2007-03-30 09:27:12 |
You may need to check the "Run 2.1 ODBC Compatibility" checkbox - Certain applications require ODBC 2.1 Compatibility to use QODBC. For example, without this option turned on, recordsets will be returned with no rowsets or only 1 rowset.
|
|
|
|
|
Posted : 2007-03-30 10:31:12 |
Hi Tom, Thank you for the reply. That option is already checked. That tab looks exactly like your screenshot, except the "Integrated Application Defaults" section on my tab is grayed out (although the same options are checked). Any other ideas? Thanks, Mike
|
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2007-03-30 11:14:29 |
What's the actual error at the end of the QODBC Message log? |
|
|
|
|
Posted : 2007-03-30 11:21:57 |
There is nothing in the "QODBC Message" button, but the following is in the "SDK Messages" button. When I run a query in SQL it actually pulls back the column layout (with no records of course), and the error posted above on the Messages tab. The only messages in the SQL log are just informational from me changing flags at setup (they are down below).
20070329.205212 D 4984 SAXParseMediator EndElement: empty aggregate: name and currentTag are the same: HostQueryRq 20070329.205212 D 4984 QBXMLMsgs HostQueryRq 20070329.205212 D 4984 QBXMLMsgs DataExtDefQueryRq 20070329.205212 I 4984 SpecVersion Current version of qbXML in use: 2.1 20070329.205212 D 4984 MsgSetHandler Parsing took 0.0780 seconds 20070329.205212 I 4984 QBSDKMsgSetHandler QUERY: Host 20070329.205212 I 4984 QBSDKMsgSetHandler Request 1 completed successfully. 20070329.205212 I 4984 QBSDKMsgSetHandler QUERY: DataExtension Definition 20070329.205212 I 4984 QBSDKMsgSetHandler Request 3 completed successfully. 20070329.205212 D 4984 QBSDKMsgSetHandler There were total of 2 requests processed 20070329.205212 D 4984 MsgSetHandler Executing Requests took 0.016 seconds 20070329.205212 D 4984 MsgSetHandler Creating Responses took 0.000 seconds 20070329.205212 D 4984 MsgSetHandler Response is 988 characters long 20070329.205212 D 4984 MsgSetHandler Writing Responses took 0.000 seconds 20070329.205212 D 4984 MacroManager::DumpMacroMap Map contains no entries 20070329.205212 I 4984 MsgSetHandler Finished. 20070329.205212 I 4984 QBSDKProcessRequest Application named 'FLEXquarters QODBC' finishing requests (process 2220), ret = 0. 20070329.205212 D 2220 RequestProcessor Finished processing requests, no errors. 20070329.205212 D 2220 RequestProcessor Processing requests took 0.126 seconds. 20070329.210128 D 2220 RequestProcessor During this session processed 1 request. 20070329.210128 I 2220 RequestProcessor "EndSession" has not been called. 20070329.210128 D 2220 RequestProcessor End Session finished OK. 20070329.210128 I 2220 RequestProcessor "CloseConnection" has not been called.
Message Configuration option 'Ole Automation Procedures' changed from 0 to 1. Run the RECONFIGURE statement to install.
Message Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
|
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2007-03-30 12:28:38 |
Sorry, I should have spotted this earier, QuickBooks 2003 isn't supported for use with SQL Server using DCOM.
Please Note: Effective April 30, 2006, in accordance with Intuit's QuickBooks Sunset Policy, QODBC is no longer actively supported on QuickBooks 2003 (or earlier) and QuickBooks Enterprise Solutions Version 2.0 & 3.0. |
|
|
|
|
Posted : 2007-03-30 12:37:43 |
what about the remote method? will that work? |
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2007-03-30 13:01:23 |
Sure, you can give it a try, but either way, we no longer support QuickBooks 2003. Actually the real problem is the age of the requestor in QuickBooks 2003. You can try switching to the QuickBooks 2004 style requestor. Its installer can be downloaded at: http://www.qodbc.com/docs/support/QBXMLRP2Installer.zip |
|
|
|
|
Posted : 2007-03-31 01:12:41 |
Hi Tom, Thanks for all the help. It does work with the remote connector. Hopefully this post will help those with old versions of QB :-) |
|
|
|
|
Posted : 2007-05-06 03:04:17 |
Tom
I receive the same error when using QuickBooks Enterprise 6.0. I am using a linked server in MS SQL Server.
OLE DB provider "MSDASQL" for linked server "qodbc" returned message "[QODBC] Error". Msg 7330, Level 16, State 2, Procedure spGetCustomer, Line 13 Cannot fetch a row from OLE DB provider "MSDASQL" for linked server "qodbc".
Any thoughts as to what I'm doing wrong?
Thanks |
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2007-05-06 09:07:56 |
It may also be that Ole Automation Procedures Option is turned off in your SQL Server Surface Area Configuration.
To turn it on with a query, see: http://msdn2.microsoft.com/en-gb/library/ms191188.aspx
which contains: sp_configure 'show advanced options', 1; GO RECONFIGURE; GO sp_configure 'Ole Automation Procedures', 1; GO RECONFIGURE; GO |
|
|
|