| QBCust.asp Returns Error 8004041c |
| Author |
Message |
|
|
| Posted : 2006-06-13 05:31:24 |
I installed and tested QODBC on my development machine without issue, but installing it on a client's server is giving me some trouble. Everything seems to be working okay EXCEPT qbcust.asp. I've:
- Verified that all of the steps in the web installation page have been completed.
- Tested the connection from the DSN setup dialog.
- Tested the connection from the VB Demo app, using the same connection string as qbcust.asp.
- Made sure that the QB client had the company file open under the same (Admin) user account.
- Run the DCOM test page successfully.
That said, qbcust.asp throws the following error message at the point where it tries to open the ODBC connection:
"Begin Session Failed. Error = 8004041c, An internal QuickBooks error occurred while trying to access the QuickBooks company data file."
I'm pretty much out of ideas at this point, any help is appreciated. |
|
|
|
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-06-13 08:39:31 |
|
|
|
|
|
| Posted : 2006-06-13 12:48:49 |
Okay, I did everything necessary to get auto-login working, now I'm getting a new error. :)
The error returned from ASP is:
Error = 80040424, QuickBooks did not finish its initialization. Please try again later.
I found the following in the SDK log:
========= Started Connection =========
Request Processor, QBXMLRP2 v4.0
Connection opened by app named 'FLEXquarters QODBC'
The file does not contain an Authenticode signature.
An internal error occured while looking for a running instance of QuickBooks. Cannot continue. hr = 80080005
Connection closed by app named 'FLEXquarters QODBC'
========= Ended Connection ==========
Callback not created: CoCreateInstance failed HRESULT=0x80040154
Callback not created: CoCreateInstance failed HRESULT=0x80040154
Callback not created: CoCreateInstance failed HRESULT=0x80040154
Hopefully that will provide some insight. |
|
|
|
| Tom |
| |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-06-13 13:59:29 |
| Sounds like your client has more than one version of QuickBooks on the server or is already using a QuickBooks session in a Terminal Server or Citrix session. |
|
|
|
|
|
| Posted : 2006-06-14 03:10:07 |
I had that thought myself, but neither was the case.
Today, without changing anything, we're back to error 8004041c. Color me confused.
|
|
|
|
| Tom |
| |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-06-14 08:15:35 |
Does the VB Demo connection using the SYSTEM DSN still work? Does it open QuickBooks in background mode and the company file if QuickBooks isn't running? If yes, then check your Windows event log for what the true "Windows" error is?
I also need to know what O/S your client's server is running? |
|
|
|
|
|
| Posted : 2006-06-14 13:26:38 |
Yes, the VB Demo connection works using the System DSN. I had task manager up while it was running and QBW32.EXE and the QODBC DCOM process were running and were using the bulk of the CPU resources as the query executed. I closed the demo app and killed both of the processes in TM, then ran QBCust.asp to see what happened. Both processes started, but they only made use of the CPU for a second or two.
The OS is Windows 2003 Server. |
|
|
|
