Brian,

The only time I have come across a virtual disk slot emulation error
is when the following has occurred:

* check that the header refers to a valid location for the archives,
problems here range from simple mis-spelling to your sys admin
moving the files to another logical/physical location and forgetting
to tell you or to upgrade any links........

although  it will generate a full" invalid virtual disk slot" error
if this is the case.... yours seems to think that the virtual disk
slot does exist but that listserv is unaware of it.....

Is this a new list header you've recently added or is it one that has
perhaps been placed "live" instead of using GET and PUT and the
listserv server was not downed when it was placed and then restarted?
Another idea......... what about any soft-links if you are using a
UNIX type system? Are they correct?

other areas to check as well:-

* check that the directory and the files for the archive exist and
belong to listserv and the permissions are correct on them for
listserv to access.

* check your settings in go.user which reference a file or directory
location and make sure it actually exists, has correct permissions
and correct owner, etc.....


hope this helps

Debra

------------------------------------------------------------------
Date:          Mon, 12 Apr 1999 11:16:13 +0000 From:
BRIAN MC NAMARA <[log in to unmask]>

It seems that everytime I try to free this particular list this is the
response I get;

An error  occurred while logging mail  to the archives of  the COEJLACTION
list. An  incomplete copy of the  message might be present  in the archive
f -> Severity: Error
 -> Facility: Generic error codes
 -> Abstract: File/major entity not found
 -> Rejected: Virtual disk slot N is not a "fixed-ACCESS"
              slot, ie the corresponding
              logical/environment variable was not defined
              prior to LISTSERV
              initialization.

Does anyone have any clues?


-Brian