Forum Discussion
Timeout at Microsoft.AnalysisServices.Tabular.Model.SaveChanges(SaveOptions saveOptions)
Anonymous wrote:Hi,
yes, the msmdsrv.ini containing this setting is there, but it is explicitely stated to NOT change this file but the other one that doesn`t contain the setting:
But: I just tried to add the <ExternalCommandTimeout> to the "outer" msmdsrv.ini (it´s not there initially, this is why i assumed that i cannot set it there) and set it to desired value, and on restart my changed setting also appears in the "inner" (rewritten on start of service) file.
So now i just have to see if this does any good...
I definitely was not talking about changing the "inner" Workspace file. As stated in the docs that gets overwritten each time the service restarts.
My "outer" file already has "<ExternalCommandTimeout>" so I'm not sure why your's does not. But copying this setting to the "outer" file should work fine as long as it appears under the correct parent element.
The fact that this setting was missing in your environment would explain why you were seeing the default value of 3600 seconds being applied.
d_gosbell wrote:...
I definitely was not talking about changing the "inner" Workspace file. As stated in the docs that gets overwritten each time the service restarts.
My "outer" file already has "<ExternalCommandTimeout>" so I'm not sure why your's does not. But copying this setting to the "outer" file should work fine as long as it appears under the correct parent element.
...
Hmm, maybe thats a matter of PBIRS version - i have March 2018.
But apart from the question which file to change (which we have sorted out nicely by now ;-) ) - do you think that this setting is indeed responsible for the timeout i´m seeing, or would you suggest looking into something else? (I cannot reproduce the behaviour "at will", so can´t just try it out...)
Thank you
Anonymous wrote:Hmm, maybe thats a matter of PBIRS version - i have March 2018.
yes, that could explain it. I'm on May 2019
But apart from the question which file to change (which we have sorted out nicely by now ;-) ) - do you think that this setting is indeed responsible for the timeout i´m seeing, or would you suggest looking into something else? (I cannot reproduce the behaviour "at will", so can´t just try it out...)
I believe so. This is main timeout setting that we would typically edit on SSAS when working with very large or slow data sources that ran for more than an hour on a single table.