The error 0 OID field means Domino is trying to update a note that has no valid Object ID essentially, Domino can’t identify which document to update because its internal reference data is missing or invalid.
Confirm the error (NSFNoteUpdate: 0 OID field!).
Then temporarily stop the Router (tell router quit)
Check for Multiple mail.box Files , List all mail.box files (show tasks)
Stop the router (tell router quit)
Take the backup of all mail.box rename into mail_old.box,
Create new mail file (load mail or load router)
Copy or move any good pending messages from the old mail.box into the new one via the Notes client.
Do not move corrupted messages — if they fail to copy, leave them behind.
There are a handful of very old SPRs with this error. But I’ve never seen it. If you haven’t already, please open a support ticket for this issue. L2 will likely want a copy of the mail.box to try to reproduce the issue. They’ll also likely will provide some debug notes.ini settings to try to further understand the issue.
The message “NSFNoteUpdate: 0 OID field!” indicates that the note has a 0 OID (Originator ID), which is supposed to be universally unique.
I understand that recreating mail.box and copying the affected messages into the new one did not resolve the issue.
To assist L2 engineer in identifying the cause, please collect the following information:
When did you first encounter this issue?
Have there been any changes made around that time on the Domino side, the OS side, or in any third-party applications running on the server?
Have all messages routed through the server encountered this error in mail.box, or only some specific ones?
How were those messages sent — by a Notes client, iNotes, Nomad, or Verse? Were any sent programmatically by a Notes agent?
Does this happen every time a message is sent, or just occasionally?
When it happens, is it always the same sender or recipients? And how often does it occur?
Are you able to open the affected messages in mail.box?
What is the status of those messages — HOLD, DEAD, or waiting for transfer?
Do you have other mail servers, and if so, have you seen the same issue there?
Is any antivirus software running on the server? If so, please try pausing it and sending another message to check if the issue persists.