I have started to get the following error when a data on demand table tries to load.

[christopher sawtelle 2]

I have started to get the following error when a data on demand table tries to load. I have one table loading from an infolink then two others should load based on values in a column in the first table. Any thoughts - suggestions

 

Failed to execute data query at Spotfire.Dxp.Data.Import.InformationLinkDataSourceConnection.ExecuteQueryCore2() at Spotfire.Dxp.Data.DataSourceConnection.ExecuteQuery2() at Spotfire.Dxp.Data.OnDemand.InformationLinkFunctionExecutor.SetOutputResult(DataSource dataSource, DataFunctionInvocation invocation, Boolean isEmpty) at Spotfire.Dxp.Data.OnDemand.InformationLinkFunctionExecutor.d__0.MoveNext() at Spotfire.Dxp.Data.DataFunctions.DataFunctionExecutorService.d__6.MoveNext()

[Manoj Chaurasia]

There shouldn't be an issue if using the same datasource. What do you see the server debug logs

[Vineet Singh]

I have seen this error in the past where Spotfire environment was setup in a load balancer configuration setup. The issue was we would get this error abruptly, I was using table refresh script with some document properties and on demand data table. The on demand query would fail 3 out of 5 times when it got routed to the load balanced server which had onfiguration issue.After the configuration was fixed this error went away.

[christopher sawtelle 2]

Thanks for the info. I am not using any script or prop controls. The first infolink loads and then triggers the second and third. I am wondering now if the second and third infolinks are conflicting since they use the same data source.

[christopher sawtelle 2]

Have not checked the logs yet. From what I have seen only one infolink can access a data source at a time. I know that if I have data pulling from an infolink and then I try to start a second data pull from an infolink using the same data source as the first it errors/times out.

[Abhishek Singh 7]

i also faced the same issue , recently , i was loading an info link , and with it two table were loaded on demand , same scenario as yours , so for the two tables that were loading on demand i included parameters in their infolink , and in data table properties, for the tables that were loaded on demand , the input for the parameter is defined on the basis of the value in column of the first table.

[christopher sawtelle 2]

That's what I am doing. The first loads then the second & third load based on values in a particular column in the first table. When I set the two on demand table to load manually they load fine.

[Abhishek Singh 7]

I was getting this error , because at the time of defining input for the Data on demand table , i was defining input for the Column , not for the Parameter that i set in the information link , i cleared the input for the column , and defined just for the parameter and it worked.

[christopher sawtelle 2]

I do not have any parameters set in the second and third infolinks. Only the first has a prompt and the user simply selects the data set he wants. Then the two on demand tables load based on the values that loaded in a single column in the first table. That is what limits the data for the second and third tables.

[Abhishek Singh 7]

Try giving parameters in the on demand data tables , and defining input for the parameters in data table properties . I know it should work like the way you are doing it. I tried the same.

[christopher sawtelle 2]

Under "Define Input" for the on demand table I have set "Input for the selected parameter" to "Values from column". I select the data table and column to use then I do not restrict it in any other way.

[christopher sawtelle 2]

UPDATE. It appears the two on-demand infolinks were timing out. It never occurred to me to set the number of connections in the data source to more than 1. Setting the MAX to 2 solved this issue since there are two infolinks using the same data source that are trying to run at the same time.

I am going to test this more tomorrow morning when my network traffic is low.

If anyone has comments on best use cases for the MAX number of connections etc. please feel free to pass them on.

[David Millet]

I got the same error with a first table A loaded on demand non automatically, then 2other B and C linked to this one and automatic. It makes the same error messagebecasue C is liked to B. So when I charge A, just after it tries to load at the same time B and C. C fails because it couldn't see B (as it is currently loading).

The option which solves this was to create a buton to load A, then B, then C. A and C at least created with non automatic load. i really think the loading doesn't takes order in account when load automatically. (at least for the Spotfire version 7.11 I use)