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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

AIF TimeoutException from C#

(0) ShareShare
ReportReport
Posted on by 1,501

Using Ax 2009.  I'm consuming AIF web services from a C# application.  Calling an operation of the service one time is fine.  When I use it more frequently the service stops responding. And I get error : 

Le canal de demande a dépassé le délai imparti en attendant une réponse après 00:00:59.9990000. Augmentez la valeur du délai d'attente transmise à l'appel à Request ou augmentez la valeur SendTimeout sur Binding. Le temps alloué à cette opération fait peut-être partie d'un délai d'attente plus long.

(I don't know how to get the message in English)

Then I wait around 5 ot 10 minutes and then the service responds again. It gets really hard to test my application when I have to wait so long between each test.

Anyone encounted something like this and knows what to do?

The service is replying only small amount of information so it's not because there's too much data to transfer.

I've found another post that looks like the same problem here but no answer : dynamicsuser.net/.../236700.aspx

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Martin Dráb Profile Picture
    239,040 Most Valuable Professional on at

    This is what I got from a translator:

    The request channel has timed out waiting for a reply after 00:00:59.9990000. Increase the timeout value passed to the call to Request or increase the value SendTimeout Binding. The time allotted to this operation may have been part of a longer timeout.

    The error merely says that you didn't get any response in given time, but you would have to collect more information to see why. Maybe you're not disposing channels properly. Or the queue is full because the processing takes too much time. Or something else.

    If the problem is in WCF, you have many configuration options - increasing the timeout, throttling and so on. If the problem is in AX (performance, locking), use the usually tools for AX.

  • Steeve Gilbert Profile Picture
    1,501 on at

    Just figured out that I wasn't closing the client!  I used example code from here

    msdn.microsoft.com/.../ff628055(v=ax.50).aspx

    and they weren't closing the client (SalesOrderServiceClient proxy) so I didn't know I had too.

    Thanks for pointing out about the channel not properly disposed, that's what triggered this search.

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Joris dG Profile Picture

Joris dG 5

#2
Andrew Jones a1x Profile Picture

Andrew Jones a1x 2

#3
GL-01081504-0 Profile Picture

GL-01081504-0 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans