Trying to use Essbase connector in POWER BI Desktop

[Jason99]

Hello,

When I try to connect to an Oracle Essbase server through POWER BI Desktop, I get the following error when trying to connect:

ExceptionResultMessage:
For security reasons DTD is prohibited in this XML document. To enable DTD processing set the DtdProcessing property on XmlReaderSettings to Parse and pass the settings into XmlReader.Create method.

I've looked on the web for a solution but can't find a straightforward, step by step solution, if there is even one. Is there?

Jason

[v-nmadadi-msft]

Hi @Jason99 

May I check if this issue has been resolved? If not, Please feel free to contact us if you have any further questions.

Thank you

[Jason99]

Hello. None of anybody's suggestions worked. We may have to go with a third party vendor in order to get this to work.

[v-nmadadi-msft]

Hi @Jason99 ,
Sorry to know it didn’t help. Please consider reaching out to Microsoft Support. You can provide them with all the troubleshooting steps you've already taken, which will help them understand the issue better and provide a resolution. They might be able to identify something specific about your admin account setup or provide a solution that isn't immediately obvious. 

Below is the link to create Microsoft Support ticket:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Thank you

[v-nmadadi-msft]

Hi @Jason99 ,

Could you please confirm if the issue has been resolved after raising a support case? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.

Thank you for your understanding and assistance.

[v-nmadadi-msft]

Hi @Jason99 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you.

[v-nmadadi-msft]

Hi @Jason99  ,
Thanks for reaching out to the Microsoft fabric community forum.

Please ensure the Essbase Analytic Provider Services (APS) server is configured correctly for the Provider Servers and Standalone Servers in the Essbase Administration Service (EAS) console. More information: Configuring Essbase Clusters
Additionally, If there's a firewall between Power BI Desktop and the provided hostname, check to ensure the provided hostname and port can pass outbound through your firewall.

Finally, Ensure that the URL is correct.

• Check to ensure the hostname and or IP address is correct.
• Check to ensure the provided port is correct.
• Check to ensure the http (not https) protocol is specified.
• Check to ensure the case is correct for the /aps/XMLA path in the URL.

I hope this information helps. Please do let us know if you have any further queries.
Thank you

[Jason99]

I take it from the replies that this essbase connector is only for Oracle essbase servers that are on-premise and not in the cloud?

[v-nmadadi-msft]

Hi @Jason99 ,
There is no such limitation but just that Essbase 11.1.2.x version and above are supported.

Thank you

[Shahid12523]

That error means Power BI is hitting an HTML page instead of the Essbase XMLA endpoint.

Fix:

Use the correct XMLA URL:

11g: http://<server>:<port>/aps/XMLA

21c: http://<server>:<port>/essbase/xmla

Make sure it’s the right port, case-sensitive path, and use http/https as configured.

Test the URL in a browser—if you see HTML, fix the URL/proxy/load balancer until it returns XML.

Once you point to the right XMLA service, the Power BI connector works.

[wardy912]

Hi @Jason99 

 This is AI Generate and unverified but I hope it helps:

Yes, there is a workaround for the "DTD is prohibited in this XML document" error when connecting Power BI Desktop to an Oracle Essbase server. This issue typically arises due to how XML is processed in the connector, and it's especially common when using the Essbase (Beta) connector.

✅ Step-by-Step Workaround

1. Use the Correct Connection URL Format
   Instead of just entering the server name, use the full XMLA URL format:

   http://<server_name>:<port>/aps/XMLA

   • Example: http://essbase.company.com:19000/aps/XMLA
   • This format is case-sensitive and must be typed exactly as shown.

2. Ensure APS (Application Provider Services) Is Running
   The APS component of Oracle Hyperion must be properly configured and running. This service handles XMLA requests and is essential for Power BI to communicate with Essbase.

3. Use Power Query in Power BI Desktop

   • Go to Get Data → Essbase.
   • Enter the full URL as described above.
   • Choose either Import or DirectQuery mode.
   • Authenticate using your Essbase credentials.

4. Avoid Using Fusion Cloud-Only Essbase
   If you're using Oracle Fusion Cloud and do not have an on-premises Essbase server, direct connection via Power BI may not be supported. In such cases, SmartView in Excel is the recommended tool, and Power BI might require a different integration approach (e.g., exporting data to a supported format).

5. Known Limitations

   • The connector does not support measure hierarchies.
   • MDX queries must be carefully crafted if used.
   • The error you're seeing is due to XML parsing restrictions in .NET, and unfortunately, Power BI does not expose the ability to change XmlReaderSettings directly.

---

🛠 Alternative Options

If the above steps don’t work:

• Consider using Essbase SmartView in Excel to extract data and then import it into Power BI.
• Use ODI (Oracle Data Integrator) or Oracle Analytics Cloud as an intermediary to expose Essbase data in a Power BI-friendly format.