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

Question

Question

Action not permitted by server to set Records Management Filing Date

Records Management
Updated February 10, 2022
asked on February 8, 2022 • Show version history

I am logged in as a user which has all Records Management Access rights

My Account has the records management privilege

Based on this documentation for Records Management, these should be the only 2 security configurations for the Records Mangement Add-On.

https://doc.laserfiche.com/laserfiche.documentation/11/userguide/en-us/Default.htm#../Subsystems/client_wa/Content/RecordsManagement/RMsecurity.htm?TocPath=Laserfiche%2520Windows%2520and%2520Web%2520Client%257CLaserfiche%2520Records%2520Management%257CRecords%2520Management%2520Security%257C_____0

 

Yet when I try to set a filing date, I get this error

 

0 0

Answer

SELECTED ANSWER
replied on February 9, 2022 • Show version history

I'm able to get this error, but just wanted to confirm that we're doing the same thing.

I'm using flexible RM, basically trying to set a filing date on a document that's not explicitly under a record folder. If that document doesn't have a cutoff instruction and retention schedule set, then you get the "Action not permitted by server. [786]" error. However, if I do have a cutoff instruction or retention schedule set while also setting the filing date, then it works.

Please confirm.

0 0

Replies

replied on February 8, 2022

What's the full output of the message in "Details"?

My recollection is that "Action not permitted by the server. [786]" is about trying to do an operation the server sees as invalid (like entering letters in a numbers-only field) rather than access rights and privileges, which would throw an "Access Denied" of some sort. I believe that error can also occur if there is a lock on the entry, which prevents any modification regardless of a user's rights/privs, so check for entry locks as well. If you restart the Laserfiche Server service, does the error persist?

There have been a small number of bugs in the past that resulted in this error, so if after validating there are no entry locks in play and checking if an LFS restart clears the error it's still occurring, please open a support case.

As always, providing the software version/build number in your original post helps us help you because it allows us to check for bugs in and fixes for that specific build.

0 0
replied on February 8, 2022

Below is the full details with the server/client build numbers included.

There is no locks showing, these are new documents that I just created without ever opening. I right click and select New Blank Document.

Error Code: 786
Error Message: Action not permitted by server. [786]

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

LFSO:
    Call Stack: (Exception)
        CLFDocument::UnsetRecord
    Additional Details:
        ERROR: 786 (CLFDocument::UnsetRecord, LFDocument.cpp:387)
         (LFSO/11.0.2102.9)
LF.exe (11.0.2103.223):
    Call Stack: (Current)
        CRecordDialog::CommitChanges
        CRecordDialog::OnOK
        CMainFrame::OnRecordUpdateSeries
    Additional Details:
        Exception: 0x80040312 [786] (Action not permitted by server.) (CRecordDialog::CommitChanges at RecordDialog.cpp:283)
    Call History:
          CLFSecurity::HasPrivilege
         CCalendarCycleCombo::Initialize
         CRecordDialog::OnInitDialog
          CRecordDialog::LoadSettings
          CRecordDialog::PopulateRetSched
          CRecordDialog::OnCbnSelchangeCmbCutoff
         CRecordDialog::OnOK
          CRecordDialog::CommitChanges

 

0 0
SELECTED ANSWER
replied on February 9, 2022 • Show version history

I'm able to get this error, but just wanted to confirm that we're doing the same thing.

I'm using flexible RM, basically trying to set a filing date on a document that's not explicitly under a record folder. If that document doesn't have a cutoff instruction and retention schedule set, then you get the "Action not permitted by server. [786]" error. However, if I do have a cutoff instruction or retention schedule set while also setting the filing date, then it works.

Please confirm.

0 0
replied on February 10, 2022 • Show version history

It worked, I was able to set the filing date if I also set a retention schedule at the same time. Does this mean we should set the retention schedule first, then the filing date?

Originally we were trying to do this with workflow and there you must take actions one at a time.

I might have just answered my own question, I set a retention schedule first, saved, then a filing date, and successfully saved.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...