Wednesday, February 20, 2008

NSFNOTECOPY breaks attachments

We are doing some work in extension manager addin, and for some reason NSFNOTECOPY periodically corrupts a message's attachments. We get a 'one or more of the source documents attachment are missing. Run fixup to delete the document in the source database'

Has anyone else seen this problem or got a suggestion ?

2 comments:

Richard said...

Difficult to say without knowing more about your code. E.g., what event is your EM handling? Are you copying from one NSF into another? Etc. One thing I can tell you: if your EM routine is copying a note from one NSF, and returning the in-memory note as if it were in another NSF (after resetting things appropriately in the note), and the source NSF's db handle is closed before code back in the Notes client or Domino server (after your EM handler has returned the in-memory note) tries to access the attached objects, then it isn't going to work. I don't recall the exact error -- and for that matter it may depend on the context in which the code attempts to access the objects. I don't know for sure, but I would have to guess that attempting to save the copied in-memory note after the source NSF db handle is closed is much the same situation.

Craig said...

I found a similar problem with NSF hooks ( back in 2005) and there is still no resolution to the problem. Be warned, if it is the same thing, anything stored as an attachment gets corrupt... including design elements like agents.