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

Question

Question

LF Connector: Maximum message size error (65536)

asked on April 25, 2019

I'm attempting to configure Laserfiche connector to run a workflow and I'm am receiving the following 65536 error.

 

 

We had to enable WCF HTTP Activation on the server(s), which resolved our initial issues, but now I'm getting this message when I attempt to load the list of workflows.

What can I do to I resolve this? I seem to get the same result from all of our workflow servers.

2 0

Answer

SELECTED ANSWER
replied on May 22, 2019 Show version history

Hello,

I finally managed to identify the source of the error. The client side binding in the LFC.exe.config file has no parameter for maxReceivedMessageSize therefore it is limited by the default value (65536).

I confirmed this by manually adding the same paramater value present in the Workflow Web Services' web.config file and when I restarted Connector it succeeded in pulling the list of Workflows.

I'm not sure if this is actually a bug in Connector, but that's the impression so far.

Updating the config file on every install of Connector would overwrite local user settings, so it is not something I'd like to do unless we have no other options.

 

The maxReceivedMessageSize parameter in the binding below is what stopped the error and got the workflow list populating correctly.

      <basicHttpBinding>
        <binding maxReceivedMessageSize="10485760" name="BasicHttpBinding_IWorkflowAPIBase">
          <security mode="TransportCredentialOnly">
            <transport clientCredentialType="Windows" />
          </security>
        </binding>
        <binding name="BasicHttpsBinding_IWorkflowAPIBase">
          <security mode="Transport">
            <transport clientCredentialType="Windows" />
          </security>
        </binding>
      </basicHttpBinding>

Can someone from Laserfiche let me know if this may cause any unexpected issues, or if this is something that can be patched?

1 0
replied on April 30, 2021

We just came across this issue 2 years after your original post. Odd there isn't more cases of it out here. 

0 0
replied on April 30, 2021

Not really. 65KB is a lot of space when you're packing text values. We've only seen this a few times over the years when there are hundreds of workflows.

1 0
replied on April 30, 2021

FYI, I made these changes with no success.  

@████████ and progress on this subject?

Thank you Gents.

 

0 0
replied on April 30, 2021

Sorry, I don't know much about connector. What kind of data are you trying to send over?

0 0
replied on May 3, 2021

Thanks for the responses everyone. We are just trying to get Connector to see the list of workflows. It is giving us a hard time so we are trying everything we can get our hands on, like this post. This was the latest error message we received so it pinged here on Answers.

We have an open support case but got some bad info, probably a newer tech on your end. I think we are on track now but has taken months to date, so every error message we get, I search on Answers.

 

Also, adjusting the maxReceivedMessageSize did not improve anything. It is likely a symptom f the problem.

 

Thanks again   

 

CC: @████████

0 0

Replies

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

Sign in to reply to this post.