|
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
|
|
| Error 80040408 after upgrading from QuickBooks Pro 2005 to QuickBooks Pro 2008 |
| Author |
Message |
|
|
| Posted : 2008-05-30 05:51:33 |
Hello,
Our client upgraded from QuickBooks Pro 2005 to QuickBooks Pro 2008 and is now receiving the following error when attempting to use a 3rd party application (which uses the QODBC driver) to extract data from QuickBooks:
QODBC Error: QB Begin Session Failed. Error = 80040408, Could not start QuickBooks.
3rd Party Application's Error: Unable to create a connection to the database using driver: sun.jdbc.odbc.JdbcOdbcDriver and url: jdbc:odbc:QuickBooks Data:
This client is using QODBC v. 8.00.00.237 and QuickBooks is installed on a Windows XP Pro desktop with the 3rd party application. they have 2 QB "company files," however we only need to connect to one. Both company files are located on a shared folder located on another machine on the network. The 17 step approach did not work.
Thank you
|
|
|
|
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2008-05-30 08:13:41 |
| Did your client purchase a new QODBC v8 Server Edition CDKey Code for QuickBooks 2008? |
|
|
|
|
|
| Posted : 2008-05-31 01:14:38 |
| Yes, we purchased a new QODBC v8 CDKey Code for QuickBooks 2008 on our client’s behalf. However, we purchased them a single user license, not a per server license. Is a per server license required for this environment? If so, why? Thanks |
|
|
|
| Tom |
| |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2008-06-02 07:38:07 |
|
|
|
|
|
| Posted : 2008-06-11 07:02:17 |
Thanks for answering my question. To clarify the situation, I have 3 additional questions:
1) Is this a new requirement with version 8? We did not experience this error with version 7.
No, the QODBC Server Edition has always been required when using a Windows Service or an application calling a Windows Service.
2) We are an OEM for your QODBC product, for use with our ETL application. We deploy the QODBC product in the event that one of our clients needs to extract data from Quickbooks. Our ETL application is a Java application. Is the server edition of version 8 the only option we have with a Java application?
No, desktop applications don't require the QODBC Server Edition, but if I take same application and then get it to run using the Windows Scheduler (which runs as a Windows Service), then it requires the QODBC Server Edition. So it really depends how the application is used.
3) Will the server license give us the ability to run it as a windows service?
I think I've made it clear, the QODBC Server Edition is required for any application running as a Windows Service or calling a Windows Service like IIS, ColdFusion or MS SQL Server.
Thanks |
|
|
|
|
|
| Posted : 2008-06-13 07:47:02 |
Unfortunately, we feel this issue is still unresolved.
In your first response you indicated that using sun.jdbc.odbc.JdbcOdbcDriver requires the server version. We have not seen this in V7 of the QODBC driver. We currently have clients running fine with V7 of the QODBC driver and these clients are using the same application as those who are having issues with V8 of the QODBC driver.
In your second post you indicated that if we run as a windows service or call a windows service we will require the server version. Our application is not running as a windows service, it is running as a tray application in user space.
In summary, we feel this is unresolved. To reiterate, we are not running as a windows service, V7 of the driver continues to function for our existing clients, yet we still have the above reported error when trying to connect with the V8 version of the driver.
Any Insight is greatly appreciated. |
|
|
|
| Tom |
| |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2008-06-13 07:58:11 |
You haven't taken into consideration the differences between QuickBooks 2005 and QuickBooks 2008. We have also tightened and locked down rogue applications that were going around our licencing requirements in QODBC v8.
Try running your application as a non-System Tray application. |
|
|
|
|