Make sure you are running the latest version of the server (065). Double check that the application scope is successfully identified in the TAF that you use to cause the error, and that it is the same application scope that you are assigning application$defaulterrorfile in.
You might also try putting logic in your default error.htx file that identifies the application or domain and acts accordingly. Robert -----Original Message----- From: Kevin Quinn [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 10, 2004 11:14 AM To: [EMAIL PROTECTED] Subject: Witango-Talk: defaulterrorfile and applications Am I missing something? I thought that all I had to do to get a customized error message in my application was to add the DEFAULTERRORFILE line to the right section of my applications.ini file and restart the server. After I did that, there server was _still_ using the default error.htx file, so I renamed it and restarted. Now, _no_ error file is being processed in my application. Is there some trick to getting this to work? When I do a <@VAR defaulterrorfile scope=app>, I get back the correct path and file name; it's just not getting executed when an error happens in the app. Kevin. ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
