The quick fix to the CGI error caused by the "Redirecting future diagnostic messages to..." warnings was to comment ERRFILE. This forces those messages to go to the "bit bucket" instead of the results page. Since all other messages also are lost, this is not the best solution, but will work for now. Thanks.
-----Original Message----- From: Aengus [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 04, 2007 9:58 AM To: Support for analog web log analyzer Subject: Re: [analog-help] Log Format on Windows Server Smith, Michael K <[EMAIL PROTECTED]> wrote: > After I moved LOGFORMAT from the forbidden list to allowed, the log > files were then processed and results output to a page. This is > strange, because I have no LOGFORMAT in my cfg files! Will leave it > so it works. > > Angus said the CGI error is an IIS issue, and was addressed in > previous posts, so I'll review them to find the resolution. I think you already discovered the resolution: http://lists.meer.net/pipermail/analog-help/2003-November/015863.html Aengus +----------------------------------------------------------------------- +- | TO UNSUBSCRIBE from this list: | http://lists.meer.net/mailman/listinfo/analog-help | | Analog Documentation: http://analog.cx/docs/Readme.html List | archives: http://www.analog.cx/docs/mailing.html#listarchives | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general +----------------------------------------------------------------------- +- +------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.meer.net/mailman/listinfo/analog-help | | Analog Documentation: http://analog.cx/docs/Readme.html | List archives: http://www.analog.cx/docs/mailing.html#listarchives | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general +------------------------------------------------------------------------
