404 error when attempting to retrieve results from odata link from VB.NET

Rick Root
Rick Root
Tenth Anniversary Kudos 2 Name Dropper Participant
in Developer Discussions

So I'm working on a project that will retrieve data from an ad hoc query odata link in one of our CRM environments. But no matter what I try, I'm getting either a 404 error. or a 401 error.

I am using the vb.net web client object.

I've tried FIVE different methods of authentication.

  • None (401)
  • Basic (404)
  • Default Network Credential (404)
  • Created Network Credential (404)
  • Basic + Created Network Credential (404)

I am 100% positive that the URL is correct. I can paste it right into my browser no problem.

I've also fiddled around with the web.config on my CRM web server. Currrently, there is this:

<location path="AdHocQuery.ashx">
<!-- System.webServer is for II7 (Vista and Longhorn Server)-->
<system.webServer>
<security>
<authentication>
<anonymousAuthentication enabled="false" />
<basicAuthentication enabled="true" realm="ad" defaultLogonDomain="ad" />
<windowsAuthentication enabled="true" authPersistSingleRequest="false" />

</authentication>
</security>
</system.webServer>
</location>

And basically, here's what my VB code looks like:

(Why doesn't this forum have an “Insert Code” option? Sheesh)

test.txt

Comments

  • Rick Root
    Rick Root
    Tenth Anniversary Kudos 2 Name Dropper Participant

    finally got this figured out, after a whole lot of trial and error. I was able to get it working using the preferred method of Default Network Credential - the only way I could come up with to actually not have to store a password somewhere.

    After looking in the IIS logs on our learning environment, I saw three requests each time I ran the global change in our dev server…. the first was a 401, then a 302 then a 404 for the generic error page. I didn't even realize it but the generic error page does not exist, so IIS was getting an actual 500 error then redirecting to the generic error page, and since that didn't exist, it was a 404.

    This was in my web.config on the learning server

    <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">

    When I removed the defaultRedirect attribute, IIS started returning a 500 error instead, and I looked in the server Event Viewer and saw that the user I set up didn't actually have permission to run the ad hoc query!

Categories