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

Question

Question

Laserfiche 9.1.1.546 Client Error Code 9063

asked on August 19, 2014

Just upgraded to Laserfiche 9.1.1.546   Alt – down arrow to advance to the next document to verify for a member gives error. Only occurs when using Alt-Down arrow to advance to next document. Does not occur when using other methods to advance to next document.

 

Error Code: 9063

Error Message: 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:3868)

         (LFSO/9.1.1.546)

LFMetadata91.dll (9.1.1.510):

    Call Stack: (Current)

        CLFMetadataCtrl::SaveData

    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.) (CLFMetadataCtrl::SaveData at LFMetadataCtrl.cpp:1222)

    Call History:

          CPageTemplate::GetFieldValueAsVariant

          CPageTemplate::GetFieldValueAsVariant

          CPageTemplate::GetFieldValueAsVariant

          CPageTemplate::GetFieldValueAsVariant

          CPageTemplate::GetFieldValueAsVariant

          CPageTemplate::GetFieldValueAsVariant

          CPageTemplate::GetFieldValueAsVariant

        CLFMetadataCtrl::SaveData

0 0

Answer

SELECTED ANSWER
replied on August 25, 2014

Will create a support ticket. Thanks!

0 2

Replies

replied on August 19, 2014

Can you provide additional details regarding what changes were made to the original document before the user pressed Alt+Down Arrow to jump to the next document? Is the document part of a workflow?

0 0
replied on August 19, 2014

Alexander, yes a workflow is involved. Documents are scanned via QF session and stored. Once stored, WF processes the documents and moves the documents to either a incorrect folder or Ready to Verify folder. These documents are in the Ready to Verify folder. The verifier then verifies the document and changes a metadata field from Pending Verification to Verified. At that point the WF processes the document to move it from the Ready to Verify Folder to the Completed Member Documents Folder. If they change the field to "Verified" and click Save, they do not get the message. If they change the field to "Verified" and then use the "Alt Down" to save and move to the next document it gets the error.

0 0
replied on August 19, 2014

I'm not able to recreate the issue, however, it could be because the workflow I'm testing with is pretty trivial.

 

Could it be a timing related issue? If you test with documents that aren't involved with a workflow, does the issue still occur? Just open any folder that contains multiple documents, open the first document, edit a field, and then press Alt+Down Arrow.

 

If the issue only occurs with documents that are involved with a workflow, you may want to contact your Laserfiche reseller to open a support case as we may need to review the workflow in question.

0 0
SELECTED ANSWER
replied on August 25, 2014

Will create a support ticket. Thanks!

0 2
replied on August 27, 2014

I current have this issue, 9063:0xc0042367

 


The entry is locked and cannot be modified, or the object needs to be refreshed before it can be updated.

0 0
replied on August 28, 2014

Nick, I have provided Laserfiche Support with a copy of our workflow, a client trace and video. Development was able to confirm that a secondary application has the record locked. Since we have verified tens of thousands of documents using this process previous to the upgrade without issue they have now asked for a server trace to determine what application or process is causing the lock. I am in the process of providing that trace to Support.  I will post response to the board as updated information is available.

0 0
replied on September 9, 2014

Issue resolved. Support provided " a new build of lfs.exe (9.1.1.564). They did not indicate the cause of the problem other than multiple application access was causing the lock condition.

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

Sign in to reply to this post.