how to handle long loading in ssrs report

(0) Share

Report

Posted on by Rvp_

Hello Everyone,

can anyone help me, i made a report use query builder and for the parameter i use inventdim table but when i try ro make design in VS(visual studio) or i will try to run the report in VS it just show loading until lost connection.

is there a problem with my report or it happen because i use inventdim ? and how to handle it?

thanks.

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Rvp_ 89 on at

Like (0)

Report
hello crispin,

i just wanna show normal report but i use 2 parameters.

1. use contract class for first parameters

2. use query

if i just use contract parameter it go well

but if i use all the parameters it just show loading like this :

and after a long time it show error like this :

Error 1 Timeout error occurred will calling AOS service. Use Dynamics AX client configuration utility to change WCF configuration values. Exception details: The request channel timed out while waiting for a reply after 00:09:59.9870000. 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. EU_RPT_HitunganProsesQuery.EU_PD_HitunganProsesQuery [Preview] 0 0

and i dont know how to handle that problem, i still cant check the report show true data or not

Was this reply helpful? Yes No
Jie G on at

Like (2)

Report

Hi,

According to the error message, we need to use Dynamics AX client configuration utility to change WCF configuration values. Following are the steps to adjust the client-side WCF timeout:
1. Open the Run window and type AXclicfg to open the client configuration.
2. Create a new client configuration and give it a name.
3. In the Connection tab, click on the Configure Services button. A message is displayed as seen in the following screenshot; click OK to continue.

4. In the Configuration window that opens up, locate the Bindings node of QueryServiceEndPoint.
5. In the adjacent Binding tab, locate the SendTimeOut property and increase it from the default value of 10 to the desired amount.
6. Similarly, in the MaxReceivedMessageSize property, increase the message size from the default value to the desired value. The maximum value is the int64 limit, since this is an int64 field.
7. Click on Apply followed by OK.

Was this reply helpful? Yes No
Rvp_ 89 on at

Like (0)

Report

thank you ada ding, heheh thats good

Was this reply helpful? Yes No
guk1964 10,888 on at

Like (0)

Report

My first suggestion is to debug/trace/optimize your code. e.g to avoid Select * or inner joins.

Changing timeouts is rarely the right answer other than for a temporary fix while you investigate.

Long timeouts for example cause the [ReportServer]TempDb database on the SSRS database server to grow very large when many users have open sessions

Have you checked the SSRS logs?

What version are you on - there was a hotfix for long running reports at R2 v7

if you are going to change timeouts then you might also need to look at other timeout settings

The previous note above relates to the Query Service that sends data to SSRS when requested, You can increase the sendTimeout attribute of the binding element with the QueryServiceBinding name attribute to handle requests that take longer than the default 10 minutes. You might also then check the Ax32Serv.exe.config file for the AOS handling reporting requests

As well as a Site level timeout you can also set timeout for the specific report only. (right mouse menu/manage)

The SQL Server instance has two settings that may cause timeouts when the user session used to render SSRS reports takes too long.

SessionTimeout and SessionAccessTimeout settings (both are in seconds.) but these a bit more complex to change.

Was this reply helpful? Yes No