SDK v9 MetastormOperation StartAction problem

Jerzy_Ryszard
Jerzy_Ryszard
in AppWorks #1

Hi,

 

I'm getting this message when invoke an StartAction operation on the ECL.WS service.:

 

MetastormOperation session = new MetastormOperation("someEclAdrress");

...

IActionResponse action = session.StartAction("", mapName, actionName, false, null);

 

Exception:

Failed to execute 'system action'. Exception 'Error: The formatter threw an exception while trying to deserialize the message: There was an error while trying to deserialize parameter http://metastorm.com:StartActionResult. The InnerException message was 'There was an error deserializing the object of type Metastorm.ECL.Client.ActionResponse. The maximum string content length quota (8192) has been exceeded while reading XML data. This quota may be increased by changing the MaxStringContentLength property on the XmlDictionaryReaderQuotas object used when creating the XML reader. Line 1, position 21838.'.  Please see InnerException for more details.' occurred when attempting to 'Run script'. Error: The formatter threw an exception while trying to deserialize the message: There was an error while trying to deserialize parameter http://metastorm.com:StartActionResult. The InnerException message was 'There was an error deserializing the object of type Metastorm.ECL.Client.ActionResponse. The maximum string content length quota (8192) has been exceeded while reading XML data. This quota may be increased by changing the MaxStringContentLength property on the XmlDictionaryReaderQuotas object used when creating the XML reader. Line 1, position 21838.'.  Please see InnerException for more details.

Tagged:

Comments

  • Dan Ternes
    Dan Ternes
    #2

    There are a number of parameters that you need to change in the HTTP Bindings section of the client-side web.config file.  These are:

     

    maxBufferSize="41943040"

    maxReceivedMessageSize="41943040"

    maxStringContentLength="41943040"

    maxArrayLength="41943040"

     

    There's more information in the Help Files at:

    - SDK Enterprise Component Libraries

    - Enterprise Component Library for Web Services

    - Enterprise Component Library for Web Services - Overview

     

    (In case it's not clear, this is supposed to represent the "tree" of help files that you need to drill down into.)

  • Jerzy_Ryszard
    Jerzy_Ryszard
    #3

    In the web.config file (C:\Program Files\Metastorm\BPM\ECL.WS\web.config)
    those parameters were set by default

    Default:

    maxBufferSize="41943040"
    maxReceivedMessageSize="41943040"
    maxStringContentLength="41943040"
    maxArrayLength="41943040"

    Change to :
    maxBufferSize="2147483647"
    maxReceivedMessageSize="2147483647"
    maxStringContentLength="2147483647"
    maxArrayLength="2147483647"

    Still get the error.

    We use ECL for .NET in the designer server script:
    //
    using Metastorm.ECL.Client.Net;
    IMetastormOperation metastormSession = new MetastormOperation();
    //

    Where else should I set the required parameters?

    TIA

  • Kaman_Paul
    Kaman_Paul
    #4

    I realize this is an old post, but I can't seem to fix this and oddly it just started happening.  I don't know how or why.

     

    In either event I've update the web.configs as I can find them... but it still didn't resolve.  Were you able to resolve and do you recall what else you had to do?

  • Kaman_Paul
    Kaman_Paul
    #5

    Anyone?  It appears to not be my day.  Downloaded the SDK chm files and those don't load.  Never really dealt with these help files that much.

     

    I guess I'm emailing the Help Desk.  Joy.

  • Kaman_Paul
    Kaman_Paul
    #6

    The issue related to the maxStringContentLength in the app.config of the service.

     

    However, my problem was compounded because I was testing my service (which was a c# library consuming a BlankFormService) and I didn't have the app.config updated correctly in the console app.

     

    That is, when  you test a library that references a service, your test project (in my case a console app) had to also have the endpoint service reference.

     

    So I think the answer is to have your app.config updated correctly.  That seems to be the weak link because I updated all my web.configs per the previous comments to this post.

  • Aaron Van
    Aaron Van
    #7

    For the CHM files you can right click them and go to properties. Click on the Unblock button and all is good.

  • Michael_Turek
    Michael_Turek
    #8

    I'm was having the same issue as snorek.  I'm basically trying to call a wcf service method.

     

    After setting the configuration like the users mentioned above.  I needed to set these parameters server side on my services web.config file.

     

    I pretty much copied binding info from the metastorm - connections - advanced tab - "basichttpbinding", to the service config file.  Also the endpoint should be pointing to the name of the binding.

Categories

image
OpenText CE Products
AppWorks
Gateway & Platform