Wow, that is strange - the application.ini file shows a modified date of just a couple days ago - the day before my problem happened. And I'm sure I didn't modify it. I've changed the password and secured the config folder - but the server still can't load application scope variables. The application.ini file looks OK to me - how would I go about fixing the original problem?
(here's the application.ini file): [Applications] Config=For the Tango 2000 Configuration application Default=This application controls everything in the web root which is not part of another application. Demos=For the demos provided with Tango 2000 [Default] CUSTOMSCOPESWITCH=on EXTERNALSWITCH=on FILEDELETESWITCH=on FILEREADSWITCH=on FILEWRITESWITCH=on JAVASCRIPTSWITCH=on JAVASWITCH=on MAILSWITCH=on PASSTHROUGHSWITCH=on PATH="/" [Demos] CUSTOMSCOPESWITCH=on EXTERNALSWITCH=on FILEDELETESWITCH=on FILEREADSWITCH=on FILEWRITESWITCH=on JAVASCRIPTSWITCH=on JAVASWITCH=on MAILSWITCH=on PASSTHROUGHSWITCH=on PATH=/Tango2000/Demos [Config] CUSTOMSCOPESWITCH=on EXTERNALSWITCH=on FILEDELETESWITCH=on FILEREADSWITCH=on FILEWRITESWITCH=on JAVASCRIPTSWITCH=on JAVASWITCH=on MAILSWITCH=on MAILSWITCH=on PASSTHROUGHSWITCH=on PATH=/Tango2000/Config Ok, --Quick explain of the application.ini-- Witango application files belong to the application specified by the immediately dominating application path. For example, if there are two applications, "A" and "B", and the path to "A" is /foo/ (that is, the foo folder within the Web server document root) and the path of application "B" is foo/bar, the file foo/bar/example.taf belongs to application "B", not "A". The application.ini file is where these folder boundaries for each application are defined. -- ok, can you check the dates of the ini files in you configuration folder if they are todays, baring you haven't made changes and just viewed, then someone has. You might want to check/change your CONFIGPASSWD= (make a note of this) also, check that the APPCONFIGFILE= reflects where the applications.ini is locatated. Also under IIS you might want to stop the config.taf from being accessible from the net. Just trying to help here, there have been recent hacks against Tango/Witango servers Ben Johansen - http://www.pcforge.com Authorized Witango Reseller http://www.pcforge.com/WitangoGoodies.htm Latest downloads & List Archives @ http://www.witango.ws -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Dave Machin Sent: Wednesday, October 16, 2002 2:49 PM To: Multiple recipients of list witango-talk Subject: Re: Witango-Talk: Application Scope Variables Fail The ApplicationSwitch=ON - there's plenty of free hard drive space (20 GB free). We're not logging anything, and I've never made a change to applications.ini (not even sure what it's for). ----- Original Message ----- From: Ben Johansen To: Multiple recipients of list witango-talk Sent: Wednesday, October 16, 2002 2:34 PM Subject: RE: Witango-Talk: Application Scope Variables Fail Hi, What is the setting of APPLICATIONSWITCH= in you T4Server.ini or Witango.ini? It should be APPLICATIONSWITCH=on Is there a enough space left on the drive that Witango is running on? Are you logging? Is this file getting to big? Was there a recent change to the Applications.ini file? Ben Johansen - http://www.pcforge.com Authorized Witango Reseller http://www.pcforge.com/WitangoGoodies.htm Latest downloads & List Archives @ http://www.witango.ws -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Dave Machin Sent: Wednesday, October 16, 2002 11:05 AM To: Multiple recipients of list witango-talk Subject: Witango-Talk: Application Scope Variables Fail We've had a sudden occurrence on one of our webservers where we get the following error when trying to assign new application scope variables: Error An error occurred while processing your request: File: setvar2.taf Position: home_page Class: Internal Main Error Number: -624 The application scope is not defined. key_graph_title I stopped and started WiTango, IIS a couple times and it hasn't gone away. This page has been working fine for about two years. If I change the scope to 'user' it works fine. We did get an event on our event log saying that the WiTango service had stopped unexpectedly at about the time the error first appeared. We're running WiTango 2000 on Windows 2000SP3. Any idea? This is sort of worrying me. Dave Machin [EMAIL PROTECTED] ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
