This post was most recently updated on January 9th, 2021.Reading Time: 3 minutes.
This article explains how to fix error with error code AADSTS50196. This issue usually comes up with an error message somewhat like “The server terminated an operation because it encountered a client request loop.”
The error seems to be popping up more and more often. No worries – it wasn’t caused by you! It is, in fact, an unintended side effect of a security hardening feature in some browsers, and some outdated configuration on Microsoft’s end.
Obviously, you could run into the issue on other sites as well, and the workaround is actually the same. The example error messages on this article will be from Microsoft, however.
But let’s first take a step back. What exactly does happen?
So, what is AADSTS50196 error, and when do you encounter it?
The actual error message seems to usually be “AADSTS50196: The server terminated an operation because it encountered a client request loop. Please contact your app vendor”, but as with most AAD-related error messages, I’m sure this one can vary, too.
Typically, you run into it somewhat like this – when navigating to a website hosted by Microsoft – and, crucially, offering a log-in provided by Microsoft – you are unable to proceed and encounter an error message like below:
Sorry, but we’re having trouble signing you in. AADSTS50196: The server terminated an operation because it encountered a client request loop. Please contact your app vendor. Troubleshooting details If you contact your administrator, send this info to them. Request Id: [omitted] Correlation Id: [omitted] Timestamp: [omitted] Message: AADSTS50196: The server terminated an operation because it encountered a client request loop. Please contact your app vendor. Advanced diagnostics: If you plan on getting support for an issue, turn this on and try to reproduce the error. This will collect additional information that will help troubleshoot the issue.
This ugly error is likely thrown at you as soon as you try to access the website.
Due to the implicit authentication happening behind the scenes, the error might stop you from accessing sites such as microsoft.com, MSDN subscriber downloads or even Microsoft Store.
There’s a couple of different solutions to this issue – but the actually root cause is with the way Microsoft handles authentication to their web properties. You can’t solve that. But the steps below aim to remediate the issue somewhat and should help – at least temporarily!
Time needed: 5 minutes.
How to solve AADSTS50196 Error on your machine?
- Change to a different browser
Especially if you’re using Microsoft Edge or Apple Safari, switching to another browser might help. Google is not very prudent about security-related things, so Google Chrome might be the most likely browser to work.
- Clear your browser’s cache
Removing cookies might help! This issue might be solved (at least temporarily) by getting rid of any offending cookies. How to do this varies between browsers, but usually the following keyboard combination opens up the view to do just that:
Ctrl + Shift + Delete
From the window that opens, make sure to choose anything and everything that relates to “cookies”, and hit “Clear”. Like shown in the screenshot below!
And you should be good. If it didn’t help, let me know in the comments section below! :)
- How to fix “System.IO.FileSystem: Could not find a part of the path \AppData\Local\AzureFunctionsTools\Releases\3.17.0\workers. Value cannot be null. (Parameter ‘provider’)” when running Azure Functions locally? - January 12, 2021
- How to nuke the Identity Cache in Visual Studio? - January 11, 2021
- Fixing unexpected Microsoft.AspNetCore package errors after a dependency update - January 6, 2021