| Modal Window causes qbw32.exe to hang in background when opened with QODBC |
| Author |
Message |
| Mat |
| |
| Group | : Members |
| Posts | : 7 |
| Joined | : 2006-06-16 |
|
| Profile |
|
| Posted : 2006-06-16 01:41:39 |
I'm running php scripts on a Win 2k server to access my company file, and export certain tables to csv files. I've checked the option to allow QODBC to login automatically, and I've unchecked the Launch Quickbooks UI option. Frequently the scripts will error with: "Error = 80040414, A modal dialog box is showing in the QuickBooks user interface...." and while my php script will stop running, an instance of qbw32.exe will continue running and the scripts will error with the same message until I manually kill the qbw32.exe process.
I have my scripts setup to run as scheduled tasks from a user that is always logged into the server. There are other users that log into quickbooks but do not use the QODBC driver. I've tried turning off all the alerts or pop-up messages for the QODBC quickbooks user, however I'm still running into this modal dialog box error, even when no other user is logged into the server. Am I missing some option to make the qbw32.exe process end when my script errors out?
I do not want to leave the QODBC user logged into quickbooks continuously, because the other users occasionally have to switch to single-user mode and I would prefer this to be as automated as possible. |
|
|
|
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-06-16 09:59:45 |
The problem here is that the QuickBooks company file is being opened in both modal and non-modal modes at the same time, so if for example someone opens an invoice and your script then tries to create invoices, then you will get a "Error = 80040414, A modal dialog box is showing in the QuickBooks user interface...." which has nothing to do with alerts or pop-up messages. QuickBooks is simply saying that a modal connection is active for this part of QuickBooks and you need to wait.
Normally the other user would eventually close the Invoice modal screen allowing your script retries to be successful.
BTW: I believe that Intuit have made some errors in making a number of user interface (UI) operations in QuickBooks "modal" to Integrated Applications such as QODBC. |
|
|
|
| Mat |
| |
| Group | : Members |
| Posts | : 7 |
| Joined | : 2006-06-16 |
|
| Profile |
|
| Posted : 2006-06-17 00:34:10 |
| Is there a timeout setting in the driver that will close the qbw32.exe process after this error? I understand what you're saying about the modal and non-modal modes, but I'm still left with the fact that the qbw32.exe process isn't closed after the error is encountered, even if no other users are logged into the company file. |
|
|
|
| Tom |
| |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-06-17 09:56:37 |
| Normally the other user would eventually close the modal screen causing the error allowing the QODBC connection to keep on doing whatever it's doing. To close qbw32.exe the QODBC connection just needs to closed, or the script ended. |
|
|
|
| Mat |
| |
| Group | : Members |
| Posts | : 7 |
| Joined | : 2006-06-16 |
|
| Profile |
|
| Posted : 2006-06-19 23:56:39 |
That is the problem though. Even after the other users have all logged out, and my scripts have recorded the error message, and closed the QODBC connection and ended, the qbw32.exe process remains. Here is an example of how my script works if that helps explain the process, all pseudo-code:
Customer script starts
Call odbc connection to QODBC dsn
Determine if connection was successful or not
if not successful
record error message returned by qodbc driver
close odbc connection
end script with return 2
if successful
begin customer table export to csv file
close odbc connection
send file to users that need it
end script with return 0
I know that the not successful condition is being fulfilled because the error message is appended to the customer script error log, and the return code is recorded as 2 not 0. When the script is successful (which is most of the time), the csv file is created properly. I hope this makes the process a little more clearer, I'm just curious if I'm closing the script prematurely, or if there is something else causing that process to hang. When the error occurs, any repeat attempts by the script to run will cause it to give the modal window error until I manually kill the process. |
|
|
|
| Tom |
| |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-06-20 09:50:50 |
Sorry, I'm not to sure whether the other UI users are on the same server (Terminal Server Sessions) or on their own workstations? If you are only reading info out of the Customer table, then you shouldn't be getting modal errors. I only get modal errors if I try to create for example an invoice and have the invoice model pane running in QuickBooks on a invoice for the same customer.
I suggest you try to find out what modal pane is interferring here. Walk around all the users are see what they are doing in their QuickBooks session. The company file will also need to always be in Multi-User mode! If the company file is set to single user, then your script won't work. |
|
|
|
|
|
| Posted : 2006-07-01 01:31:09 |
I am having the same trouble, but am not getting modal error messages. It seems like when I am logged into the server where QODBC and our QB db live, then we don't have any problems...but when I'm not logged into it our script will run fine the first time, but QBW32.EXE remains open and no further scripts will run without erroring out (which also causes our sales/job management server app to lock up). The only way to fix it is to log into the server and kill the QBW32.EXE process. None of our QB users are getting any error messages, QBW32.EXE just won't close on it's own if I'm not logged into the server. Any help would be appreciated as our sales staff is getting ready to kill me if I can't get this fixed.
Thanks, |
|
| |
-Dillon S.
IT Supervisor
|
| | Top | |
|
|
| Tom |
| |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-07-01 09:21:20 |
| The server console (local session) on the server needs to be logged into always. The server can't be left at a login screen waiting for you to come along. Why?, because QuickBooks is an application .... not a "true" service. |
|
|
|
|
|
| Posted : 2006-07-01 15:12:50 |
We just upgraded from QB Pro 2005 to QB Enterprise 2006. When we were using Pro 2005 we did not have to stay logged into the server. We had no problems with QBW32.EXE staying active and hanging. Now that we have upgraded to Enterprise 2006 (and upgraded to QODBC Driver 6) we are having this problem. Having seen our scripts and our previous version of the QODBC driver work perfectly with QB Pro 2005, I have a hard time swallowing the "you have to stay logged into your server all the time" fix. If we did not have to stay logged into our server all the time before, then why now? Has something changed?
Please help. |
|
| |
-Dillon S.
IT Supervisor
|
| | Top | |
|
|
|
|
| Posted : 2006-07-07 00:22:51 |
Any additional help or ideas would be much appreciated.
Thanks in advance! |
|
| |
-Dillon S.
IT Supervisor
|
| | Top | |
|
|
| Tom |
| |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-07-07 08:30:13 |
| Intuit changed unattended access and the DBMS backend in QuickBooks 2006. In fact there have been ongoing issues even with R7. The server console (local session) on the server needs to be logged into always. Well at least try it to see if it resolves your issue? |
|
|
|
|
|
| Posted : 2006-07-07 08:54:20 |
That is definitely a bummer. Will definitely try it to see what kind of results we get. We appreciate the info and hopefully a way to bypass this issue will turn up sometime soon.
Thanks again for the update. |
|
| |
-Dillon S.
IT Supervisor
|
| | Top | |
|
|
