The following can seen in a dtrace of nserver.
[1936] (nserver) <3316> EV:L {EVNoteStream::SaveFieldsToNote} (Exit) Status: [Success]
[1936] (nserver) <3316> EV:M EVNoteStream::SaveToNote - saving note
[1936] (nserver) <3316> EV:M EVNoteStream::SaveToNote - error saving note: (551) Invalid or nonexistent document
[1936] (nserver) <3316> EV:H EVNoteStream::SaveToNote _com_error exception. hr=Unspecified error (0x80004005)
[1936] (nserver) <3316> EV:M EVNoteStream::SaveToNote - removing DB objects from target DB
[1936] (nserver) <3316> EV:H {EVNoteStream::SaveToNote} (Exit) Status: [Unspecified error (0x80004005)]
[1936] (nserver) <3316> EV:M EVNoteStreamImporter::Import _com_error exception. hr=Unspecified error (0x80004005)
[1936] (nserver) <3316> EV:L {EVNoteStreamImporter::Import} (Exit)
[1936] (nserver) <3316> EV:M SavesetRestoreHelper::RestoreSaveset - Notes error: (257) Unknown OS error
[1936] (nserver) <3316> EV:L {SavesetRestoreHelper::RestoreSaveset} (Exit)
[1936] (nserver) <3316> EV:M SavesetRestoreHelper::DoRestore - restore failed: 257
[1936] (nserver) <3316> EV:M SavesetRestoreHelper::DoRestore - Notes error: (257) Unknown OS error
[1936] (nserver) <3316> EV:L {SavesetRestoreHelper::DoRestore} (Exit)
This could be caused by the IMAP access to an EV Enabled database. Once an IMAP access has occurred the restore stops working properly.
As a temporary workaround the following command could be run against the affected EV Mailbox database
Load convert -e- mail\
This will disable the NSF support for IMAP for the specific databases allowing the restore functionality to work properly, whenever the database is being accessed by a client IMAP again and a restore is needed the same command is supposed to be run again.
This issue has been addressed as part of the following release:
Enterprise Vault 9.0.4
Enterprise Vault 10.0.2