On 11:23 AM 2/26/2003 or thereabouts, Brad wrote:
 >But when I click on List Archives from the WWW interface I get this message:
 >
 >The archive files could not be accessed, either because the list
 >does not have Web-accessible archives or because they are
 >being updated.

Looks like you're running IIS on Windows.

In the site management program (site.exe), click Advanced configuration.
Scroll all the way down, check the values of WWW_ARCHIVE_CGI
The value should be a URL like /cgi-bin/wa.exe, and the status should be
"Has been configured"
Check WWW_ARCHIVE_DIR
The value should be a path like c:\inetpub\wwwroot\archives, and hopefully
"Has been configured".
I would guess that these are ok, otherwise you wouldn't get any archive web
pages at all.

Next, you need to make a subdirectory under the IIS archives dir for each
list, the name being the same as the official list name.  If it's
LISTSRV-L, then that must be the subdirectory name.

Now for the fun part, making sure the directory and file permissions are
ok.  The IIS accounts, typically IUSR_[servername] and IWAM_[servername],
need at least RX (read + execute) permissions on the archives directory
tree and the "Notebook=" directory -- the path in the Notebook= line of the
list header where the messages are really stored -- so those pages can be
served by IIS.  The HTML pages in the IIS archive pages are just TOCs,
pointers to the Listserv files in the "Notebook=" directory; it would be
pointless to duplicate everything just for the web interface.

If you see the TOC in the web interface, and clicking on a link gives you
the error you mentioned, it is likely that the IIS accounts don't have the
necessary permissions on the "Notebook=" dir.

The account that the Listserv service is running under needs Modify and
Write on the IIS and (naturally) Listserv directories, so it can create and
change the HTML TOC files.  Most people run it under Local System, so
permissions are not a problem.  Security might be a problem, but not
permissions...

- George