Domino & Notes error

Document is not signed

Also seen as: Problem with signature on policy document or one of the policy setting documents it specifies: Document is not signed

The alternative wording appears on the server console for policy documents. AdminP requests can also fail with the short form.

What it means

Domino expected a document to carry a valid signature, such as an Administration Request or policy document, but found none, so it would not act on it.

Common causes

  • A policy or policy settings document was created or changed by code or replication in a way that left it unsigned
  • An AdminP request was created by an agent or tool that did not sign it
  • A wrong name in an administrator's Person document, such as a server name in the User name field

Quick fixes

  1. Open the policy or policy settings document in the Domino Administrator and save it, which signs it with your ID
  2. For AdminP requests, delete the failed request and redo the action from the Domino Administrator
  3. Check the Person documents of the administrators involved for incorrect entries in the User name field

Need a hand with this?

Paste your exact message into What's That Error? for a plain-English explanation, or get in touch. I've been supporting Domino and Notes for 28 years.

Disclaimer

The errors, causes and fixes on this site are carefully researched, drawing on HCL documentation and 28 years of hands-on Domino and Notes experience. Every environment is different, though, and a solution that works in one may not be right for yours. Exact wording can also vary between Domino and Notes versions.

This information is general guidance only and is provided without warranty of any kind. Always back up your data and test changes on a non-production system first. To the extent permitted by law, Bruinsma Services Pty Ltd accepts no responsibility or liability for any loss, damage, downtime or other consequence arising from use of this information. For advice specific to your environment, please contact me.