Due to scheduled maintenance, some areas of our site are currently inaccessible. Thank you for your patience.

Please reach out to sales@eonesolutions.com with any questions.

Back

Maximum request length exceeded

Published: Dec 08, 2011
Post Author Written by Kevin Jones

When running a Real-Time SmartConnect map from CRM to Great Plains, receiving an error that pops up saying the record could not be saved. When looking in the Windows Event Viewer, and entry is in there that contains the message “Inner Exception: System.Web.Services.Protocols.SoapException: There was an exception running the extensions specified in the config file. —> Maximum request length exceeded”

This is caused by CRM attempting to send over all records instead of just the one record that has changed. Open your CRM Real-Time Data Source for the map you are attempting to run. Click on the Define button. When the SmartConnect Query Builder window opens, click on the Builder View Tab. At the bottom of the window, look at the criteria for the key field in the entity. For example, in the Account entity, the key field (GUID) is Account.Account. In the criteria section, there should be a placeholder that says this: =’00000000-0000-0000-0000-000000000000′ If this is not there, then the Plug-In is trying to send all the data, and not just the specific record that has changed. If the criteria is missing, you can add it. The screen should look like the following.

Feeling stuck? Get the support and guidance you need to help you power through any data challenge

We're on your integration team. Connect with our people and let us know how we can help you.