We found a bug with the Scheduled Achiving process. The agent “(Archive Now)” in the standard mail template has a problem where it changes the title of the archive database to:
“User Name (Archive)”
In many cases we have users with multiple archives and they name them after the current year, such as “Joe Test (Archive 2012)”.
But when the archive agent runs it changes the title back. I have determined that the issue occurs on this line:
lngReturn = db.archiveNow()
Unfortunately db.archivenow() is a black box function and we can’t see or control what its doing.
In the agent itself I was able to write some code to capture the db titles from all current archives before db.archivenow is called. Then after it runs, I recheck all the archive titles and replace if necessary.
This enables us to get around the error when the user manually triggers the agent.
However, there is also the scheduled archive process that runs without user interaction. (Via the Compact task in the ($Programs) view of the local names.nsf)
For this one we can’t see what its doing at all, and therefore cannot capture the error. My guess is that its calling some variation of db.archivenow(), but we can’t see it so there’s nothing to change.
I believe there is a general error with db.archivenow() and the compact task that triggers it.
Hopefully someone from Lotus can share some light on the problem and the function itself.
Thank you.