Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. "The request failed with HTTP status 400" error when you integrate transactions using Microsoft Dynamics GP Web Services

"The request failed with HTTP status 400" error when you integrate transactions using Microsoft Dynamics GP Web Services

View products that this article applies to.

Symptoms

When you use Microsoft Dynamics GP Web Services to integrate a large number of transactions that contain many distributions, you receive the following error message: 
The request failed with HTTP status 400: Bad Request.

↑ Back to the top

Cause

This issue occurs because a time-out or limitation is being encountered on the integrations that contain a large number of distribution records. 

↑ Back to the top

Resolution

To resolve this issue, you can adjust the maximum message size quota (maxReceivedMessageSize) in the configurator file. To do this, you can modify the WSBindings.config file as follows:

  1. Navigate to the WSBindings.config file in the GPwebservices\ServiceConfigs folder, and open it with Notepad.

    Note The default path is:
    C:\Program Files\Microsoft Dynamics\GPWebServices\ServiceConfigs

     
  2. Add the maxReceivedMessageSize property to the basicHttpBinding node on the binding name line as shown in the following text: 
    <basicHttpBinding>
    <!-- change maxReceivedMessageSize to 2147483647 from 128896-->
    <binding name="BasicHttpBindingTarget" maxReceivedMessageSize="2147483647">
    <readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647"/>
    <security mode="TransportCredentialOnly">
    <transport clientCredentialType="Ntlm"/>
    </security>
    </binding>
    </basicHttpBinding>
  3. After you make the change and then save the modified configurator file, restart the web service, and then test another integration that has a large number of distributions.

↑ Back to the top

Keywords: kbmbspartner, kbmbsmigrate, kbsurveynew, kberrmsg, kbexpertiseinter, kbfix, kbbug, kbtshoot, kb

↑ Back to the top

Article Info
Article ID : 2960931
Revision : 1
Created on : 1/7/2017
Published on : 4/23/2014
Exists online : False
Views : 293