Skip to content


Error 400 Bad request when using the Excel 2013 or above AddIn

Running a map via the Excel AddIn returns an “Error 400 bad request”. Typically the symptoms only occur when sending a large amount of data, when sending smaller files you do not receive the error.

If you are regularly sending large amounts of data in via the SmartConnect WCF service, you can makes some modifications to the Web.config file to allow for larger transactions. To do this perform the following steps.
1. On the machine that is hosting the SmartConnect WCF service, browse to the following directory.

On a 32 bit machine go here: C:\Program Files\eOne Solutions\wcf
On a 64 bit machine go here: C:\Program Files (x86)\eOne Solutions\wcf

2. Open the web.config file located in that directory using Notepad or some other text editor.

3. Find the section that looks like this:

<readerQuotas maxStringContentLength=”2147483647″></readerQuotas>

4. Replace that section with the following:

  <binding maxBufferSize=”2147483647″ maxReceivedMessageSize=”2147483647″ maxBufferPoolSize=”2147483647″>
<readerQuotas maxDepth=”2147483647″ maxStringContentLength=”2147483647″ maxArrayLength=”2147483647″ maxBytesPerRead=”2147483647″ />
<security mode=”None”/>

NOTE: When you copy the above statement you may end up with accented quotes, which will cause problems.  We recommend copying and pasting the text into Notepad, and then erasing the double quotes and retyping them in Notepad which will put them in the correct format.   Click Web Config Modifications to download a notepad document with the changes in it. You can copy and paste the text from this Notepad document.  

5. Save and close the web.config file. Then in Internet Information Services Manager (IIS) highlight the SmartConnectWcf website and click on the “Restart” icon on the far right side of the page.

You now should be able to process larger transactions using the SmartConnect Excel 2013 AddIn.


Configuring Salesforce Integration User
Business Central Extension Publish Error
Re-registering a Change Data Source in Business Central on
Moving SmartConnect 21 to a new server
eConnect error 4628 - The Tracking Number (Tracking_Number) is empty


SSL Security error using OLEDB Connection
This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms
Removed Part: /xl/vbaProject.bin part. (Visual Basic for Applications (VBA))
The server process could not be started because the configured identity is incorrect.
Using WINSCP and a task to upload or download files from an SFTP site



Business Central CRM D365 Business Central Dynamics 365 dynamics crm Dynamics GP Dynamics NAV Econnect Employee Spotlight eone eOne News error Error Message Events Excel Excel Report Builder Extender Flexicoder GP integration Map Microsoft dynamics crm Microsoft Dynamics GP Navigation List Builder Office Relationships Partner All Hands Call Popdock promotions release Salesforce SmartConnect SmartConnect Bootcamp SmartConnect Maps SmartConnect Office Hours SmartList SmartList Builder SmartPost SmartView SQL Tech Tuesday Templates training Zendesk

Integrate & Automate without Any Code.

SmartList Data has Never Been Faster.

The Easiest Way to Report on GP Data.