web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Problem with IIS when using HTTP adapter with inbound port

(0) ShareShare
ReportReport
Posted on by 485

We have a custom SOAP web service for incoming sales orders, but due to incompatibility with net.tcp on sending side, we had to use HTTP adapter. The problem now is that it can only handle sales orders with about 50 lines max. We should be able to receive at least 100-150 sales lines in one request, but something happens to large messages between IIS and AOS. I can see IIS receives the request msg, but it probably never goes to AOS. I have tried to increase max and timeout-values in web.config for both bindings, HTTP and net.tcp like this:

            <basicHttpBinding>
                <binding name="basicHttpBindingWithWindowsAuth" closeTimeout="00:05:00" openTimeout="00:05:00" sendTimeout="00:05:00" maxBufferPoolSize="2147483647" maxBufferSize="2147483647" maxReceivedMessageSize="2147483647">
                    <security mode="TransportCredentialOnly">
                        <transport clientCredentialType="Windows" />
                    </security>
                </binding>
            </basicHttpBinding>
            <netTcpBinding>
                <binding name="DefaultServiceGroupBinding" closeTimeout="00:05:00" openTimeout="00:05:00" receiveTimeout="00:10:00" sendTimeout="00:05:00" transactionFlow="false" transferMode="Buffered" transactionProtocol="OleTransactions" hostNameComparisonMode="StrongWildcard" listenBacklog="10" maxBufferPoolSize="2147483647" maxBufferSize="2147483647" maxConnections="10" maxReceivedMessageSize="2147483647">
                    <readerQuotas maxDepth="32000000" maxStringContentLength="81920000" maxArrayLength="163840000" maxBytesPerRead="4096000" maxNameTableCharCount="16384000" />
                    <reliableSession ordered="true" inactivityTimeout="00:10:00" enabled="false" />
                    <security mode="Transport">
                        <transport clientCredentialType="Windows" protectionLevel="EncryptAndSign" />
                        <message clientCredentialType="Windows" />
                    </security>
                </binding>
            </netTcpBinding>

So what it does with large orders is basically nothing.. And it takes only about 5-10 seconds to response to the sales order with 50 lines, so it's definitely not a timeout problem. 

What are my tools to find out what happens to the message and why it's not moved forward to AX? IIS adds only the request to logs, but nothing more. Any tips where to start solving the problem?

*This post is locked for comments

I have the same question (0)
  • Vilmos Kintera Profile Picture
    46,149 on at

    Could it be related to message size?

    [View:http://www.cloudfronts.com/configure-inbound-port-in-ax-2012-to-handle-bigger-size-xml-coming-inside-via-aif/:750:50]

    The AIF port allows you to enable logging for all document versions, that keeps the incoming and reply XML document messages.

    It is in the System administration module of AX. Also processing errors are there.

  • migi111 Profile Picture
    485 on at

    Hi,

    Thanks for trying...yep, I've already increased the message size and I also have enabled logging for all document versions.

  • Vilmos Kintera Profile Picture
    46,149 on at

    Ok then what do you see in the logged documents? Is there an incoming message? Is there an error logged?

    For troubleshooting purposes to rule out issues with communication and IIS configuration problems I typically set up a file-based AIF adapter, and validate the document exchange there. Even you could debug through if required:

    [View:https://technet.microsoft.com/en-us/library/jj710372.aspx:750:50]

  • migi111 Profile Picture
    485 on at

    You probably mean in Document history or exceptions form? Yes I can see there the incoming messages, but only for those that have made through IIS (under 50 rows). So I still think the issue is in IIS not passing bigger orders to AX.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans