Henning, I briefly investigated this a while back too. As far as I could work out, the message is hard-coded into the Witango plug-in (for IIS in my case). I came to the conclusion that I would not be able to automate this and wrote the script posted earlier -- which I forgot to mention, is fired by the Win2K Scheduled Task frequently.
Of course, what would be better would be to get a new version (hint, hint) that doesn't have the bug that causes this. From what I've seen in the Win2K Event Logs, the TAS dies (usually with a FATAL_EXCEPTION), ServerWatcher tries to restart it but the TAS service is still in the process of dying, so it cannot be restarted; ServerWatcher logs an error and doesn't try again. Jon -----Original Message----- From: Henning Sittler [mailto:[EMAIL PROTECTED]] Sent: 15 July 2002 21:24 To: Multiple recipients of list witango-talk Subject: RE: Witango-Talk: Restarting Tango Hmm, Thanks Jon. I'll use this to write a cron job too, but I'm still trying to find out what exactly generats that "Tango 2000 Could not connect to server." message displayed by the webserver when the Tango server is not running but a taf is requested. If I can hack that to trigger a script, then the cron need only be running as a backup protection, just in case! Henning Sittler www.inscriber.com -----Original Message----- From: Jon Grieve [mailto:[EMAIL PROTECTED]] Sent: Monday, July 15, 2002 4:18 PM To: Multiple recipients of list witango-talk Subject: RE: Witango-Talk: Restarting Tango ________________________________________________________________________ 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
