You’re offline. This is a read only version of the page.
Announcements
1,671
Hi everyone
I'm running a certain report in Ax 2012 R3 CU13, Vendor Invoice Transactions. When run for a short period, it works. When run for a long period, it doesn't - it runs longer and so times out.
The time out happens after 10 minutes exactly.
The timeout problem isn't on the report server itself. The site default timeout setting is 2 hours, and the report itself has a timeout setting of 30 minutes.
I found this article which seems more appropriate:
However, even though I've implemented these changes, the timeout still happens.
Here is other information:
- The reporting service is on a different server to the AOS
- The reporting service uses a default config file found on the AOS server
- The (main) error message in the log file on the report server is:
System.TimeoutException: A timeout error occurred while calling the AOS service. Use the Microsoft Dynamics AX Configuration utility to change the WCF configuration values. Exception details: The request channel timed out while waiting for a reply after 00:09:59.9531497. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. ---> Microsoft.Dynamics.AX.Framework.Services.Client.QueryServiceException: The request channel timed out while waiting for a reply after 00:09:59.9531497. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. ---> System.TimeoutException: The request channel timed out while waiting for a reply after 00:09:59.9531497. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. ---> System.TimeoutException: The socket transfer timed out after 00:10:00. You have exceeded the timeout set on your binding. The time allotted to this operation may have been a portion of a longer timeout. ---> System.IO.IOException: The read operation failed, see inner exception. ---> System.TimeoutException: The socket transfer timed out after 00:10:00. You have exceeded the timeout set on your binding. The time allotted to this operation may have been a portion of a longer timeout. ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
Things I've tried:
- Modified the timeout value in the config file (according to the article), and replaced the config file on the AOS server
- Modified the timeout value in the config file (according to the article), and placed it in the bin folder on the report server
- Modified all timeouts in the file to 1 minute to see if any of them have an effect on the report, but the same error occurs. Even though all timeouts are 1 minute, the report times out after 10
- Restarted the reporting service after each of these operations
- Tried the suggestions here: docs.microsoft.com/.../tips-to-help-prevent-long-running-reports-from-timing-out
What am I missing? Any help appreciated as always
I've tried the configuration on the first link that you mentioned, and it seems to be working on my server and it resolved the time out error.
Other than that, before that config, I've set no timeout in the SSRS Site settings and Report setting (on the report name it self). Also i've set no timeout on my SQL Server Instance: SSRS and Database
The only real solution is to convert it to pre-process as described here docs.microsoft.com/.../how-to-long-running-reports . Pre-process reports do not have a timeout as such so can run for days.
#1
André Arnaud de Cal...
294,217
Super User 2025 Season 1
#2
Martin Dráb
232,978
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (
