Hello Razzak! Long time no talk.
For customer support and Razzak, i knew about this issue however, we have
been running fine for many months and just all of a sudden in the past week
or so have we had problems so i dont think this is the issue.
any other ideas out there?
----- Original Message -----
From: "A. Razzak Memon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, June 03, 2004 6:27 PM
Subject: Re: Witango-Talk: server issues
In addition to the Oterro 3.0 features, enhancements and bug-fixes listed
below, the following two items have
also been taken care of since May 21, 2004 in upcoming Oterro 3.0 Update 1
(currently under private beta).
01. VB.NET: Close method on ODBCDataReader (in System.Data.ODBC) functions
correctly.
Previously the Close method would throw intermittent exception
errors dependant on memory usage.
02. More compatibility with Witango Application Server (Build: 5.0.1.065)
Multi-Threading logic.
Thanks to Chuck Lockwood, Bill Downall, Dave Shelley and Steve Sweeney for
their professional and
collaborative efforts, including the needed stress test as well as managing
all tests/logs for our
development team.
The official release of Oterro 3.0 (update 1) will be announced shortly.
http://www.oterro.com
Very Best R:egards,
Razzak.
At 09:49 AM 6/4/2004 +1000, you wrote:
>>We are on windows 2003 server using witango 5.0.1.065, oterro (r:base)
>>2.6.00.03 and IIS.
>
>The 065 server uses a ODBC 3.x interface and the old Oterro driver will
>crash the odbc driver manager which will drag down the witango process.
> When we upgraded to the ODBC 3.x standard interface in Witango Servers
>5.0.1.062 (ODBC 3 specs were published in 1996/7) we did not anticipate
>that Pervasive's ODBC driver and R:Base's Oterro were still using an
>ODBC 2 interface. This caused quite a few issues with Oterro and the
>Pervasive SQL ODBC driver crashing the ODBC driver manager which gets
>loaded into the Witango Server's memory space. ODBC drivers that had
>problems with the ODBC 3 interface. Try using
>Oterro 3 and see if it stabilises your application.
>
>An extract from the Oterro 3.0 What's New document:
>
>. Countless efforts were made between the R:BASE Technologies'
>Development Team
>and users of R:Tango 5.0, when the updated version of Witango Server,
>bundled with
>R:Tango 5 (R:BASE 6.5++, Oterro 2.6, Witango Server, Witango
>Development Studio),
>introduced ODBC 3.0 features in their build 5.0.1.062.
>. On March 10, 2004, an official bug along with supported sample and
>log files was
>submitted in relation to ODBC 3.0 compliant SQL_MAX_ROWS for both
>SQLFetch and
>SQLExtendedFetch functions used with Witango Server (Build: 5.0.1.065).
>The bug
>was fixed and the pre-release version of Oterro 3.0 was sent to that
>beta tester.
>. On March 17, 2004, an official bug along with supportive details and
>samples was
>submitted in relation to using CALL(Proc) command using with Oterro 3.0
>and Witango
>Server. The bug was fixed and the pre-release version of Oterro 3.0 was
>sent to that
>beta tester.
>
>Oterro 3.0 will be available as a "Step-Up" for all existing registered
>users of Oterro 2.6 and as an
>"Upgrade" for all other versions of Oterro. All subsequent in-line
>patches will be available as FREE
>updates to all registered 3.0 users. For complete details, licensing
>and upgrade prices, please
>contact RBTI sales team at 1+724.733.0053 or mailto:[EMAIL PROTECTED]
>
>Acknowledgment: R:BASE Technologies and its Dream Team would like to
>thank all those who
>have been an integral part of making Oterro 3.0, especially those who
>have been involved in last
>three weeks to help us fine tune and test all the features implemented
>for .NET and Witango
>Server (Build: 5.0.1.065) used with R:Tango 5.0.
>
>On 04/06/2004, at 1:57 AM, Alan Wolfe wrote:
>
>>over the past week and a half for some reason witango and/or IIS has
>>become
>>really unstable, and we've had to restart witango a handful of times
>>per day
>>because it stopped responding. It seems too that the server is less
>>responsive than it used to be.
>>
>>the hard drive was fairly fragmented so we defragged and that helped a
>>little with responsiveness but it's still not like it used to be and
>>still
>>unstable.
>>
>>in the witango log, about half the time we have these crashes, theres a
>>message about an expired user right before the crash, as the last
>>entry in
>>the log file:
>>[Expired] Variables for key [EMAIL PROTECTED]
>>
>>not sure if thats triggering the crashes or coincidence.
>>
>>also in the witango events log we have messages like this peppered
>>here and
>>there but have had these all along so not sure if it's related:
>>
>>[ 3352] 2004-06-03 08:19:26 RUNTIME FATAL The "" application
>>file,
>>action "NULL", caused an unrecoverable OS exception
>>[ 3352] 2004-06-03 08:19:26 RUNTIME FATAL System Exception at
>>0043e42a; Thread ID=3428; Code=EXCEPTION_ACCESS_VIOLATION Read:
>>00000118;
>>[ 3352] 2004-06-03 08:19:26 RUNTIME FATAL System Exception at
>>0043e42a; Thread ID=3428; Stack: 00000000 00e5f4a0 0047de18 00e5f6e4
>>0041b788 00e5f500 00e5f540 00e5f554 00e5f53c 00e5f700 00e5f530 00a0d2f0
>>00a6e830 00e5f534 00000004 77f89570 ffffffff 00000000 77bbbb26 00360000
>>00a6bf78 00000002 00000020 0000f544 00000000 00e5f2f4 77bbbb70 00a6e5e8
>>77f45a34 00000010 ff00ffff 00360000 00e5f310 00360000 00e5f588 77f45a34
>>77f89570 00e5f5f8 00000000 77f47c00 009e1318 77f46700 00360700 005749f4
>>00000000 00000000 00000000 77bbbb00 00575040 00a6e8cc 00a6bf78 00a6bf78
>>00000000 00000010 77bb0000 00000001 00a6bf79 00000002 00000000 00e5f558
>>00000000 00e5f5f0 77bc4d50 77ba20f8 ffffffff 77bbbe90 00000020 00000000
>>00000002 00000000 00e5f678 00408b42 00000000 00a6e2d8 00e5f5fc 00a6e838
>>00408881 00e5f678 00a6e2d8 00360000 00e5f678 00000004 00013ed5 00e5f544
>>00a6e2d8 00e5f630 77f45a34 77f89458 ffffff00 77f467f9 77bbb9be 00360000
>>00000000 00000004 00000000 00e5f6d8 0000000e 004538a1 00a6e2d0 00a6bf78
>>00e5f724 00000020 0000f64c 00360000 00e5f430 77ba20c0 00e5f6a8 77f45a34
>>77f89570 ffffffff 77f473f3 77bbbb26 00360000 00000000 00000011 00000000
>>00e5f6b8 00000000 00a6e8cc 77bbbb70 77bbbe90 00a6e8cc 00000011 00a6e8cc
>>00000000 00e5f600 00a6c538 005749f4
>>
>>We havent changed any witango code or software on the machine, this is
>>coming just out of the blue it seems.
>>
>>anyone have any idea what might cause this?
>>
>>We are on windows 2003 server using witango 5.0.1.065, oterro (r:base)
>>2.6.00.03 and IIS.
>>
>>Thank you for any help!
>>
>>_______________________________________________________________________ _
>>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
