More problems with server based archiving

Two of my users which are set up for server based archiving have the following problem when archiving runs:

“Error archiving documents from : You are not authorized to use the server on remote server.”

The archive is created and documents copied but they do not get deleted from the original mailbox.

I have checked ACL’s etc. but can not see any difference between these two and the mailboxes where archiving works correctly.

I see from Lotus KB that one suggestion is to recreate the mailbox but before I do that I just wanted to make sure there are no less drastic approaches to this issue.

Any ideas?

Subject: SOLUTION !!! - More problems with server based archiving

This fix was from and IBM tech… did it for 2 users and it works.

  • Open affected mailfile

  • With mailfile open go to Create >> Agent

  • this will open the mailfile in designer client

  • Specify name for agent in agent dialogue and click on small check in the right side of the name field

  • Change the drop down list box from “Simple Action(s)” to “LotusScript”

  • Click on Initialize event

  • Paste the code between the “Sub” entries

Dim s as new notessession

Dim db as notesdatabase

Dim doc as notesdocument

Set db=s.currentdatabase

Set doc = db.GetProfileDocument(“Archive Profile”)

Call doc.Remove(True)

  • Save these changes

— Now have user run the agent from mailfile by selecting Actions >> Delete Archive Profile (this will be whatever you named the agent)

  • Have the user close and re-open the mailfile and this will create a new archive Profile

  • Re-run the compact -A and this should resolve the error

Subject: More problems with server based archiving

I am having the same exact problem and have been working with IBM since Friday. So far they had me enable console logging and then change the logging level for archiving using set config log_archiving=5, re-run the Compact -A and try to capture the information. FYI, the console log is stored in the IBM_TECHNICAL_SUPOORT folder in the DATA directory.

I would suggest giving them a call to open a ticket because the more people they realize are having this problem the better.

If I get a solution today, I will post.