Memory problems with preview and moving document into next workflow step

Hi everyone, 

Lately we have experienced strange behavior with latest M-Files version 21.5.10227.5. We have a general feeling that everything slowed down a bit. 

During our testing yesterday, we have experienced problems with memory when we tried to move document into next workflow step (in our case publishing state where we create PDF and link working copy with that released document type). We have as experienced problems when trying to preview document (here we convert document into PDF and show final PDF in preview window).

This is an error occurring when we move document into next workflow step:

CoScriptObjectFactory.cpp, 465, Not enough memory resources are available to complete this operation. (0x8007000E)
ScriptErrorHelper.cpp, 96, Not enough memory resources are available to complete this operation. (0x8007000E)
MDispatchExImpl.h, 694, Not enough memory resources are available to complete this operation. (0x8007000E)
MDispatchExImpl.h, 994, Not enough memory resources are available to complete this operation. (0x8007000E)
MetadataCardAction.cpp, 386, Not enough memory resources are available to complete this operation. (0x8007000E)
MetadataCardAction.cpp, 570, Not enough memory resources are available to complete this operation. (0x8007000E)
MetadataEditor.cpp, 2967, Not enough memory resources are available to complete this operation. (0x8007000E)
MetadataModel.cpp, 4266, Not enough memory resources are available to complete this operation. (0x8007000E)
MetadataModel.cpp, 4703, Not enough memory resources are available to complete this operation. (0x8007000E)
ElectronicSignatureUIHelper.cpp, 235, Not enough memory resources are available to complete this operation. (0x8007000E)
MetadataModel.cpp, 12191, Not enough memory resources are available to complete this operation. (0x8007000E)
CoVaultMountingDocumentOperations.cpp, 3204, Not enough memory resources are available to complete this operation. (0x8007000E)
DocumentCache.cpp, 11283, Not enough memory resources are available to complete this operation. (0x8007000E)
DocumentCache.cpp, 11392, Not enough memory resources are available to complete this operation. (0x8007000E)
DocumentCache.cpp, 19559, Not enough memory resources are available to complete this operation. (0x8007000E)
RPCMethodCallWithRetry.h, 35, Not enough memory resources are available to complete this operation. (0x8007000E)
RPCMethodCallWithRetry.h, 35, Not enough memory resources are available to complete this operation. (0x8007000E)
RPCDocumentOperations.cpp, 12721, Not enough memory resources are available to complete this operation. (0x8007000E)
RPCDocumentOperations.cpp, 7386, Not enough memory resources are available to complete this operation. (0x8007000E)
MCallInLoop.h, 712, Not enough memory resources are available to complete this operation. (0x8007000E)
RPCDocumentOperationsHelper.cpp, 4170, Not enough memory resources are available to complete this operation. (0x8007000E)
RPCDocumentOperationsHelper.cpp, 3731, Not enough memory resources are available to complete this operation. (0x8007000E)
RPCDocumentOperationsHelper.cpp, 9381, Not enough memory resources are available to complete this operation. (0x8007000E)
RPCDocumentOperationsHelper.cpp, 9972, Not enough memory resources are available to complete this operation. (0x8007000E)
RPCDocumentOperationsHelper.cpp, 27544, Not enough memory resources are available to complete this operation. (0x8007000E)
RPCDocumentOperationsHelperPrivate.cpp, 2908, Not enough memory resources are available to complete this operation. (0x8007000E)
RPCDocumentOperationsHelperPrivate.cpp, 3120, Not enough memory resources are available to complete this operation. (0x8007000E)
RPCDocumentOperationsHelperPrivate.cpp, 3503, Not enough memory resources are available to complete this operation. (0x8007000E)
RPCDocumentOperationsHelperPrivate.cpp, 3752, Not enough memory resources are available to complete this operation. (0x8007000E)
RPCDocumentOperationsHelper.cpp, 11627, Not enough memory resources are available to complete this operation. (0x8007000E)
ViewerFiles.cpp, 279, Not enough memory resources are available to complete this operation. (0x8007000E)
ViewerFiles.cpp, 1247, Not enough memory resources are available to complete this operation. (0x8007000E)
ViewerFiles.cpp, 1310, Not enough memory resources are available to complete this operation. (0x8007000E)
ViewerFiles.cpp, 799, Not enough memory resources are available to complete this operation. (0x8007000E)
(M-Files 21.5.10227.5)

