Last night I was working on a custom web application and had left Fiddler open to watch what kind of calls Internet Explorer was making to the server. I was working on the opportunity form when I happened to look over and see red log entries passing by on the Fiddler display window. As it turns out, every time I opened the opportunity form it was making bad OData calls to get the business unit of the logged in user. What was happening is the method that was making the call to get the user's business was passing a null parameter to the method which was attempting to pass an invalid guid in the OData call.
As it turns out this bad OData call apparently has been crashing our UAT server environment. We haven't confirmed this as yet but right now we believe that while yes we were making a bad OData call, the server should just return an error like it does in our development environment. What seems to be happening in our UAT environment is the bad OData call crashes the CRM service so there is potentially something on the Microsoft side going on too. This issue is under investigation but the evidence seems pretty compelling at the moment. The Microsoft guys are working to figure out how this is happening but in the meantime we are going to fix our bad OData calls and see if that corrects the issue.
The bottom line is that it appears that if you end up making bad OData calls it could potentially cause server problems on the back end. If you find yourself in the situation use your Jedi powers and make sure to check your web service calls with a tool like Fiddler to make sure everything is as it should be...
It appears that the problem may stem from the service account user being used not being properly setup with the correct permissions. When an error occurs in the system CRM may be attepting to write trace files and such that it can't access which cause the service to hang. This investigation is ongoing but this is the path being followed at the moment.
The complementary paper includes over 12 years of research, recent survey results, and CRM turnaround success stories.
This 60-second assessment is designed to evaluate your organization's collaboration readiness.
Learn how you rank compared to organizations typically in years 1 to 5 of implementation - and which areas to focus on to improve.
This is a sandbox solution which can be activated per site collection to allow you to easily collect feedback from users into a custom Feedback list.
Whether you are upgrading to SharePoint Online, 2010, 2013 or the latest 2016, this checklist contains everything you need to know for a successful transition.