I just upgraded our servers and clients to Notes 6.0.1 and created an archiving policy (explicit) for some users to test.
We want to archive to a different server than the mail server.
However, when launching the compact -a mail\xxxx.nsf on the server, we have a strange error:
03/11/2003 10:10:06 AM Running Program document for ‘COMPACT -A mail\xxx.nsf’
03/11/2003 10:10:13 AM Archiving documents from mail\xxx.nsf (Firstname LASTNAME)
03/11/2003 10:10:29 AM Pushing mail\xxx.nsf to Archiveserver/Organization archive\a_xxx.nsf
03/11/2003 10:10:31 AM Unable to replicate ArchiveServer/Organization archive\a_xxx.nsf: Invalid or nonexistent document
03/11/2003 10:10:32 AM Error archiving documents from mail\xxx.nsf: Invalid or nonexistent document
03/11/2003 10:10:32 AM Database compactor process shutdown
Does somebody know a fix for this?
Thanks a lot for your help.
Marc
Subject: Server based archiving problems - Please help
I’ve a evry similar problem. The log reveals the following:
load compact -a mail\madel.nsf
04/05/2004 07:41:04 Archiving documents from mail/madel.nsf (Madel Mail DBase)
04/05/2004 07:41:32 Pushing mail/madel.nsf to Archive/SELMS/AN mail\A_Madel.nsf
04/05/2004 07:41:33 Unable to open note on mail/madel.nsf (NoteID = 21922) to store in Archive/SELMS/AN mail\A_Madel.nsf (NoteID = 0): You are not authorized to perform that operation
This “Unable to open note…” is reported for I think every single doc to be archived filling up the log.nsf
The archive db is created correctly, it’s just when the actual archiving occurs (I thing after determining what to be archived and creating the archive db) the problem starts.
I’ve checked all ACL’s, server security settings, Mail file owners etc, fixup, restarted Domino servers etc.
I have no archive policies set up.
The strange thing is that when set up it worked. I scheduled the compact -a task to run at night and tu my surprise the log file is full of the "unable to open note " messages.
Any solution?
Subject: RE: Server based archiving problems - Please help
Ok, maybe this will work for you.I upgraded to Domino 6.0.2 CF1. Then, checked all calendar profiles for the databases to be archived. I even deleted some of them with a small LotusScript and re-created them without forgetting to set the right owner of the mail files to be archived.
Check in the ACL that source and destination servers had manager access to the databases. Run a complete fixup and compact on each of them and deleted all full text indexes before on the files.
But I think, the one thing that did the trick was to re-create the profile documents. Maybe they got messed up with the upgrade. Of course, be sure that the source and destination server have proper access to create dbs and replicas on the destination server.
Hope it will help you.
Marc