You are viewing limited content. For full access, please sign in.

Question

Question

Failed to initialize metadata display - Error Code 784

asked on March 27 Show version history

I have a document in a folder that generates this error when I try to open it. Sometimes the Document Viewer will open but both the Electronic File and Metadata panes are blank. Once the error is cleared, the Electronic File portion will load but nothing for Metadata. At other times, the Viewer doesn't open at all.

When the Viewer does load, I've tried closing/reopening the Metadata pane, or even viewing tags, links, etc. but the same error happens.

This document has been in the repository for a few months and various people/processes/workflows have interacted with it, with no issues. Other documents in the folder (and other folders) open without this error. It seems to be something happening with this one PDF.

It doesn't seem to be a security/access issue with the document itself. I've queried one of our system admins to check the SQL side but if it was a server communication issue I'd expect it to be affecting all documents in the repository, not just this one.

Details of the error follow.

(With thanks in advance for any insights into this somewhat weird glitch!)

 

Error Code: 784
Error Message: Failed to initialize metadata display
Operation timed out. [784]

------------ Technical Details: ------------

LFSO:
    Call Stack: (Exception)
        LFSession::SendRequest (GET /+LF/entry/8982475?links=src,dest)
        CLFEntryLinkCollection::InitById
        ILFEntryImpl::FindLinks
    Additional Details:
        ERROR: 784 (TestLastError, LFSession.cpp:930)
         (LFSO/11.0.2102.9)
LF.exe (11.0.2103.223):
    Call Stack: (Current)
        CMetadataWrapper::InitializeControl
        CMetadataDialog::OnInitDialog
        CMetadataDialog::DoModal
        CFolderListCtrl::ViewMetadata
    Additional Details:
        Exception: 0x80040310 [784] (Operation timed out.) (CMetadataWrapper::InitializeControl at MetadataWrapper.cpp:222)
    Call History:
        CFolderListCtrl::ViewMetadata
         CFolderListCtrl::GetSelectedEntries
         CMetadataDialog::CommonConstruct
         CMetadataDialog::DoModal
          CMetadataDialog::OnInitDialog
           GetOptionString ([Settings]MetadataDialogStartTab)
            CAttachedRepository::GetProfileValue
           CMetadataWrapper::InitializeControl

0 0

Replies

replied on March 27

One thought that you might be able to check with the installed desktop client: a multi-valued metadata field with a lot of entries. I saw this once years ago, where a workflow kept appending values to a multi valued field on a certain folder, and trying to load all the values up in Web Access caused issues.

0 0
replied on March 28

Thank you, Pieter. I did have this problem a few months back (which didn't result in the same error, thankfully) so I started investigating and got far enough to see that at least one of the documents linked to the problem invoice does have an excess of a multi-valued field.

But I ran into problems in general navigating through our repository as other issues are affecting our databases today and generating a lot of connection errors in the repository. It could be a confluence of problems hitting at once. At this point, It's hard to tell if the error is the result of the multi-valued field or from whatever is mucking up the databases.

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.