Word Integration with documents on mapped network drive

Robin Goodall
Users have a mapped network drive such as U:\ goes to \\filestore\r\rjg99\

User creates a new document, can insert citations no problem. Save the document to the U: drive (or reopen a document saved on the U: drive), now inserting citations gives the error:

Zotero experienced an error updating your document.
[zoteroWinWordIntegration Exception... "Could not find a running Word instance." code: "0" function: "zoteroWinWordDocument::initFromActiveObject" location: ".\zoteroWinWordDocument.cpp"]

Strangely, opening the document from the UNC path works fine. Tried with alternative mappings and all have the same problem. Using a drive mapping fails, using a UNC works.

Users should not be expected to work out the UNC path to their filespace to open documents.

Please can this be resolved asap.


Error log version stamp:
version => 3.0.8, platform => Win32, oscpu => Windows NT 5.1, locale => en-GB, appName => Firefox, appVersion => 14.0.1

Entries when using MAPPED DRIVE:

(3)(+0000000): Integration: Instantiating @zotero.org/Zotero/integration/application?agent=WinWord;1 for command addCitation with doc U:\test\test.docx

(3)(+0000003): 'QueryInterface' => function(...){...}
'message' => "Could not find a running Word instance."
'result' => 2147500037
'name' => "Could not find a running Word instance."
'filename' => ".\zoteroWinWordDocument.cpp"
'lineNumber' => 0
'columnNumber' => 0
'location' => {}
'inner' => {}
'data' => {}


Entries when using UNC:

(3)(+0015440): Integration: Instantiating @zotero.org/Zotero/integration/application?agent=WinWord;1 for command addCitation with doc \\filestore\r\rjg99\test\test.docx

(3)(+0000029): CSL: Using collation sort

(3)(+0000045): CSL: Using collation sort

(3)(+0000019): CSL: Using collation sort

(3)(+0000198): Integration: Retrieved 2 fields in 0.024; 83.33333333333333 fields/second

(3)(+0000045): Setting mode to integration
...
  • Robin Goodall
    Further investigation:
    Word creates file monikers as UNCs in the Running Object Table
    The .DOT uses ActiveDocument.Path and ActiveDocument.name (not ActiveDocument.FullName but that doesn't matter) and passes this to the Firefox addon.
    The addon presumably enumerates the ROT looking for the appropriate instance but cannot find it because U:\test\test.docx doesn't match \\filestore\r\rjg99\test\test.docx

    The plugin needs to check whether the drive letter given refers to a network share and then convert it to a UNC then look in the ROT.
  • Simon
    This will be fixed in the next release.
  • Robin Goodall
    This appears to be fixed for files in subfolders on the mapped drives but not files in the root. The log suggests that it is looking for something like:
    \\filestore\r\rjg99\\test.docx
    (when the drive root is mapped to \\filestore\r\rjg99)

    I'm guessing the double slash is making the lookup in ROT fail.

This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.

Sign In or Register to comment.