Re: Witango-Talk: FATAL EXCEPTIONS Thrown - Post-Upgrade .054to .065

[Ferr� A&T - Giorgio Tassistro]

Adam, I had some problem last year... sorry but if you use BLOB fields, Witango (only after .58 version) has a problem with pervasive 2000.sql, or better Pervasive has a problem with witango ;-) Witango use ODBC 3.0; interface that it'snt "compatible" with pervasive 2000.SQL that use 2.0 ...  Pervasive don't release a new version of ODBC for pervasive 2000 because Pervasive don't support SQL 2000 from 31 december 2003! (you see attachment)   Now,I think that the alternative solutions are 4:   1) You access with JDBC interface; but you must have witango development studio 5.5 and Java Engine (J2RE or J2EE) installed on server and JDBC driver for pervasive. 2) You upgrade pervasive with V8 version; V8 has 2.5 ODBC interface, but it run well with Witango. 3) You use .58 old version of Witango that is last version compatable  with pervasive. 4) You change dBase engine.   I hope that I help you Bye Regards   Giorgio   attachment for you: Pervasive.SQL 2000i Transition Support Now Effective As of September 2003, Pervasive.SQL 2000i entered the Transition Support phase of its lifecycle. What this means is that during the Transition Support phase: Limited research time will be spent on issues with this product. Phone and electronic support will be charged for any issue related to this product. No maintenance updates will be made. Exception: component-level fixes may be provided on an emergency basis for critical issues to customers with a Platinum or Managed support contract. To view the Pervasive Software Product Lifecycle policy, visit it online at http://www.pervasive.com/support/lifecycle.asp. Pervasive.SQL V8 has been an outstanding success and has enjoyed the fastest adoption rate of any Pervasive.SQL release! We do understand that not all users have had the opportunity to complete the migration to Pervasive.SQL V8. Pervasive is committed to continue providing our established high level of customer service to our partners still using Pervasive.SQL 2000i while completing the migration to Pervasive.SQL V8. To offset the costs associated with supporting multiple editions of the database engine, Pervasive raised the price of Pervasive.SQL 2000i on July 1, 2003. Pricing for Pervasive.SQL V8 will not change.  For more information on Pervasive.SQL V8, visit the Pervasive.SQL V8 home page at http://www.pervasive.com/psql/index.asp.   ----- Original Message ----- From: Adam Leisring To: [EMAIL PROTECTED] Sent: Monday, March 15, 2004 11:32 PM Subject: RE: Witango-Talk: FATAL EXCEPTIONS Thrown - Post-Upgrade .054to .065 We've just received this error on the server while executing the a SQL query through the wiTango engine:   "WiTango Priviledged Instruction" ? -See Attachment-   -----Original Message----- From: Adam Leisring [mailto:[EMAIL PROTECTED] Sent: Monday, March 15, 2004 3:47 PM To: >" < Cc: [EMAIL PROTECTED] Subject: Witango-Talk: FATAL EXCEPTIONS Thrown - Post-Upgrade .054 to .065 WiTango Community,   As a result of our upgrading from WiTango .054 to .065, we are experiencing major system issues. Below you can find descriptions of our environment and the resulting error(s).   Application Server:   Windows 2000 Advanced Server SP4 / IIS 5 / 1 Processor - IDE Drive   Witango 5.0.1.065 Just Upgraded From 5.0.1.054 - Standard License Example Error: (an actual error received) [ 2148] 2004-03-15 16:02:07 RUNTIME    FATAL    The "/acl/show_description.taf" application file, action "Get_Descriptions", caused an unrecoverable OS exception [ 2148] 2004-03-15 16:02:07 RUNTIME    FATAL    System Exception at 02b13ef9; Thread ID=1944; Code=EXCEPTION_ACCESS_VIOLATION Write: 02ad1000; [ 2148] 2004-03-15 16:02:07 RUNTIME    FATAL    System Exception at 02b13ef9; Thread ID=1944; Stack:, (insert hex pointers here) etc. The FATAL errors seem to revolve around ODBC connections, but even on non-database calls, the server seems much slower than 054.  A simple IF action takes longer than 054 did.   Witango 5.0.1.054 was working great for us (for over a year and a half).  However, due to the vulnerability discovery within 054, we'd like to move forward with the patched version.  Any advice would be greatly appreciated! Thanks, Adam Leisring Fischer Homes, Inc. Crestview Hills, KY 859-578-3718 ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf