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 CRM (Archived) / Instance Web API not w...
Microsoft Dynamics CRM (Archived)

Instance Web API not working

(0) ShareShare
ReportReport
Posted on by crmprogrammer2013 2,665

Hi,

One of our dev environments is not responding to the Service Root URL that is available in developer resources.

My script which uses odata stopped working and no matter what I do, the script fails to respond to the odata url. That lead me to look at the url that is in developer resources. I tried running this url in the browser and fails to load throwing 'An error has occurred' error. No other information, that's it.

Interestingly our prod and test environments are working fine. The odata url in developer resources are working fine totally fine.

This looks like my dev environment broken or something! Is that right to think so? Has anybody experienced this? How do I troubleshoot further?

Please let me know. I do not want to do my deployments from dev and introduce the bug into other environments.

Thank you.

*This post is locked for comments

I have the same question (0)
  • Ali .NET Profile Picture
    Ali .NET on at

    You have tagged your question for version 2016. I guess you have online orgs. My wildly guessed troubleshooting approach is relevant for Online orgs only.

    What specific versions of CRM you are on in your production, test and dev environments? Is there any difference in versions?

    May be there is some specific update applied by Microsoft (that usually happens automatically) on your dev org that is causing this issue. Compare the versions. And if there are any differences in versions try this:

    • Create an online trial (trials are created on the most recent D365 version, I have observed)
    • Check the version if it is matching your dev org's version
    • If so, try reproducing the issue on that trial org.
  • gdas Profile Picture
    gdas 50,091 Moderator on at

    Hello Roxanna,

    Are you able to browse the API URL separately?

    Try to paste the API URL in chrome browser and add one  entity name like  "/contacts"  to make sure API is responding or not .

  • crmprogrammer2013 Profile Picture
    crmprogrammer2013 2,665 on at

    Thanks Khadim Ali,

    My apologies for not being clear. We are on-prem. We've recently upgraded from CRM 2015 to 2016.

    Things were working fine after upgrade but not sure since when this started. All the dev, test & prod are on version 2016. We always keep them identical. The only change was applied to dev recently was we have added two new fields and a quick view form which are completely unrelated to scripts.

    Please let me know if you need more information. Thanks again!

  • crmprogrammer2013 Profile Picture
    crmprogrammer2013 2,665 on at

    Thanks Goutam,

    Yes, I tried running the URL(xxxx.xxx.xx/.../v8.0) in the browser and all I get is "Object reference not set to an instance of an object"

    I've added /contacts at the end of the url and still got the same above error!

  • Ali .NET Profile Picture
    Ali .NET on at

    Then no idea.

    But if I would have same situation, I would be trying troubleshooting tools/techniques for asp.net/web API on dev/production server. Google has ton of information on how to troubleshoot an application in production. You may apply the same on your dev server.

    You may log a service request with Microsoft Dynamics support team along with trying troubleshoot techniques.

  • Community Member Profile Picture
    Community Member on at

    Need to look at your authentication models.

    I believe there were some changes ie moving from v1 to v2 in an upgrade.

    Additionally you should be able to copy the prod code to your dev environment, it if works you are building on the wrong code base in development.

    You could also run tracing on your dev environment and you will get better exception detail for easier debugging

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 CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans