web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Trying to connect to O...
Microsoft Dynamics AX (Archived)

Trying to connect to ODataQueryService by using Power View

(1) ShareShare
ReportReport
Posted on by Community Member

Hi,

Just trying to connect to ODataQueryService by using Power View and I receive this error:

DataSource.Error: OData: Request failed:
OData Version: 3 and 4, Error: The remote server returned an error: (400) Bad Request.
OData Version: 4, Error: The remote server returned an error: (400) Bad Request.
OData Version: 3, Error: The remote server returned an error: (400) Bad Request.
Details:
mtessier-aos.mtessierlab.local/.../ODataQueryService

I tried only the server name (no domain) and IP address, no luck.

Should be built-in and does not need configuration, I don't see why it does not work

Any ideas?

Thank you

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Martin Dráb Profile Picture
    Martin Dráb 237,961 Most Valuable Professional on at

    Can you open the URL in web browser?

  • Community Member Profile Picture
    Community Member on at

    Thanks for replying.

    I tried in Internet Explorer and I receive the same error : HTTP 404.

    If I try from the AOS server, it works.

    I tried in another Dynamics AX 2012 R3 environment and I have the same behavior.

  • Martin Dráb Profile Picture
    Martin Dráb 237,961 Most Valuable Professional on at

    So it's a network connection issue... It maybe blocked by a firewall, there may be a problem with DNS or something.

  • Community Member Profile Picture
    Community Member on at

    I wish haha

    I checked everything, firewall, DNS. I can access port 8101 by using telnet. I have the same behavior in 4 different customer environment. I built all of them though haha.

    I am missing something, authentication, registry key, config file...

  • Martin Dráb Profile Picture
    Martin Dráb 237,961 Most Valuable Professional on at

    The fact that it works from AOS and not over network, means that it's network issue by definition.

    Do you mean that you can connect to the URL through telnet but still get HTTP error 404? It's not more useful than getting the same error code in browser. It simply means that no resource with the URL can be found. You said you checked everything, but the fact it doesn't work proves that not everything is correct.

  • Community Member Profile Picture
    Community Member on at

    The telnet test was meant to prove that the firewall was not the issue.

    Just found out that it works with the IP address. Obviously, my DNS records are correctly configured in the DNS.

    Probably related to Kerberos/NTLM/SPN or something similar.  

  • Suggested answer
    Martin Dráb Profile Picture
    Martin Dráb 237,961 Most Valuable Professional on at

    If it work with IP but not with the domain name, it's sound more like a proof that Domain Name System is to blame, rather than that it's "obviously correctly configured".

  • Community Member Profile Picture
    Community Member on at

    Trust me, my DNS is correctly configured.

    I can reach this web service without any problem: (doesn't ask for credentials)

    mtessier-aos/.../MetadataService

    This one does not work: (ask for credentials)

    mtessier-aos/.../ODataQueryService

    and finally, this want works: (ask for credentials)

    192.168.0.7/.../ODataQueryService

  • Martin Dráb Profile Picture
    Martin Dráb 237,961 Most Valuable Professional on at

    Okay, could please explain your problem again?

    Until now you were saying you got 400 or 404 error codes and suddenly you're talking about credentials, which you didn't mention before. I would like to avoid trying to answer a wrong question again.

  • Community Member Profile Picture
    Community Member on at

    It can be confusing because I am sharing my troubleshooting steps as well.

    The problem is quiet simple:

    I receive an error HTTP 400 when I try to browse the Odata web service by using the FQDN address from a server other than the AOS.

    This is a "common" issue with IIS, but never seen it with AIF.

    social.technet.microsoft.com/.../windows-authentication-not-working-on-w2008-server-iis7-when-using-dns-name

    More Info:

    It works if I use the AOS IP address instead of the FQDN

    Web Service ask for credentials (normal), but if I use the FQDN, I can actually type anything and it will go through. With the IP address, if I type the wrong password, it will prompt again. Hence I believe it is an authentication issue and error 400 is irrelevant

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans