M-Files is a 2025 Gartner Peer Insights Customers' Choice for Document Management
➡️Download the report!

Options
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 2 replies
  • Subscribers 13 subscribers
  • Views 749 views
  • Users 0 members are here
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Limitation of Roll-Back feature?

ssential

Scenario: I have a marketing staff member that generates great finished documents. Since she uses Photoshop and InDesign files that are reliant on file paths, she's found it easiest during the 'Design Phase' to have everything that's in the design phase within the multi-file. These multifiles consist generally around 20-50 files, all towards the creation of one or two final 'published' documents. The rest are fonts, graphics, logos, mock-ups etc.

I've 'marketed' the concept of a manual workflow for users for this situation in order to prevent duplicate detection on logo files within the multi-files; so that once the design phase is finished, everything except the final document (like a PDF) is deleted, and we can convert the multi-file to a single file. The idea being that should we need to, we can roll back the document to its earlier version if something needs to change. 

In testing this (V. 2021.2) I get this error message:

Question: Is this a limitation if an earlier version is too large? OR is this an error with this version of M-Files?

ShellFrameWnd.cpp, 5633, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
CommandStore.cpp, 320, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
CommandStore.cpp, 403, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
MFShellCommands.cpp, 16171, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
MCommands.cpp, 317, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
MFShellCommands.cpp, 849, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
MFShellCommands.cpp, 3220, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
VaultDocumentOperations.cpp, 1502, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
ThreadOutCaller.cpp, 67, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
ThreadOutCaller.cpp, 583, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
VaultMethodCallTasks.cpp, 1282, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
CoVaultMountingDocumentOperations.cpp, 2987, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
CoVaultMountingDocumentOperations.cpp, 7082, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
CoVaultMountingDocumentOperations.cpp, 7238, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
CoVaultMountingDocumentOperations.cpp, 7544, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
DocumentCache.cpp, 7441, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
DocumentCache.cpp, 7502, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
RPCMethodCallWithRetry.h, 25, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
RPCMethodCallWithRetry.h, 25, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
RPCDocumentOperations.cpp, 12866, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
RPCDocumentOperations.cpp, 7699, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
MCallInLoop.h, 712, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
RPCDocumentOperationsHelper.cpp, 5002, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
RPCDocumentOperationsHelper.cpp, 12186, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
RPCDocumentOperationsHelperPrivate.cpp, 1252, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
RPCDocumentOperationsHelperPrivate.cpp, 4622, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
RPCDocumentOperationsHelper.cpp, 29384, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
RPCDocumentOperationsHelper.cpp, 22396, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
VaultDBSessionEvents.cpp, 578, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
VaultDBSessionEvents.cpp, 1602, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
VaultScriptSessionTemplates.cpp, 269, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
VaultScriptSessionTemplates.cpp, 328, Script execution failed. ((AfterFileUpload::ConvertEmailtToPDF: 312105-37)) (0x800408BB)
VaultScriptSessionTemplates.cpp, 328, The maximum number of script executions permitted during a single operation was exceeded for the object "312105". (0x80040839)
VaultScriptSessionTemplates.cpp, 451, The maximum number of script executions permitted during a single operation was exceeded for the object "312105". (0x80040839)
VaultTrTrackerHelper.cpp, 582, The maximum number of script executions permitted during a single operation was exceeded for the object "312105". (0x80040839)
(M-Files 21.2.9928.4)

Parents
  • 0

    I also want to mention that we do have a script that looks for files like .msg and converts them to PDF automatically. Is this what's happening? I didn't write the code, and I don't understand it. Maybe someone can make sense of it?

  • +1 in reply to ssential

    The rollback causes this?

    This error is typically thrown when an operation causes a "cascade" of other things to happen in the vault.  All of these things happen in a single transaction, and the system throws this error.  It's basically a safety-net to stop the script getting in some sort of unending loop.

    In my experience they're sometimes quite difficult to get to the bottom of, simply because of the sheer number of things that are happening .  You need to understand what exactly the action you're taking causes, then track down what impact that has on other things.  Most of those, I'm sure, you want to actually happen.  Where you have a lot of custom code - or lots of configuration of things like QMS or the compliance kit - it can get quite involved.

    Once you've worked all that out you then have to work out a way to design something that can avoid it...!

    If you definitely want to look at it yourself then I would take a look and see whether there's an event handler named "ConvertEmailtToPDF" (looks to be an "AfterFileUpload" handler).

    Honestly, though, you may want to speak to your M-Files reseller or Customer Success Manager to see what options they can provide around assistance.

Reply
  • +1 in reply to ssential

    The rollback causes this?

    This error is typically thrown when an operation causes a "cascade" of other things to happen in the vault.  All of these things happen in a single transaction, and the system throws this error.  It's basically a safety-net to stop the script getting in some sort of unending loop.

    In my experience they're sometimes quite difficult to get to the bottom of, simply because of the sheer number of things that are happening .  You need to understand what exactly the action you're taking causes, then track down what impact that has on other things.  Most of those, I'm sure, you want to actually happen.  Where you have a lot of custom code - or lots of configuration of things like QMS or the compliance kit - it can get quite involved.

    Once you've worked all that out you then have to work out a way to design something that can avoid it...!

    If you definitely want to look at it yourself then I would take a look and see whether there's an event handler named "ConvertEmailtToPDF" (looks to be an "AfterFileUpload" handler).

    Honestly, though, you may want to speak to your M-Files reseller or Customer Success Manager to see what options they can provide around assistance.

Children
No Data
M-Files
M-Files Support


© 2025 M-Files, All Rights Reserved.