The M-Files Community will be updated on Tuesday, April 2, 2024 at 10:00 AM EST / 2:00 PM GMT and the update is expected to last for several hours. The site will be unavailable during this time.

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

Problem on server side

Hi M-Files and community, 

Wondering if someone could guide how to navigate following problem:

We have our own migration tool written based on REST-based API. For the last release, I had to change quite a bit in our VAF and now our migration tool stopped working.

I am getting an error:

M-Files: 21.10.10725.5

Due to a user or client operation, an error response with the following reference ID was sent to the client: 
1ecb80f5-7a43-4bd1-bc1e-8f374dd0a866
If the error requires further investigation, see below for detailed error information.

Exception Information

Name: 
Message: The parameter is incorrect.

ATLHelper.h, 474, The parameter is incorrect. (0x80070057)
(M-Files 21.10.10725.5)

(0027)
URL: /objects/0
Method: POST
Status Code: 500

Stack Trace

   at MFWS.RestHandlers.ObjectHandler.CreateObject(Int32 objId, ObjectCreationInfo creationInfo, Boolean checkIn)

M-Files:
   CoVaultObjectOperations.cpp, 609, The preconditions specified for the new state are not satisfied. (0x80040840)
   ServerVaultObjectOperationsHelper.cpp, 65, The preconditions specified for the new state are not satisfied. (0x80040840)
   RPCObjectOperationsHelper.cpp, 283, The preconditions specified for the new state are not satisfied. (0x80040840)
   LatestRPC.generated.cpp, 16452, The preconditions specified for the new state are not satisfied. (0x80040840)
   RPCDocumentOperations.cpp, 11711, The preconditions specified for the new state are not satisfied. (0x80040840)
   RPCDocumentOperations.cpp, 5742, The preconditions specified for the new state are not satisfied. (0x80040840)
   MCallInLoop.h, 712, The preconditions specified for the new state are not satisfied. (0x80040840)
   RPCDocumentOperationsHelper.cpp, 2064, The preconditions specified for the new state are not satisfied. (0x80040840)
   RPCDocumentOperationsHelperPrivate.cpp, 208, The preconditions specified for the new state are not satisfied. (0x80040840)
   RPCDocumentOperationsHelper.cpp, 9397, The preconditions specified for the new state are not satisfied. (0x80040840)
   RPCDocumentOperationsHelper.cpp, 10069, The preconditions specified for the new state are not satisfied. (0x80040840)
   RPCDocumentOperationsHelper.cpp, 27746, The preconditions specified for the new state are not satisfied. (0x80040840)
   RPCDocumentOperationsHelperPrivate.cpp, 2883, The preconditions specified for the new state are not satisfied. (0x80040840)
   StateTransitionManager.cpp, 836, The preconditions specified for the new state are not satisfied. (0x80040840)
   StateTransitionManager.cpp, 836, Script execution failed. ((In Publishing, StateCondition: 5343-1)) (0x800408BB)
   StateTransitionManager.cpp, 1168, Script execution failed. ((In Publishing, StateCondition: 5343-1)) (0x800408BB)
   VaultScriptSessionTemplates.cpp, 273, Script execution failed. ((In Publishing, StateCondition: 5343-1)) (0x800408BB)
   VaultScriptSessionTemplates.cpp, 338, Script execution failed. ((In Publishing, StateCondition: 5343-1)) (0x800408BB)
   VaultScriptSessionTemplates.cpp, 338, The parameter is incorrect.
   
   ATLHelper.h, 474, The parameter is incorrect. (0x80070057)
   (M-Files 21.10.10725.5)
   
   (0027) (0x80040007)
   VaultScriptSessionTemplates.cpp, 521, The parameter is incorrect.
   
   ATLHelper.h, 474, The parameter is incorrect. (0x80070057)
   (M-Files 21.10.10725.5)
   
   (0027) (0x80040007)
   CoActiveScriptSite.cpp, 895, The parameter is incorrect.
   
   ATLHelper.h, 474, The parameter is incorrect. (0x80070057)
   (M-Files 21.10.10725.5)
   
   (0027) (0x80040007)
   CoActiveScriptSite.cpp, 737, The parameter is incorrect.
   
   ATLHelper.h, 474, The parameter is incorrect. (0x80070057)
   (M-Files 21.10.10725.5)
   
   (0027) (0x80040007)
   In Publishing, StateCondition, 25, The parameter is incorrect.
   
   ATLHelper.h, 474, The parameter is incorrect. (0x80070057)
   (M-Files 21.10.10725.5)
   
   (0027) (0x80040007)
   MErrorHelper.cpp, 2449, The parameter is incorrect.
   
   ATLHelper.h, 474, The parameter is incorrect. (0x80070057)
   (M-Files 21.10.10725.5)
   
   (0027) (0x80040007)
   (M-Files 21.10.10725.5)

Browser Information

Browser Name: Unknown
Major Version: 0
Supports Frames: False
Supports Tables: False
Supports Cookies: True
Supports Javascript: 0.0
Supports Java Applets: False

System Information

Operating System Platform: Unknown

Usually, in such cases, I would catch something on VAF if there is an issue and fix it or at least understood it.

Now I just see that error happens in workflow state:


StateTransitionManager.cpp, 836, Script execution failed. ((In Publishing, StateCondition: 5343-1)) (0x800408BB)
StateTransitionManager.cpp, 1168, Script execution failed. ((In Publishing, StateCondition: 5343-1)) (0x800408BB)
VaultScriptSessionTemplates.cpp, 273, Script execution failed. ((In Publishing, StateCondition: 5343-1)) (0x800408BB)
VaultScriptSessionTemplates.cpp, 338, Script execution failed. ((In Publishing, StateCondition: 5343-1)) (0x800408BB)

but even though I have on both State action and state pre-condition breakpoints (I debug on VAF), the break point does not get hit.

Do you have any suggestion how I could localize what is going on?

Best,

Dejan

Parents
  • It looks like the state precondition on state "In Publishing".  Is that the one you have the breakpoint on?

  • Hi Craig, yes that's the one. But I have it disabled before I run the tool. So it should not come there.

    That is strange. Same vault app and patch works on one vault but on other 3 not. This could be a major problem because I need this tool for periodic migration of documents.

    If you have any thoughts why disabled state precondition is still reached, let me know. Thanks

  • I honestly don't know about that.  If it's disabled then it should be disabled.  If not then it's a bug in the software, but I've not personally heard of something like this from customers or partners.

    I will ask the stupid question...  Are you sure you disabled it on the correct vault?

    If you 100% believe that the disabled state precondition is being run then I would raise this with support, because that is unexpected behaviour.  That said: support's response may well indicate the age of the server version you're running, as Timo did below.

Reply
  • I honestly don't know about that.  If it's disabled then it should be disabled.  If not then it's a bug in the software, but I've not personally heard of something like this from customers or partners.

    I will ask the stupid question...  Are you sure you disabled it on the correct vault?

    If you 100% believe that the disabled state precondition is being run then I would raise this with support, because that is unexpected behaviour.  That said: support's response may well indicate the age of the server version you're running, as Timo did below.

Children
No Data