Avalara Tax Connector - Troubleshooting - Error - Maximum Message Size Quota For Incoming Messages Has Been Exceeded

Avalara Tax Connector - Troubleshooting - Error - Maximum Message Size Quota For Incoming Messages Has Been Exceeded

Issue

You may receive the following message after running the Tax macro on an order with a lot of lines:
"'The maximum message size quota for incoming messages (65536) has been exceeded.
To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element.' At Line 0 Position 0"



This only occurs when clicking on the macro.

Steps to Recreate:
Save an Order and click Order Total with Tax

Expected Results:
Instead of showing the error box it should show the box which displays the order total and the expected tax.

Business Impact:
It seems that the connector tool is working it is just not displaying the tax for the order when this error pops up. it also seems to occur on orders that have a larger number of lines on them.


Resolution

There are (2) two possible resolutions.  
1)  Modify the Order Total with Tax macro.

One can choose to either of the following line mods:
  1. util.MaxReceivedMessageSize = CDbl(util.MaxReceivedMessageSize)*10
  2. util.MaxReceivedMessageSize = CDbl(2147483775)


2) Go to the customers SRITaxServer  installation. 
Open the web.config file
In the <bindings> section of the web.config files needs the following bolded modifications;  alongside whatever might already be there:
  1. <bindings>
  2.     <basicHttpBinding>
  3.        <!-- maxReceivedMessageSize="2147483775" maxBufferSize="2147483775"  -->
  4.         <binding name="basicHttp" allowCookies="true"
  5.                  maxReceivedMessageSize="20000000" 
  6.                  maxBufferSize="20000000"
  7.                  maxBufferPoolSize="20000000">
  8.             <readerQuotas maxDepth="32" 
  9.                      maxArrayLength="200000000"
  10.                      maxStringContentLength="200000000"/>
  11.         </binding>
  12.     </basicHttpBinding>
  13. </bindings>
Also verify that the binding name is in the endpoint configuration.
  1. <client>
  2.     <endpoint ... bindingConfiguration="basicHttp" />
  3. </client>

Notes
Notes:
  1. "basicHttp" in this example is the name of the already-existing binding in the web.config. There should already be an existing binding in there--use that name.
  2. 200 million was chosen arbitrarily as a number greater than 65536. The drawbacks of having a larger limit is that there is more vulnerability to a DDOS attack, so that number can be adjusted as needed.


    • Related Articles

    • Common Macro Errors

      Summary: This KB will show the most common Issues and solutions to Errors when running Macros in Visual Requires a Login When a WM-Synergy macro is run an Synergy Login Dialog box pops up. The macroserver is used by vtg.loader.managed to find the ...

    • Avalara Tax Connector - Troubleshooting - Sales Tax Calculation Returns $0

      Avalara Sales Tax Calculation Returns $0 Here is a list of items to verify when trying to figure out why the sales tax calculation returns $0: The Customer does not have “Use Avatax” checked in Customer Maintenance The Customer has ‘Tax Exempt’ ...

    • Maximum Request Length Exceeded

      To correct this error, edit the "Web.config" in the root directory of Launchpad and add / edit the httpRuntime node to allow bigger file sizes to be uploaded: maxRequestLength is in KB executionTimeout is in seconds

    • Avalara Tax Connector - How To - Find Version Number

      Using Visual ERP From Visual ERP run Customer Maintenance -> Macros -> Tax Configuration The 'Avalara Tax Configuration' window will be displayed as shown below. A window will appear with the current version number in the lower left corner. Provide a ...

    • WM-Synergy Macro Editor

      WM-Synergy Macro Editor This is rich client user interface, which allows for the maintenance of Synergy Created Macros that support the Infor Visual ERP Manufacturing, (VE), Visual Basic Scripts (VBScript) typically used in a VE Macro situation. Each ...