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

Question

Question

Client getting 9063 error when renaming document

asked on March 21, 2017

My client is getting a 9063 error when renaming an untitled document when it is open. When they have the document open they will apply a stamp. When they press the key "F2" on the keyboard the laserfiche viewer asks them if they want to save the changes(they click yes), and then asks them to rename the document and the user names it to their needs. After they submit the new name, they get an error 9063 that the entry is locked, but it still saves the name change. They have been having this issue since 8.3, and we have even tried repairing LF(they are currently on 9.1.1.486), and clearing their attributes but nothing has changed. Is this supposed to give that error since the document technically is open? Thanks for any insight!

 

Error Details:

"

Error Code: 9063
Error Message: Could not create new version or undo automatic check out.
The entry is locked and cannot be modified, or the object needs to be refreshed before it can be updated. [9063]

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

LFSO:
    Call Stack: (Exception)
        ILFObjectImpl::Update
    Additional Details:
        HRESULT: 0xc0042367 (LFSession::ProcessResponse, LFSession.cpp:3815)
         (LFSO/9.1.1.453)
LF.exe (9.1.1.486):
    Call Stack: (Current)
        CLFDocument::SaveDocument
        CDocBaseFrame::OnClose
    Additional Details:
        Exception: 0xc0042367 [9063] (The entry is locked and cannot be modified, or the object needs to be refreshed before it can be updated.) (CLFDocument::SaveDocument at LFDocument.cpp:494)
    Call History:
         CAttachedRepository::GetProfileValue
        CFolderListCtrl::RefreshSelectionCache
         CSelectionProperties::SetSelectedEntries
        CMainFrame::GetCurrentStatusMessage
        CMainFrame::GetCurrentStatusMessage
        CSelectionProperties::GetFlags
        CDocBaseFrame::OnClose
         CLFDocument::SaveDocument

"

0 0

Replies

replied on March 21, 2017

Do you have any Workflows running that could be monitoring for document modifications and updating the document from under the user?

0 0
replied on March 21, 2017

Scratch that. I can reproduce this with the 9.1 client, but not the 9.2 client. Looks like this was fixed after 9.1.

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

Sign in to reply to this post.