Hi Experts, I have a bad quality SSRS report to generate the monthly payroll. It takes time to be generated due to the way how the DP calls where developed.
now due to grow in data i get the following error when i run it
{
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
}
i tired few actions it use to work when i do them like restart SQL Services, use the system in the ideal time, run the Rich Client of the application from server. it is not working any more.
when i try to run it from reporting server ,URL http://<serverName>/Reports it get following error , after i changed the report timeout from SQL Server Reporting Services, still i get the error
{
- An error has occurred during report processing. (rsProcessingAborted)
- Query execution failed for dataset 'LevpaySalaryRegStatic'. (rsErrorExecutingCommand)
- 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.9909872. 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.
- The request channel timed out while waiting for a reply after 00:09:59.9909872. 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.
- The request channel timed out while waiting for a reply after 00:09:59.9909872. 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.
- The socket transfer timed out after 00:09:59.9989972. You have exceeded the timeout set on your binding. The time allotted to this operation may have been a portion of a longer timeout.
- The read operation failed, see inner exception.
- The socket transfer timed out after 00:09:59.9989972. You have exceeded the timeout set on your binding. The time allotted to this operation may have been a portion of a longer timeout.
- 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
- The socket transfer timed out after 00:09:59.9989972. You have exceeded the timeout set on your binding. The time allotted to this operation may have been a portion of a longer timeout.
- The read operation failed, see inner exception.
- The socket transfer timed out after 00:09:59.9989972. You have exceeded the timeout set on your binding. The time allotted to this operation may have been a portion of a longer timeout.
- The request channel timed out while waiting for a reply after 00:09:59.9909872. 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.
- The request channel timed out while waiting for a reply after 00:09:59.9909872. 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.
- 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.9909872. 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.
- Query execution failed for dataset 'LevpaySalaryRegStatic'. (rsErrorExecutingCommand)
}
I know the best way is rewrite or enhance the report processing class in the report, but development we take time and testing efforts, can i find solution or temporary solutions. I have only issue in this report other reports are working fine.
*This post is locked for comments
I have the same question (0)

Report
All responses (
Answers (