Other than that, can I get someone from Witango to tell me what's up with the variableTimeout in domain scope? Straight from the pdf on the witango website...
...
To change the expiry timeout period for domain variables only, assign the desired value to variableTimeout in domain scope. For example, to specify that domain scope variables never expire, make the following assignment:
<@ASSIGN NAME=variableTimeout SCOPE=domain VALUE=0>
Setting this variable with user scope sets the expiry timeout for the current user, overriding the value in the system scope.
...
The programmers guide is using the variableTimeout in domain scope as an example. ??? I'm not necessarily complaining... if domain variables never timeout... that's great with me. I'm just making sure they don't timeout.
Thanks,
David Green [EMAIL PROTECTED]
Robert Shubert wrote:
I don't recall this being a change in 065.
-----Original Message-----
From: Stefan Gonick [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 10, 2004 1:20 PM
To: [EMAIL PROTECTED]
Subject: Re: Witango-Talk: Client/Plug-in Error
I'm pretty sure that you can no longer assign variableTimeout in the domain scope. It's automatically set to not expire.
Stefan
At 01:08 PM 3/10/2004, you wrote:
Thanks Alan,
Yes, I did back them all up. Now it's even more weird... I guess I started and stopped the service or the server itself enough, because
now
it's working. But it's still not running right...
Why can I not assign the domain$variableTimeout to 0? Here's the
error:
File: startup.taf Position: assignDomainVariables Class: Internal Main Error Number: -609
You may not set the configuration variable (variableTimeout) in the (domain) scope.
Consult the documentation for a list of valid scopes that can be used
with
this variable.
Anyone?
Thanks,
David Green [EMAIL PROTECTED]
Alan Wolfe wrote:
Not sure if this is the problem but did you back up your .ini's before
the
upgrade? The upgrade overwrites them with the defaults. ----- Original Message ----- From: "David Green"
<[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]> Sent: Wednesday, March 10, 2004 9:44 AM Subject: Witango-Talk: Client/Plug-in Error
Hi All,
I just upgraded our test server to 65. Now I'm running into this
error...
Client/Plug-in Error Unable to initialize the client's environment. Check the client configuration file format and permissions.
Nothing else has changed on this box. Here is what my clients.ini
looks
like. [Witango Client Definitions] wiis.dll=
[wiis.dll] WITANGO_SERVER=127.0.0.1,18100 ERROR_HTML=C:\\Program
Files\\Witango\\Server\\MiscFiles\\clienterror.html
REPORTCLIENTERROR=TRUE
Is it wrong? No permissions have changed whatsoever.
Any ideas?
Thanks,
David Green [EMAIL PROTECTED] _____________________________________________________________________
___
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
========================================================
Database WebWorks: Dynamic web sites through database integration
http://www.DatabaseWebWorks.com
________________________________________________________________________ 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
