Notes/Domino Fix List
 |  |
| SPR # GRCE6ADT4R | Fixed in 6.5.6; 7.0.2; 6.5.5 FP2 release |  |
Product Area: Server Technical Area: Administration Platform: Cross Platform
Lotus Customer Support APAR: LO11096
SPR# GRCE6ADT4R - During a mail file move, the AdminP failed with the errors: "Error: Unable to obtain mail archive settings for mailfile" and "Error: Signer does not have the required access rights to the source database." In most cases this error can be resolved by having the mail file owner access the archive profile in the mailfile, and accept the current settings. This should resign the profile with the appropriate name and allow the operations to complete. The administrator can then restart the request which failed. Most likely either "Create New Mailfile Replica" or "Push Changes to New Mail Server" will need to be restarted from the admin4 database.
Technote Number: 1463234
Problem:
This issue was reported to Quality Engineering as SPR# GRCE6ADT4R and was fixed
in Domino 7.0.2, Domino 6.5.5 Fix Pack 2 (FP2) and 6.5.6.
Excerpt from the Lotus Domino Release 7.0.2 MR, 6.5.5 FP2 and 6.5.6 fix lists
(available at http://www.ibm.com/developerworks/lotus):
Administration
SPR# GRCE6ADT4R - During a mail file move, the AdminP failed with the errors:
"Error: Unable to obtain mail archive settings for mail file" and "Error:
Signer does not have the required access rights to the source database." In
most cases this error can be resolved by having the mail file owner access the
archive profile in the mail file" and accept the current settings. This should
resign the profile with the appropriate name and allow the operations to
complete. The administrator can then restart the request which failed. Most
likely either "Create New Mail file Replica" or "Push Changes to New Mail
Server" will need to be restarted from the admin4 database.
Refer to the Upgrade Central site for details on upgrading Notes/Domino.
Supporting Information:
The problem Is related to rogue values specified in the archive profile for the
archive.
It is likely that the server-based archive database may have been moved from
another server. A later attempt to move the user's mail file was initiated and
failed due to security checks against the archive database (which still
contained the old server information).
Workaround for earlier versions:
In most cases, this error can be resolved by having the mail file owner access
the archive profile in the mail file, and accept the current settings,
realigning the profile with the correct name, allowing the operation to
complete. The administrator can now restart the failed request. More >
Last Modified on 05/30/2014
Go back
|