I get the following message:
Admin Process: Received the following error performing a Change User Password in Domino Directory request on «username» (File name: admin4.nsf): Document is not signed.
I replaced the design of the admin4.nsf database again, signed it with the server id. ACL looks allright…
Help, what is going wrong here and how can I fix it?
(The server is upgraded from 5.09 to 6.01)
Subject: Admin process : document not signed
I had the same Problem when doing the following:
-
Renamed a ressource
-
saw the error in the admin4.nsf
-
changed some field in the request-Document
-
checked “Perform request again”
-
tell adminp process all
-
Error: Document not signed …
So I set up a small script-Agent
Sub Initialize
Dim s As New NotesSession
Dim db As NotesDatabase
Set db = s.CurrentDatabase
Dim coll As NotesDocumentCollection
Set coll = db.UnprocessedDocuments
Dim doc As NotesDocument
Set doc = coll.GetFirstDocument
While Not doc Is Nothing
Call doc.Sign
Call doc.Save(True, False)
Set doc = coll.GetNextDocument(doc)
Wend
End Sub
and tadaaa - it worked.
BUT: I was the one who created the original request, I created the Agent and I ran the Agent…all with my Admin ID …
Hope this helps
Bernhard
Subject: Admin process : document not signed
Most requests that get to the Admin database are mailed there. It’s probably saying that the user that mailed in that request didn’t sign the email message.
Subject: RE: Admin process : document not signed
‘didn’t sign the email message’ you name it as if the user has a choice.
But with the esmail message is (as far I can see) nothing wrong;
The user has changed his password, this is automatically send to the adminp process. The AdminP processes the message and makes a document in which a change password request is asked. When AdminP processes this document the AdminP fails with te message I started this post.
But I you are right, how do you want to solve the problem?
Subject: I’m getting this too re: Admin process : document not signed
No solution to offer. I just wanted to add my name to the list of people getting this. I’d say approx 35% of all “Change user password in address book” requests are being rejected because of this.
I am becoming quite nervous about signatures in a mixed R4/5/6 environment - I am having quite a few signature-related issues since I upgraded my Admin server to R6.