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
|
|
Issues with initial install... |
Author |
Message |
Ben |
|
Group | : Members |
Posts | : 1 |
Joined | : 2007-09-28 |
|
Profile |
|
Posted : 2007-09-28 05:07:52 |
I have just upgraded to v8 from v7, in the hopes that it will fix the issues I am having. When I open my web page and launch my query, it appears to be working, but after an hour the page refreshes with 'Server cannot be found'. When the application is done parsing the QB database, it *should* prompt to save a CSV file of the queried data. Here is what I have done so far to troubleshoot:
- VBDemo runs successfully with the query that I am running from my web page
- I am not seeing any errors in the QODBC message log
- There are no errors in the eventviewer or the SDK log
- The qbcust.asp runs successfully
- the testdcom.asp runs successfully - there is an Error: ActiveX component can't create object for xerces-com.dll, but Matt told me that should not create any issues
Any ideas? I am at my wit's end - SAVE ME TOM!!!
Thanks for the help.
Ben |
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2007-09-28 09:21:32 |
After an hour the page refreshes with 'Server cannot be found'? What refreshed the page??? Sounds like the connection session to the server was dropped to me. This is a IIS idle connection timeout issue. You really can't expect a session with the server to be forever. |
|
|
|
|