Another error occurred with preview, preview just haven't shown anything:

 

Looking into what could cause a problems, we have inspected memory consumption on server/client, it was roughly around 60/80%. DB used most of the RAM. Originally we thought perhaps DB got too slow (we actually do not have all too many documents on this server, it is our testing instance) so we have done DB optimization. It has not helped. We have tried to restart the client multiple times as it seemed to do something with preview (but actually everything is prepared on server side) and it has not helped. After restarting server and all related services e.g. indexing services we were able again to preview and move documents to next workflow step.

It is very strange, we have not experienced this before. We have a lot on that server but it seems somehow MFiles server needed a lot of memory for such a simple actions.

Do you have experienced anything similar? Or any idea what could happened? As mentioned, we had still enough memory for executions.

Thanks.

Dejan

Parents
  • Hi there, 

    Please send a support request for M-Files. 

    Lets have a look at this issue. 

    You can start by clicking the purple ribbon at the bottom of this page: https://community.m-files.com/support/

    In case you're the company M-Files Admin, you should have the credentials to login to our support site and from there, to send a support request. 

  • Hi Timo, 

    Thanks for an offer. We still have not clarified contract agreements so I am not able to create support request. I will do it as soon we get clarified this. 

    Dejan

  • Have seen a similar error in a few instances where the original file had very many pages and perhaps some heavy graphics. The resources required to convert such files where more than allocated for the purpose. I believe you can adjust settings in Configuration, Advanced Vault Settings, but can't remember the details right now.

    Your error should not show up on regular, simple files.

  • Hi bright-ideas, 

    Unfortunately this happens also on simple small files that have only a couple of placeholders. We found out that often during testing we create a lot of sessions (some manual sessions where we connect to client and some connecting over REST API for testing). We have never verified a session management and I have found that sessions usually stay open 24 hours before they elapsed. I have now configured an hour session management in our IIS setup which should manage REST API sessions. Client, we still keep as it is. 

    Today we have again experienced an issue, we were working on VAF application and debugged but not many sessions open any other VS instances open. 

    There were 2 errors occurring:

    sqlservr (4940,R,98) SoftwareUsageMetrics-Api: Unable to create a new logfile because the database cannot write to the log drive. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error -1032.
    
    M-Files Online
    
    The operation failed because SPN value provided for addition/modification is not unique forest-wide.
    
    RPCServer.cpp, 412, The operation failed because SPN value provided for addition/modification is not unique forest-wide. (0x800721C7)
    (M-Files 21.5.10227.5)

    after that we started getting memory issues and we needed to restart the server.

    It seems we are running out of memory. Not quite sure what caused it as before we were ok in the setup.

Reply
  • Hi bright-ideas, 

    Unfortunately this happens also on simple small files that have only a couple of placeholders. We found out that often during testing we create a lot of sessions (some manual sessions where we connect to client and some connecting over REST API for testing). We have never verified a session management and I have found that sessions usually stay open 24 hours before they elapsed. I have now configured an hour session management in our IIS setup which should manage REST API sessions. Client, we still keep as it is. 

    Today we have again experienced an issue, we were working on VAF application and debugged but not many sessions open any other VS instances open. 

    There were 2 errors occurring:

    sqlservr (4940,R,98) SoftwareUsageMetrics-Api: Unable to create a new logfile because the database cannot write to the log drive. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error -1032.
    
    M-Files Online
    
    The operation failed because SPN value provided for addition/modification is not unique forest-wide.
    
    RPCServer.cpp, 412, The operation failed because SPN value provided for addition/modification is not unique forest-wide. (0x800721C7)
    (M-Files 21.5.10227.5)

    after that we started getting memory issues and we needed to restart the server.

    It seems we are running out of memory. Not quite sure what caused it as before we were ok in the setup.

Children
No Data