SSAS refresh failure after upgrade from Tier S1 to S2 in Azure

Question

Hello everyone.,

I am wondering if anyone has encountered this error and has found a feasible solution for it already.

little bit of context:
we are hosting SSAS cubes in Microsoft Azure services and after an upgrade from tier S1 Standard to S2 Standard, many of our SSAS cubes (compatibility level 1600) are failing to refresh via ADF Web activity and manually from Microsoft Management Studio. the error we are getting is related to a connection timed out.

error from SSMS
The JSON DDL request failed with the following error: <ccon>Failed to save modifications to the server. Error returned: '<ccon>Number must be either non-negative and less than or equal to Int32.MaxValue or -1.

Parameter name: timeout</ccon>. The exception was raised by the IDbCommand interface.

Answer 1

Hi Yamel Peraza ,

Thankyou for reaching out to Microsoft Q&A platform and thanks for posting your query here.

Glad that you figured out the way to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.

It seems that during the upgrade from S1 to S2 Tier, few properties were inadvertently set to invalid values, which were excessively large and exceeded Int32 (MaxValue).

In SSMS, go to the 'Properties' by doing right-click and under the 'General' tab, select 'Show Advanced (All) Properties' , then alter the properties - specifically, 'ExternalCommandTimeout' and 'ExternalConnectionTimeout' - changing their values from 36,000,000 seconds to 3,600 seconds.

Kindly accept the answer by clicking on Accept answer button. Thankyou

Answer 2

I successfully identified the problem. It appears that some configuration properties were modified during the service upgrade from the S1 to S2 Tier.

Solution: I accessed the server via SSMS, right-clicked on 'Properties', and under the 'General' tab, I selected 'Show Advanced (All) Properties'. I then altered the properties - specifically, 'ExternalCommandTimeout' and 'ExternalConnectionTimeout' - changing their values from 36,000,000 seconds to 3,600 seconds. It seems that during the upgrade from S1 to S2 Tier, these properties were inadvertently set to invalid values, which were excessively large and exceeded Int32.MaxValue.

I was able to find references to these properties under tab 'Diagnose and solve problem' in Azure Analysis Services portal and the help options there!