Michael Witmer
asked on
Lotus Notes 6.5.5 Client errors (two)
Okay, upgrading end users to new systems and setting up their systems with 6.5.5
Getting the end user's notes setup for them, put in their information and server information then a series of two errors comes up.
The First One:
"You cannot update or delete the document(s) since you are not listed as an allowable Author for this document."
*the end user is setup for full access on their own email *.nsf file
The Second One:
"The Policy and/or Settings Document assigned to you has been edited by an unauthorized person. Please notify your Administrator that you cannot proceed with the client setup."
*I edited the end users document file last and I'm setup as a full admin......
Getting the end user's notes setup for them, put in their information and server information then a series of two errors comes up.
The First One:
"You cannot update or delete the document(s) since you are not listed as an allowable Author for this document."
*the end user is setup for full access on their own email *.nsf file
The Second One:
"The Policy and/or Settings Document assigned to you has been edited by an unauthorized person. Please notify your Administrator that you cannot proceed with the client setup."
*I edited the end users document file last and I'm setup as a full admin......
Sjef Bosman
Somehow I think the user doesn't have sufficient rights to update his profile. See Tools/Preferences and set the owner of the mailfile to the intended user.
ASKER
The User has manager rights to his own nsf mail file
The owner name in Tools/Preferences MUST be set correctly.
Are you sure it is the mail database Notes is complaining about? Could it be that the used doesn't have sufficient right to write his own document in the Name&Address Book?
Are you sure it is the mail database Notes is complaining about? Could it be that the used doesn't have sufficient right to write his own document in the Name&Address Book?
ASKER
Tools/Preferences where ? Admin ? Designer ?
Notes client. In the mail database, click on the button Tools, then on Preferences. Update "This mail file belongs to:"...
ASKER
The mail file is belonging to the end user.
ASKER
Okay....if I copy a default/empty installation of the client from another system that worked....I can get in and then change the ids file and the location for the user......but still does not make sense why this error is coming up.
I'm not clairvoyant... Sorry.
And I thought clairvoyance was the main requirements for EE? :))
What most IT guys don't realize is that they can't copy an installation from one computer to the next since Notes creates basic databases for each user, log.nsf, names.nsf, journal.nsf, perweb.nsf, bookmarks.nsf. So, while you might have been trying to update a clients installation, the previous installation might have been one that was imaged from another. You can get that error from log, names, perweb or the location documents created by another user ID and where the user is not listed in the ACL of the local databases.
THe other problem is the replicator page will contain the history of replications from a previous user or previous name, and that will prevent replication since the last history note might be an error.
so basically, before you update, you need to check to be sure the local files that are in use belong to the user, make backups of mail, the archives, names, perweb, log, journal, and then install to a fresh directory.
What most IT guys don't realize is that they can't copy an installation from one computer to the next since Notes creates basic databases for each user, log.nsf, names.nsf, journal.nsf, perweb.nsf, bookmarks.nsf. So, while you might have been trying to update a clients installation, the previous installation might have been one that was imaged from another. You can get that error from log, names, perweb or the location documents created by another user ID and where the user is not listed in the ACL of the local databases.
THe other problem is the replicator page will contain the history of replications from a previous user or previous name, and that will prevent replication since the last history note might be an error.
so basically, before you update, you need to check to be sure the local files that are in use belong to the user, make backups of mail, the archives, names, perweb, log, journal, and then install to a fresh directory.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.