Signature on document is invalid (inconsistent field signatures)

I had been running into the Notes Error “Signature on document is invalid (inconsistent field signatures)” when trying to send a Notes documetn.

I have found a patch for the problem, which till now avoided the issue triggering an error message again:

I found that the error gets triggered when I try to send a document which contains a corrupted rich text field which is spread over more than one entry in the field list:

The first instance was not signed, where as the other 2 instances where signed. Unfortunately the document property .isSigned does only show the status from the first instance = not signed in the debugger!

Therefore in Notes this problem is not traceable with standard Notes tools/debugger! I have used Ytria scanEZ to debug this!

Once identifyed I could develop the patch:

I loop through all the items of the document and set the property .isSigned to False before sending.

When sending the error does not trigger :slight_smile:

However I have not figured out how the rich text item get’s corrupted in the first place. I can’t reproduce the effect. It seams to be a combination of building up a rich text field (here containing a log of actions on the document) by scripts which are executed by different ID’s.

NB: I never used the sign method. So this seams to be a very basic bug in Notes which is dragged on since Version 4 - time to fix it!

Hope this helps others

Subject: Signature on document is invalid (inconsistent field signatures)

You could also try signing the database or design element (e.g. Form) with a single Notes ID. Some sites use a specific ID file for signing all databases.

I had the same error on a form that I updated but signing the form fixed the problem.

Subject: Signature on document is invalid (inconsistent field signatures)

I have gotten this error many times and I could never completely eliminate it especially if I had a rich text field in the document. I did make this discovery last week. I had created a separate mail form and still got this error until I removed the $ConflictAction field. I realize that this field is for something completely different but it seems to work for all of my mail documents in eliminating the Signature on document is invalid (inconsistent field signatures) error. It could be coincidence but somethings in Notes are always coincidental.

Subject: Signature on document is invalid (inconsistent field signatures)

Here’s one more scenario for this error to come up:An agent tries to send a document with form (no rt items on the form, just a handful of text items) but the form being used to send along was last signed by someone without enough rights to send the memo.

Solution:

Sign the form with the same ID as the agent.

Subject: Signature on document is invalid (inconsistent field signatures)

Yes, it did :slight_smile:

Subject: Signature on document is invalid (inconsistent field signatures)

Thanks for your post, it worked for me. I couldn’t understand the response “sign the form with a single ID” since a form is always signed by a single ID. However looping on items worked, thanks again.

Subject: RE: Signature on document is invalid (inconsistent field signatures)

We had the problem on a doc.send when it have a embedded sub-form. Signing the database did not help.

To fix it, I opened the form, then double-click the sub-form. Made a change and saved the sub-form then the form.

I hope this help:


David C Slatter

Sr App Dev

210-697-1390

Subject: fix: Signature on document is invalid (inconsistent field signatures)

Here are three things I now do:1. make sure all items are not signed

Forall oneitem In doc.Items

oneitem.IsSigned = False

End Forall

Call doc.Sign 'let this user sign it

Call doc.Save(True, True) 'don’t forget to save

  1. manually look at properties of each field in designer Security Settings (beanie cap tab) - you are looking for things like:

a) Sign if mailed or saved in section

b) Enable encryption for this field

c) Must have at least Editor access to use ← this is the one that got me

  1. Look at any Computed(Computed on Compose) fields which expect to inherit valid values. In one instance I had error handling in the “parent’s” original field but in this form the computed field just inherited and this caused ‘Signature on document is invalid…’ - go figure.