KB485777: Error "Root element is missing" randomly returned when running MDX report against MDX Cube Provider

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.

Symptom  

For MDX data source, such as Analysis Services, Oracle Essbase, TM1, when the report is querying data via MDX Cube Provider, error “Root element is missing” randomly returned in template or DSSErrors.log.
 

Cause  

When the concurrency execution of dossier is big, MDX Cube Provider could fail to create connection to data source randomly.
 

Action  

To fix this problem, we add lock when creating connection in Cube Provider and add retry number when that fails, which can greatly reduce the failure ratio.  We introduce a new setting called MaxConnectionRetryNum in Datasources.xml to control the behavior. This optimization is disabled by default. 
Add entry of the “MaxConnectionRetryNum” in Datasources.xml:   
<MaxConnectionRetryNum>value</MaxConnectionRetryNum> 
 
 Change the “value”, such as: 

• -1:  use the new enhancement and the maximum retry times is 10 by default 
• Greater than 0:  use the new enhancement and the maximum retry times is the value you specify 
• Others: old logic without enhancement 

After modifying the DataSource.xml, you also need to restart the Intelligence Server. 
 

Reference 

About the configuration of Datasources.xml, please refer to other notes: 

• Configure the Essbase Client and the MDX Cube Provider
• Install and Configure Analysis Services and the MDX Cube Provider
• Install and Configure the MDX Cube Provider and TM1 OLEDB Provider