Open rajivsr23 opened 4 years ago
Hi @rajivsr23, were you trying to access the URL on this step? Please note that the URL won't work till you finish the authentication pieces right after this step.
Hi @nishandi I performed all the steps listed in "Step 3" but still get the Error Page.
@nishandi Here is the detailed error report
Server Error in '/' Application.
Response status code does not indicate success: 400 (Bad Request). Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request).
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[HttpRequestException: Response status code does not indicate success: 400 (Bad Request).]
System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() +92844
Microsoft.IdentityModel.Protocols.
[IOException: IDX20804: Unable to retrieve document from: '[PII is hidden]'.]
Microsoft.IdentityModel.Protocols.
[InvalidOperationException: IDX20803: Unable to obtain configuration from: '[PII is hidden]'.]
Microsoft.IdentityModel.Protocols.
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.3282.0
One of the reasons why you may have gotten this server error is because of how you named your base resource name. It is important to follow the naming convention when creating the base resource name i.e, all small letters, no spaces, no special characters, etc and when you create it and begin the deployment, check the deployment process to ensure that there is no errors during deployment.
For example, when you have started deployment, click on the bell icon on top of the azure page and click on the link Deployment in progress to check the deployment.
Here you can check the resources being created and can notice if there are any errors in creating any azure web sites due to an incorrect or duplicated base resource name. If there are errors, you can always go ahead and cancel the deployment and try again with a different base resource name and resource group. Continue this once you get a deployment with no errors in any of the resources created, and you should be able to access the app configuration URL.
I followed all the Steps listed in the Deployment Guide but get an Issue at Step 3.1. I replaced the Base Resource Name on the URL provided but get an error. Here is a screenshot of the error page-
I ran the diagnostics in Azure but in vain. Any help on this matter would be greatly appreciated!