Date Posted:
Product: TIBCO Spotfire®
Product: TIBCO Spotfire®
Problem:
"Could not execute function call" when running data function via TSSS, while logged in as a Spotfire administrator.
Solution:
"Could not execute function call" when running a Spotfire data function via TSSS, while logged in as a Spotfire administrator:
Could not execute function call.
There is no URL specified for TIBCO Spotfire Statistics Services.
at Spotfire.Dxp.Data.DataFunctions.Executors.RemoteFunctionClient.<PromptForCredentials>d__0.MoveNext()
at Spotfire.Dxp.Data.DataFunctions.Executors.RemoteFunctionClient.<OnInit>d__9.MoveNext()
at Spotfire.Dxp.Data.DataFunctions.Executors.AbstractFunctionClient.<Initialize>d__f.MoveNext()
at Spotfire.Dxp.Data.DataFunctions.Executors.AbstractFunctionClient.<RunFunction>d__0.MoveNext()
at Spotfire.Dxp.Data.DataFunctions.Executors.SPlusFunctionExecutor.<ExecuteFunction>d__0.MoveNext()
at Spotfire.Dxp.Data.DataFunctions.DataFunctionExecutorService.<ExecuteFunction>d__6.MoveNext()
(1) Some things to check first:
- For the Administrator user group, has the URL been specified as a preference for the correct statistical engine type for this data function's script (TSSS with TERR vs TSSS with open-source R, for example)?
- If you specify the URL as a preference for the Everyone group, does the data function find the TSSS instance and run?
- Does this happen only in the Web Player, only in the Spotfire Analyst desktop client, or both?
- Does the data function fail to run for all members of the Spotfire Administrator user group, or just for some of them?
- Are users who can run the data function also members of another Spotfire user group that has had the correct URL preference specified for it?
~~~
(2) One way this can happen is when (a) the URL has been specified in the preferences for the Analyst_User group, but not for the Administrator group, and (b) testing is performed while logged in as a Spotfire user who is a member of the Administrator group but is not a member of the Analyst_User group.
Comments
0 comments
Article is closed for comments.