Information Advisory Group

Unfortunately you haven't said what version and year of QuickBooks you are using or QODBC version and build number?

Have you recently updated either QuickBooks or QODBC or applied a QuickBooks update patch? You should also check that QuickBooks ins't already open when you run the process. I would imagine the process requires unattended mode access to call each company file.

Thanks for the response!  I am a new programmer working on the custom application.  As far as I know the following has not changed since the custom application was implemented.  The QODBC Pro Read/Write 2005 version is 5.00.00.085.   The databases we are connecting to are using QuickBooks Enterprise Solutions version 5.0.  Also, the version number (when inside the QuickBooks' update screen) is v.15.0.4007.0.

A few more details that might help troubleshooting... 

I was going through your website's troubleshooting steps and discovered that the QuickBooks' Automatic Updates were turned on.  I cannot tell you if this setting has always been this way or recently changed. To mine and the development team leader's knowledge, in the past few years these settings have not been accessed by the users.  That being said, this setting hasn't been changed by the development team. 

Only within the past 6 weeks we have noticed the process intermittently dies.  No code in the custom application has changed.  Sometimes, there is a  "Had To Kill QBW32.EXE " message in our application log, which indicates a possible database connectivity loss?  Sometimes, there are no errors and the application just stops.  When we remotely log into the computer (Win_XP SP2) that runs the application nightly, we see the error message "Run-time error "-2147220452 (8004041c):  An internal QuickBooks error occurred while trying to access the QuickBooks company data file."  When either of the fore mentioned situations occur we reboot the computer and manually run the application that gets/writes data to QuickBooks/SQL databases and may continue to receive the error message or may not.

Also, within the past 2 months we have added new clients' QB databases to the process (without code changes).  Bringing our total database count to 15.  No one accesses any databases during the scheduled procedure. 

We have a 10-user license.

We actually have 3 scheduled tasks to run our custom application processes, one to update our SQL database to flag which records to export to QB, one to actually export invoices into QB, and one to export payments from QB to SQL.  We have eliminated the theory that these tasks are overlapping, because the "Had To Kill QBW32.EXE" message or drop in application logging occurs long before the next task begins or if it is the last task, kills occur hours before users access the QB files. 

I hope that this is helpful.  If you need any further explanation or would like to see a snippet of our log files, please let me know.  We are trying to get this resolved as quickly as possible as to the intervals between failures is increasing dramatically.

Thanks again!

Melissa Knight

Senior Programmer

Exactly do you mean by resolved on site?  Do I need to contact your support directly?  What is the contact information I should use?  Is there a charge for this support?  Is there a ticket number I can reference or is this forum sufficient?

I appreciate your prompt responses.  If this is something we can handle tomorrow I would be grateful, but will understand if it needs to wait until Monday.  I do request that if the handlings of this situation is on Monday that it occur as early as possible.  Let me know when to be available and how to proceed and I will do everything I can.

Thanks again!

Melissa Knight

Senior Programmer

On site means that this something that must be resolved on site on your network and the applications you are using. This isn't something we can reproduce here using QODBC. We currently do not offer any on-site support other than telephone callback, see: QODBC Callback Telephone Support.

My guess your copy of QuickBooks has been updated or a company file was updated from another workstation, or is is at a different level to the other company files. You shoud check whether the internal QuickBooks error occurred while trying to access a particluar company data file and the amount of delay you allow between disconnecting and connecting each company file.  

We also changed the way unattended mode works in QODBC v6.00.00.148 due to changes by Intuit where we added an Advanced tab in QODBC Setup with new defaults for Integrated Application Authorization popup settings for USA QuickBooks 2005 and QuickBooks 2006 users. (See How do I setup QODBC to auto-login into QuickBooks and start it if it's not running?  for what we do now).