Forum Discussion
Essbase Connector - XMLA Parser Error
Hello,
I tried connecting to an Essbase server via the Essbase connector to
http:/host:19000/aps/XMLAas per this blog post https://blog.anbuchelva.in/hyperion/power-bi-steps-to-connect-essbase-using-essbase-connector-beta/
however I get the following error:
"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."
Anyone know how to resolve this?
Thansk!
Hi Anonymous
- Is it a DNS issue?
- Connecting to Microsoft’s datacenters might be trickier than you’d think. Interwebs is filled with stories about Microsoft just returning unresolvable DNS entries, which messes up the script, or your ISP might be trying to help and just makes the issue worse (by offering a “DNS help”-page which just omits the actual exception)
- This might be fixed with changing to Google’s DNS (8.8.8.8), adding new entries to hosts file, disabling ISP or router features or just simply running the program/script somewhere else – try Azure virtual machine, for example.
- It’s not DNS messing up? Then maybe it’s IPv6!
- Trying to disabling IPv6.
- More information about the DNS issues:
- http://asp.net-hacker.rocks/2016/01/15/XML-parsing-problem-because-of-your-ISP.html
- https://stackoverflow.com/questions/13854068/dtd-prohibited-in-xml-document-exception
- https://blogs.technet.microsoft.com/marios_mo_betta_blog/2016/06/05/o365-powershell-error-dtd-is-prohibited-in-this-xml-document/ (that one’s about Verizon)
- More info about the IPv6 issues:
- Is it a DNS issue?
4 Replies
Hi amitchandak, thanks for the quick response, however the links you provided don't address the specific issue I am facing, unless I'm missing something.
HI Anonymous
Please check the below links it mentions excatly the same issue you are facing.
Hi Anonymous
- Is it a DNS issue?
- Connecting to Microsoft’s datacenters might be trickier than you’d think. Interwebs is filled with stories about Microsoft just returning unresolvable DNS entries, which messes up the script, or your ISP might be trying to help and just makes the issue worse (by offering a “DNS help”-page which just omits the actual exception)
- This might be fixed with changing to Google’s DNS (8.8.8.8), adding new entries to hosts file, disabling ISP or router features or just simply running the program/script somewhere else – try Azure virtual machine, for example.
- It’s not DNS messing up? Then maybe it’s IPv6!
- Trying to disabling IPv6.
- More information about the DNS issues:
- http://asp.net-hacker.rocks/2016/01/15/XML-parsing-problem-because-of-your-ISP.html
- https://stackoverflow.com/questions/13854068/dtd-prohibited-in-xml-document-exception
- https://blogs.technet.microsoft.com/marios_mo_betta_blog/2016/06/05/o365-powershell-error-dtd-is-prohibited-in-this-xml-document/ (that one’s about Verizon)
- More info about the IPv6 issues:
- Is it a DNS issue?
