The quick answer is yes, this can/does happen. Likely an issue in the ODBC connection routine, but I'm not positive. If you are not running 065 yet, get that, it's much better. I am hopeful that 5.5 will be better or at least handle the problem better.
I'm not positive that Witango is 100% to blame. It could be an IP packet issue - loss or corruption on the network - or something in the ODBC. I have found that running the very latest ODBC drivers (MDAC 2.8) helped as well. For reference, I see this issue about once every 2-3 million SQL queries, by my estimation. Sometimes I'll go a whole month (10's of millions of queries) without an occurrence. Oh, and load is a factor. Robert -----Original Message----- From: Jason Pamental [mailto:[EMAIL PROTECTED] Sent: Friday, October 15, 2004 10:15 AM To: [EMAIL PROTECTED] Subject: Witango-Talk: Witango 5 / SQL Server 7 Hey everyone- Anyone out there using Witango 5 connecting to SQL Server 7? One of our clients' environment is Windows 2000/SQL Server 7/IIS/Witango 5, and we're still having odd issues with threads getting stuck seemingly on queries (different ones, not always the same) and then hanging the Witango service. Since it's lots of different files, even ones that I've rebuilt in Witango 5, I'm wondering if it's an ODBC issue. Anyone out there using this combination (ODBC Driver verison 3.70.x)? Windows and SQL Server both have the latest service packs (issue was there before and after those updates to SP4 on both). Thanks, Jason ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
