The description for Event ID ( 10 ) in Source ( Witango_Server_5.5 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [3196] System Exception at 77f486f7; Thread ID=3744; Code=EXCEPTION_ACCESS_VIOLATION Read: 02080151;.
Peter
----- Original Message ----- From: "Dory" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 10, 2004 5:30 PM
Subject: Re: Witango-Talk: application vars timing out
Although it is unfortunate you are running into this, I am glad someone else is!
I have noticed that on our devel and test servers, it worked properly at one point, and then one day just decided to start timing out application vars (at the same interval as the system variabletimeout is set to). At the same time, my applications.ini starts being ignored so our timeformats revert to what is set in the system settings.
Several days ago, we put our application into production to give it a dry run. Application vars seemed to work as expected and applications.ini was being read. Then yesterday, with no provoking, application vars started timing out and applications.ini appears to be ignored again. Exactly what happened on our devel and test servers.
In our Windows log we found a bunch of errors along this line:
09/11/2004 8:10:46 AM Witango_Server_5 Error (1) 10 N/A UWEB "The description for Event ID ( 10 ) in Source (Witango_Server_5 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [1776] The ""/ssam/support/../TCF/ssam_utilities.tcf"" application file, action ""get_security_info_h"", caused an unrecoverable OS exception."
I've checked the action specified in the error message and it is a very simple database query, no reaon for it to be causing any problems.
As as aside, I have attempted to discuss this with Witango support, but have been told that they can't replicate my problem and thus can't do much. Hopefully they are still researching.
On Wed, 10 Nov 2004 08:18:16 +0100, Peter Ternstr�m <[EMAIL PROTECTED]> wrote:
________________________________________________________________________Hello all,
we're having the exact same problem - application vars and objects stored in
application scope time out and our application seizes to work properly. This
is a major issue for us, since we are hosting about 140 communities on the
web and noone can log in. We have tried to solve this by checking if app
vars are existant upon login, but this ultimately (after a number of logins,
usually once every couple of days) causes a server crash caused by reloading
application vars and objects stored in application scope discussed in other
threads of witango talk.
In fact, this is such a big problem for us, that we are looking for other
program languages for our application. The program language and application
server HAS TO WORK ACCORDING TO THE MANUAL. Otherwise our developers have
guess what functionality witango really supports, and all time to try to
build an app "by the book" is lost.
We would really like some input from you guys and with on this issue. We are
strung in a situation where at least one of us has to keep an eye on the
server and reload app vars if necessary- 24/7. Maybe it is a configuration
problem on our side? We only run one application, thus have not configured
other applications in applications.ini than "default". (Yes, we have tried
to configure another application, but still same result - loss of app vars).
Is anyone out there using application vars at all? Do you have the same problem? Is there a solution?
We are running Win 2003, Apache 2.049, SQL 7 (on separate server), and Witango 5.5.
Grateful for all input! Peter
----- Original Message ----- From: "Dory" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 26, 2004 12:41 AM Subject: Witango-Talk: application vars timing out
> We are experiencing 2 problems: > > 1. It appears that our application variables are timing out after the > system variabletimeout period. On page 349 of the Witango 5 > Programmer's Guide.pdf, it says that application variables NEVER time > out, yet ours do. I tried to resolve this by setting the > variabletimeout trigger which on page 485 of the same document says > that we can set that var in the application scope. When I try this I > get this error, "You may not set the configuration variable > (variabletimeouttrigger) in the (application) scope". > > The document says I am able to set this, yet I am not able to. Is > there a way I can set this var in the application scope? How do I stop > my application vars from timing out rather than just setting the > system variabletimeout to a really huge number? > > > 2. The timeformat and timestampformat specified in our > applications.ini file is being ignored. The system settings are used > for these values instead of our application specific ones. I am not > sure if this is related to problem 1 or not. How do I make Witango pay > attention to the timeformat and timestamp format in the > applications.ini file? (yes the Witango server has been restarted) > > We are running Witango Application Server (Standard Edition Upgrade) > 5.0.1.065 > > Thanks for any tips or information you can provide. > ________________________________________________________________________ > 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
