You’re offline. This is a read only version of the page.
5
Hi,
Recently we discovered a problem with our CRM to GP Web Service integration.
The issue is that we are receiving a big invoices and when calling a Web Service through the below function
DynamicsGP wsGPParam;
wsGPParam.CreateSalesInvoice(salesInvoice, contextParam, CreateSalesInvoicePolicy);
we are getting the below error message (output for our log file):
2014-11-19 08:40:10,298 [1] ERROR RMS2GPIntegration.Program Error Occured in : CreateInvoices()
System.Net.WebException: The request failed with HTTP status 413: Request Entity Too Large.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at RMS2GPIntegration.GPWebService.DynamicsGP.CreateSalesInvoice(SalesInvoice salesInvoice, Context context, Policy policy)
at RMS2GPIntegration.Program.CreateInvoices(DynamicsGP wsGPParam, Context contextParam, Policy CreateCustomerPolicy, Policy CreateSalesInvoicePolicy, Policy CreateSalesReturnPolicy, String ClassIdParam, LodgeType lodge, AppConfiguration config)
In reference to the WSProgrammersGuide.pdf (page 26-29) we have updated our Visual Studio project app.config file with the below snippet (attached):
<system.serviceModel>
<bindings>
<wsHttpBinding>
<binding name="LegacyDynamicsGP" maxBufferPoolSize="2147483647" maxReceivedMessageSize="2147483647">
<readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384" maxBytesPerRead="4096" maxNameTableCharCount="2147483647" />
<security mode="Message">
<transport clientCredentialType="Windows" />
</security>
</binding>
</wsHttpBinding>
</bindings>
<client>
<endpoint address="http://<Server Name>:48620/DynamicsGPWebServices/DynamicsGPService.asmx"
binding="wsHttpBinding" bindingConfiguration="LegacyDynamicsGP"
contract="DynamicsGP" name="LegacyDynamicsGP" />
</client>
</system.serviceModel>
It did not help and the error message remains the same.
Should we also update any IIS settings, server settings or configuration files on the server?
Do you have any suggestions?
*This post is locked for comments
I have the same question (0)
Share
Report
All responses (
Answers (
