Re: .nlo: File does not exist

I spoke too soon. I had the events4 set up to send notices from either
server if the message contains the text ".nlo: File does not exist". These
are the messages we get on ARCHIVE1:
08/14/2012 07:45:14 The database
/ARCHIVE1/NOTES/DATA/archive/a_aburg4.TMP was unable to write to file
/NOTES/DATA/DAOS/0028/9BD651D7E7B567EF6FA5760A445B11EEDF35194E0002710D.nlo:
File does not exist
08/14/2012 07:45:14 Router: Transferred 2 messages to GDISYS01/DEKKO via
Notes
08/14/2012 07:45:15 Error compacting archive/a_aburgess.nsf: File does
not exist

These are the messages I am getting on ARCHIVE2:
08/14/2012 08:09:16 The database
/ARCHIVE2/NOTES/DATA/archive/a_aburg0.TMP was unable to write to file
/NOTES/DATA/DAOS/0022/55F8FC520D2E357085257A5A0042C479809055F8FC520D2P.nlo:
Document attachment is invalid
08/14/2012 08:10:27 Error compacting archive/a_aburgess.nsf: Document
attachment is invalid

Perhaps I waited too long to fix something by cluster. Now what? (other
than changing the message from ".nlo: File does not exist" to "Error
compacting".)

Rob Berendt