We have an application that uses OLE automation to bring notes into view (via EditDocument). For the most part this application works as expected; however we have a recurring problem where the call to EditDocument fails with an HRESULT of 80010105 (RPC_E_SERVERFAULT).
Most of the notes that have resulted in this error case have been calendar documents. And for all cases that we have traced, the behavior appears to be the same. The LotusScript triggered by the form’s QueryOpen eventually calls the Init() method of a NoteCS* object (i.e. NotesCSEventOwnerDocument, NotesCSReservationDocument, NotesCSEventParticipantDocument). During the call to Init() an error occurs. At this point, the Invoke() method of the OLE automation app receives the 80010105 HRESULT, and the executing LotusScript stops in its tracks. The error is never handled (even though a handler is set), and the method never returns. The resulting behavior is almost as if the exception/error from Init() is being picked off by the OLE app and not allowed to propagate back to the LotusScript error handler.
Is this known/expected behavior? The same problem occurs with both VB and C++ implementations. It also occurs under both Windows XP and Windows Server 2003. We are currently using Notes 7, however the problem was also present when using Notes 6.
When one of these notes is opened manually in the Notes client, an error also occurs on the call to Init(). However in this case the error makes it back to the handler, which is just a Resume Next. This is of course the same behavior that we would like to see when opening the note using automation.
Thanks.
Jim