Member Login

Username
Password
Forget Password
New Sign Up
Search Forum

Buy Support
Incidents

If you can't find your answer in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us private or confidential information:

Click Here
If you can't login and post questions or you are having trouble viewing forum posts:
Click Here
Callback
Support

If you live in USA, UK, Canada, Australia or New Zealand, you can leave us details on your question and request us to call you back and discuss them with you personally  (charges apply).

Click Here
 
Buy Support
Incidents
If you can't find your answer in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us private or confidential information:
Click Here

Forum : QODBC, QB Pro 2007, and TomcatSearch Forum

Forum Home > QODBC - ODBC Driver for QuickBooks > QODBC v7 Forum

 New Topic 
 
 Post Reply 
[1]  
 QODBC, QB Pro 2007, and Tomcat 
 Author   Message 
  Kevin 
  
 Group: Members 
 Posts: 9 
 Joined: 2006-09-24 
 Profile
 Posted : 2007-01-29 08:22:39

I upgraded to QB Pro 2007 a few days ago and a QODBC web application that was running reasonably well in QB Pro 2005 no longer works.  The QODBC that I'm running is a "07" serial number, having just been purchased in November so that's not the issue.

The identical code will work as a standalone Java application, but not when executed within Tomcat in a servlet as a response to a web request, which suggests that it's a configuration issue with Tomcat.  However it worked as is with QB 2005.  I have tried adding a resource to the context and a resource-ref to the web app even though these were not necessary for QB 2005, but it still fails.

The error in the log file is:
[QODBC] QB Begin Session Failed. Error = 80040408, Could not start QuickBooks.

What is the difference between QB 2005 and QB 2007 that would prevent QODBC from working in this circumstance?  More important, how do I get it to work? 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2007-01-29 13:19:56

The problem here is that you have upgraded to QuickBooks 2007. The error is saying that your servlet could not start QuickBooks. Hopefully it's just because unattended mode isn't working, see: After upgrading to QuickBooks 2006 or 2007, QODBC "auto-login" unattended mode no longer works? for the workaround.

 

  Top 
  Kevin 
  
 Group: Members 
 Posts: 9 
 Joined: 2006-09-24 
 Profile
 Posted : 2007-01-30 13:13:59
No luck.  The same message "Could not start QuickBooks." appears under all circumstances.  After following the directions in the last post, I tried with and without the QB UI running, in multi and single user mode, attempting to log in as Admin or a different user.  I tried copying the standalone program directly to the doGet() method of the servlet.  I tried a different company file altogether.  Nothing changes the server log output -- nothing can start QuickBooks.  But the standalone program with identical code has no problems connecting and retrieving data.
 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2007-01-30 13:44:31
Does VB Demo connect without QuickBooks running? Unattended mode must work first. If you can't get the DCOMs working try switching to the QODBC/iBiz Remote Connector setup on the server itself. 

  Top 
  Kevin 
  
 Group: Members 
 Posts: 9 
 Joined: 2006-09-24 
 Profile
 Posted : 2007-01-31 01:18:35
I uninstalled QB2007 and reinstalled QB2005 and continued getting the same connection error.  I uninstalled Tomcat 5.5.20 and went back to 5.0.28 thinking that I might not have tried connecting since updating to that version.  Same problem, and I'm sure I've never changed the Tomcat version on the deployment machine.  I may have to go back to QB2005 anyway since the first QODBC license I bought just in August is a version 06, unless there's a pretty cheap upgrade cost. 

The VB Demo connects fine without the QB UI.  I decided to add some logging messages and pass them to the response jsp, rather than having to go look at the Tomcat log file to see the system.out.println output.  After adding some log statements, which stored the messages in a vector and passed the containing class to the jsp for display ... the connection to QB2005 worked.  But this was the whole point behind upgrading to QB2007 -- sporadic connection failures.  In fact, on the deployment machine, it would only work when the QB UI was NOT running which severely limited the use of the QODBC program.  Which reminded me to try that.  It still fails when QB is open, regardless of the QB UI mode (single, multi), the configuration of the QODBC source (same as file, single, multi), or log in (same user as open UI or different).  I exited QB, and tried again ... successful connection.

I'm open to suggestion :)
 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2007-01-31 08:24:04
When a connection is made through a Windows service using the QODBC DCOMs, QuickBooks must not be running. Unattended mode will automatically start QuickBooks as either a background or foreground task depending on whether "Launch QuickBooks UI" is checked or not checked in the QODBC setup screen. This was changed since 2005 because many developers didn't like users getting to QuickBooks while their application was performing tasks and many run their servers not logged in. 

  Top 
  Kevin 
  
 Group: Members 
 Posts: 9 
 Joined: 2006-09-24 
 Profile
 Posted : 2007-01-31 23:06:28
Maybe there's a solution to the domain problem that I not thinking about.

We look up items on our primary vendor's website, which I'd like to strip and insert into QuickBooks automatically.  That part works fine as long as QuickBooks is closed.  I can view an item on the vendor's site, right-click and select "Export to QuickBooks" on an I.E. pop-up menu extension which sends the information to a servlet.  The short scenario is that QB responds with a status, but there's potentially more communication involved.  But we need QuickBooks open at the same time to continue the customer transaction -- entering an invoice to print for the customer.  Obviously, opening and closing QuickBooks isn't realistic.  The item must be defined before it can be added to a customer invoice.

I'd rather not have the added work of defining a web interface for all the QB actions that I might have to use during a customer transaction. 

  Top 
  Kevin 
  
 Group: Members 
 Posts: 9 
 Joined: 2006-09-24 
 Profile
 Posted : 2007-02-01 00:34:08
My application is not a "background" maintenance task that should be run when QB is closed.  In a retail environment, I want to look up an item on a vendor's website, strip the information, and automatically insert it into QB if it's not already there.  The item must be defined before an invoice can be generated for the customer standing there at the counter.  I don't want to keep the customer waiting while manually defining the item and typing in cost information.

Although a complete QODBC web-based application to the QB file, including entering customers and invoices, would be nice, I was hoping to implement a piece at a time.  Shouldn't this be a configurable selection?  Is there any workaround? 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2007-02-01 08:15:42
As stated before, your servlet can launch the QuickBooks UI (depending on whether "Launch QuickBooks UI" is checked or not checked in the QODBC setup screen) so it can be used by a user on the same machine if desired. Simply don't close the connection until it's time to do so. Another approach is to have desktop application which can run the same time as QuickBooks. 

  Top 
 New Topic 
 
 Post Reply 
[1]  

Jump to