Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1565
  • Last Modified:

ODBC connection problems

I am trying to connect my QuickBooks DB to SalesForce using the Flexquarters QODBC driver and the Jitterbit dataloader.  I have verified that QODBC connects to QB OK but when I try to connect Jitterbit to the driver I get this error message.  QB is running on the desktop:

Failed to test the connection.

[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed

Details:
Unable to connect to database using DSN SERVER=192.168.1.18;DRIVER=QODBC Driver for QuickBooks;DATABASE=QuickBooksData;UID=;PWD=<REMOVED>;!


SQL Errors:
(0) SQL Error! SQLSTATE = IM006 Native err = 0 msg = [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed

(1) SQL Error! SQLSTATE = IM006 Native err = 0 msg = [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed

(2) SQL Error! SQLSTATE = 00000 Native err = 10041 msg = [QODBC] QB Begin Session Failed. Error = 80040408, Could not start QuickBooks.


(3) SQL Error! SQLSTATE = 00000 Native err = 10041 msg = [QODBC] QB Begin Session Failed. Error = 80040408, Could not start QuickBooks.




Please post the stack trace (click the button below) to the Jitterbit Support Forum.

Client version: 5.0.3.8
Server version: 5.0.3.8
Client platform: Windows 7 - Java 1.7.0_07
Server platform: Windows 7 Professional, 64-bit 6.1 (No Service Pack Detected) Build 7600
CPU: GenuineIntel x86 Intel(R) Core(TM)2 Quad CPU    Q9650  @ 3.00GHz - Intel64 Family 6 Model 23 Stepping 10, 4 cores total.
RAM: -2 GB in use, 9.319 GB available, 15 GB total.
Swap: 0.2376 GB in use, 1.774 GB available, 2 GB total.
Disk (where Jitterbit is installed): 152.4 GB in use, 86.07 GB available, 238.5 GB total.


org.jitterbit.integration.client.server.IntegrationServerException: [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed

Details:
Unable to connect to database using DSN SERVER=192.168.1.18;DRIVER=QODBC Driver for QuickBooks;DATABASE=QuickBooksData;UID=;PWD=<REMOVED>;!


SQL Errors:
(0) SQL Error! SQLSTATE = IM006 Native err = 0 msg = [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed

(1) SQL Error! SQLSTATE = IM006 Native err = 0 msg = [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed

(2) SQL Error! SQLSTATE = 00000 Native err = 10041 msg = [QODBC] QB Begin Session Failed. Error = 80040408, Could not start QuickBooks.


(3) SQL Error! SQLSTATE = 00000 Native err = 10041 msg = [QODBC] QB Begin Session Failed. Error = 80040408, Could not start QuickBooks.



      at org.jitterbit.integration.client.server.webservice.WebServiceConfiguration.convertToIntegrationServerException(WebServiceConfiguration.java:205)
      at org.jitterbit.integration.client.server.webservice.WebServiceServerCall.convert(WebServiceServerCall.java:49)
      at org.jitterbit.integration.server.implementation.webservice.interchange.connection.impl.ConnectionTesterWsImpl.testDatabase(ConnectionTesterWsImpl.java:198)
      at org.jitterbit.integration.client.datalocation.connection.DatabaseConnectionTester$TestSourceJob.makeServerCall(DatabaseConnectionTester.java:251)
      at org.jitterbit.integration.client.datalocation.connection.ConnectionUiJob.runImpl(ConnectionUiJob.java:69)
      at org.jitterbit.application.ui.job.UiJob$2.run(UiJob.java:514)
      at org.jitterbit.application.worker.DefaultApplicationWorker$RunnableWrapper.run(DefaultApplicationWorker.java:202)
      at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
      at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
      at java.util.concurrent.FutureTask.run(Unknown Source)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
      at java.lang.Thread.run(Unknown Source)
Caused by: [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed

Details:
Unable to connect to database using DSN SERVER=192.168.1.18;DRIVER=QODBC Driver for QuickBooks;DATABASE=QuickBooksData;UID=;PWD=<REMOVED>;!


SQL Errors:
(0) SQL Error! SQLSTATE = IM006 Native err = 0 msg = [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed

(1) SQL Error! SQLSTATE = IM006 Native err = 0 msg = [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed

(2) SQL Error! SQLSTATE = 00000 Native err = 10041 msg = [QODBC] QB Begin Session Failed. Error = 80040408, Could not start QuickBooks.


(3) SQL Error! SQLSTATE = 00000 Native err = 10041 msg = [QODBC] QB Begin Session Failed. Error = 80040408, Could not start QuickBooks.



      at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:223)
      at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:130)
      at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
      at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
      at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
      at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
      at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
      at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
      at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
      at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
      at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
      at javax.xml.parsers.SAXParser.parse(Unknown Source)
      at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
      at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:695)
      at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
      at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:807)
      at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
      at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
      at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
      at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
      at org.apache.axis.client.AxisClient.invokeTransport(AxisClient.java:150)
      at org.apache.axis.client.AxisClient.invoke(AxisClient.java:289)
      at org.apache.axis.client.Call.invokeEngine(Call.java:2838)
      at org.apache.axis.client.Call.invoke(Call.java:2824)
      at org.apache.axis.client.Call.invoke(Call.java:2501)
      at org.apache.axis.client.Call.invoke(Call.java:2424)
      at org.apache.axis.client.Call.invoke(Call.java:1835)
      at org.jitterbit.integration.server.implementation.webservice.interchange.connection.client.Konga_test_connectionSoapBindingStub.testDatabaseConnection(Konga_test_connectionSoapBindingStub.java:253)
      at org.jitterbit.integration.server.implementation.webservice.interchange.connection.impl.ConnectionTesterWsImpl.testDatabaseSource(ConnectionTesterWsImpl.java:171)
      at org.jitterbit.integration.server.implementation.webservice.interchange.connection.impl.ConnectionTesterWsImpl.testOdbcSource(ConnectionTesterWsImpl.java:211)
      at org.jitterbit.integration.server.implementation.webservice.interchange.connection.impl.ConnectionTesterWsImpl.testDatabase(ConnectionTesterWsImpl.java:195)
      ... 10 more



Any ideas please?

Thanks.
0
Mike London
Asked:
Mike London
1 Solution
 
lcohanDatabase AnalystCommented:
Did you posted the message as the error is suggesting to the Jitterbit Support forum?
"Please post the stack trace (click the button below) to the Jitterbit Support Forum."

I would also look into updating my OS to SP 1 as ODBC drivers ties back to the OS and on that computer you seem to have "Server platform: Windows 7 Professional, 64-bit 6.1 (No Service Pack Detected) Build 7600" if I'm not mistaken.
0
 
Mike LondonAuthor Commented:
I did as you suggested thanks and in the end I had feedback from the vendors of the QOBDC connector who helped me with the configs.  Then it all worked.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now