|
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
|
|
| QBW32.EXE does not exit |
| Author |
Message |
|
|
| Posted : 2008-11-14 06:31:43 |
After upgrading to QB Enterprise 9, whenever I run a query using QODBC, the QBW32.EXE process automatically starts up correctly, but it no longer exits after the query is run like it did in version 8. Could this cause any problems?
This is frustrating for me because when I run queries overnight, I use a batch file to run "dtexec" commands to query data, and when QuickBooks is opened through the scheduled task, it floods the event log with "HHCTRL" information messages (it did this in version 8 as well). Now, it continues to fill the event log until I manually go in and kill the QBW32.EXE process. Is there any way to fix this? |
|
|
|
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2008-11-14 16:47:55 |
| QODBC never exits after a query is run. The calling application must always close the connection for QODBC to release the connection to QuickBooks (QBW32.exe). Scheduled tasks also don't release connections until the actual service is closed. |
|
|
|
|
|
| Posted : 2008-11-15 04:24:08 |
| In this case, then, is there a way to force QODBC to release its connection so that it will behave like it did with Enterprise 8? It is pointless for us to leave the Quickbooks process running on the server all day when we only use it to run overnight queries. |
|
|
|
| Tom |
| |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2008-11-15 10:33:38 |
Repeat, QODBC v6, v7, v8 and v9 never exits after a query is run. The calling application must always close the connection for QODBC to release the connection to QuickBooks (QBW32.exe). Scheduled tasks also don't release connections until the actual service is closed.
Try closing/stoping the service that's running the scheduled tasks. |
|
|
|
|
|
| Posted : 2008-11-26 03:22:12 |
I have tried the following:
Open SQL Server Management Studio, run an Integration package that queries QuickBooks (QuickBooks will start automatically in the background), then close SQL MS completely. I can confirm that QBW32.EXE is then still running, and the service that accessed QB is no longer running. |
|
|
|
| Tom |
| |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2008-11-26 20:29:08 |
Repeat, the calling application must always close the connection. Terminating the calling application kills the application not the connection. When using MS SQL Server you need to link and unlink QODBC.
For example:
EXEC sp_addlinkedserver @server = N'QODBC', @srvproduct=N'QODBC', @provider=N'MSDASQL', @datasrc=N'QuickBooks Data', @provstr = 'ODBC;DSN=QuickBooks Data;DFQ=C:\Program Files\QODBC Driver for QuickBooks\sample04.qbw;SERVER=QODBC;UseDCOM=Y; OptimizerDBFolder=C:\Program Files\QODBC Driver for QuickBooks\Optimizer; OptimizerAllowDirtyReads=Y'
EXEC sp_dropserver @server = N'QODBC' |
|
|
|
|