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

Question

Question

Laserfiche Unknown Error 768 after accessing several Documents

asked on December 30, 2019

I've just finished setting up a solution for a client and their users are having problems accessing documents in the main Laserfiche Windows client.

 

After logging in they can look at several documents (3-4) in various locations in the repository but then after the 4th file they try to access another one and are denied.


It isn't a permission issue as the locations are not restricted. (There are restricted areas but the users can successfully access those depending on rights).

Does anyone have any advice on how to resolve this?

 

We're running the latest release of Laserfiche Avante 10.4

Here's the error code in full:

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

LFSO:
    Call Stack: (Exception)
        CLFEntryListing::CreateForDispatch
        CLFFolder::GetEntryListing
    Additional Details:
        HRESULT: 0x80040300 (CLFEntryListing::setParams, lfentrylisting.cpp:123)
         (LFSO/10.4.0.63)
LF.exe (10.4.0.311):
    Call Stack: (Current)
        CFolderTreeView::GetEntryListingByFolder
        CFolderTreeView::GetEntryListingByFolderId
        CFolderTreeView::InsertChildFolders
    Additional Details:
        Exception: 0x80040300 [768] (Unknown error.) (CFolderTreeView::GetEntryListingByFolder at foldertreeview.cpp:4117)
    Call History:
        IsRepositoryLoggedIn
        GetOptionString ([Settings]RefreshFolderPane)
         CAttachedRepository::GetProfileValue
        CFolderTreeView::InsertChildFolders
         CFolderTreeView::GetEntryListingByFolderId
          CFolderTreeView::GetEntryListingByFolder
           GetOptionString ([Settings]ColumnGroupedByFoldersAndDocuments)
            CAttachedRepository::GetProfileValue

0 0

Replies

replied on December 30, 2019

Please open a support case, we need the trace logs to identify the root cause. To get these logs, go to Help->About->Tracing. enable LFSO tracing, restart the client and reproduce the problem.

0 0
replied on December 30, 2019

Thanks Robert,

 

I've got a support case open. I will start that tracing though on the client side and try to get more details.

Once solved I'll update this answer and close it down.

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

Sign in to reply to this post.