When the error message is lost in translations

By | July 10, 2019

Every now and then, I see this kind of error message in the UCI:


It may seem useful, but, when looking at the log file, all I can say is that, well, something has happened. Since all I can see in the downloaded log file is a bunch of callstack lines similar to the one below:

at Microsoft.Crm.Extensibility.OrganizationSdkServiceInternal.Update(Entity entity, InvocationContext invocationContext, CallerOriginToken callerOriginToken, WebServiceType serviceType, Boolean checkAdminMode, Boolean checkForOptimisticConcurrency, Dictionary`2 optionalParameters)

One trick I learned about those errors in the past is that switching to the classic UI helps. Sometimes. Since the error may look more useful there. Somehow, though, I was not able to reproduce the error above in the classic UI this time around, so… here is another trick if you run into this problem:

  • Open browser dev tools
  • Reproduce the error
  • Switch to the “Network” tab and look for the errors

There is a chance you’ll find a request that errored out, and, if you look at it, you might actually see the error message:


That said, I think it’s been getting better lately since there are errors that will show up correctly in the UCI. Still, sometimes the errors seem to be literally lost in translations between the server and the error dialog on the browser side, so the trick above might help you get to the source of the problem faster in such cases.

4 thoughts on “When the error message is lost in translations

  1. Linn Zaw Win

    Thanks for the post. This error dialogue in Unified Interface is not helpful at all.
    There’s no meaningful message and downloading the log doesn’t help either.

  2. Dan

    This is awesome! Thanks so much, you’d think the {0} and {1} placeholders could be populated with some useful information, but obviously not!


Leave a Reply

Your email address will not be published. Required fields are marked *