We are working on a form and some Lotustscript agent code that uses the .Send (True ) command (to store form with email). The code runs fine when I am the last editor/signer of the form. However, when we sign all the design elements with the Server ID, the code gives the following error when the .send( True ) command is being executed: "Notes error: Signature on document is invalid (inconsistent field signatures).
Does anyone know why this would happen? Is it a security setting in the Database, on the form/fields, or LotusScript agent perhaps?
When you do sign with the server ID, you do have "all design documents" (not able to change) AND you did not check "update existing signature only (faster)", right for this last option?
in Designer check "Last Modified Date" on your form/subforms (shared actions if any in your form, embedded view/folders/subforms your form can use), to see if last modified date correspond to the date you do sign the objet.
tell me if last modified date correspond to the last time you do sign the database with the server ID (in designer please close then reopen the datase)
Thanks for the continued support Jerome! I am doing exactly as you said and the Date Modified for the different elements is the same as the Sign date and Time.
Got this problem in the past with forms and shared field ($TemplateBuild), I used to sign twice the template and then replace design of the production database, (but finally I ended using signEZ from ytria....).
So try to sign the template twice on server (or locally with server.id....) and then replace design, if still unsucessful, there is something in the form or db that generate such stuff, so if I wa you I would open a case with HCL for this problem.
Do you have a clustered environment? Do other applications on the same server signed by the same server have this issue? That setting that Jerome identified, seems to be used for mail-triggered agents. Is your agent a mail-triggered agent?
This is the error the setting tries to prevent: Notes displays the message for the user "Unable to determine the execution access privileges" if the mail server cannot be reached.
You didn't mention if the server you are running this on is your mail server.
2 - No other apps have the issue, but I don't think any others use the TRUE for Attach Form in the .Send command. We tested it with False and it ran without error. It seems to be a conflict of some type between the server signing of the form and the TRUE (AttachForm) parameter
3 - It is not Triggered by emails coming in, but it builds a doc in LotusScript and sends it. So, I don't THINK that qualifies as Mail-triggered