This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(19.2, 85%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EH%3C/text%3E%3C/svg%3E)
Hi,
I have my ASP.NET CORE hosted on Azure, the SQLServer DB is also hosted on Azure. Before deploying the Angular front end I decided to test it to see if it would hit the deployed backend and database. I was getting a CORS error but, now that I have resolved that I am getting a 500 error.
Where can I check in Azure to see what the 500 error means?
I am thinking that it might have something to do with the following?
When I published the API using Visual Studio it showed at the bottom that I had 2 dependencies from the code I deployed:
I was able to connect the Azure SQL Database but I can't figure out how to connect to the Microsoft Identity platform. When I click the more ... button to the left it just gives the option to connect but when I click on that it does nothing.
Is there something I need to set up on Azure to configure Identity. I already shared the connection string for the web API with the database.
Here are the web and app log streams:
IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly. <li>IIS was not able to process configuration for the Web site or application.</li> <li>The authenticated user does not have permission to use this DLL.</li> <li>The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.
</li>
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 77%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
Hello @hpbcrowe,Just checking in to see if the provided answer helped. If it did, please click "Accept the answer” and Yes for the answer . So it can benefit other community members reading this thread. If you have any further queries, do let us know.
Hello @hpbcrowe,We still have not heard back from you. Could you please let us know if the answer provided below was helpful? If it resolves your query, kindly click Accept Answer and Yes, as it could assist other community members reading this thread. Additionally, if you have any further questions, please let us know.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
The identity platform configuration is done in entra id where you configure the application. The assumption is you are using msal for angular.
Your 500 error is the application crashing. You appear to be using windows and IIS so the web.config should be configuring the asp.net core hosting module.
I am still investigating I think the problem is that I forgot to change the connection string that is producing my JWT token to take it from the API instead of localhost. I don't have my code set up to switch between development and production, so I am working on making sure the project is still working locally then I will make the changes to my deployed project to see if my thought is correct.
@Bruce (SqlWork.com) I still am having issues with this 500 error. I tried running the app with the Angular Frontend and the ASP .NET CORE backend running locally but connected to the Deployed Azure SQL Server Db.
That worked without any problems.
Using the same Azure SQL Server connection string that worked with both the front end and backend locally, I tried the deployed back end again with the local FE and deployed SQL server DB. I still get the 500.0 error.
I have the Azure Web API IP addresses listed as a rule for the SQL Server DB firewall. I have this box checked Enable Access-Control-Allow-Credentials for CORS. This is what the log stream gives me for the 500 error
Most likely causes:
When I look in the app service editor, it shows a web.config file.
I am using ASP ,NET Core so it uses an appsetting.json not web.config but Azure created one. I don't know need to change my code to use it or not?
Someone else said they got the same error and recommendation from log stream but it turns out they were using the wrong connection string to the DB. I am using the ADO.NET (SQL authentication) connection string.
The two calls that are giving the 500 error are calls that are made to the DB without the user being signed on and authenticated. They populate some of the screen with data from the DB. So, I don't think it would be a problem with the user not being logged in.
if hosting on azure windows, then a web.config is required to configure the asp.net core hosting module.
https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/aspnet-core-module?view=aspnetcore-9.0
your asp.net core app will not use it. see:
https://learn.microsoft.com/en-us/aspnet/core/test/troubleshoot-azure-iis?view=aspnetcore-9.0
ok thank you @Bruce (SqlWork.com)
I finally was able to get my deployed Back End Services to connect to my deployed Azure SQL DB. I did a few things. I am not sure which exact item fixed my 500.0 error I was receiving.
https://learn.microsoft.com/en-us/azure/service-connector/overview
So I deleted all of the service dependencies and any additional files created by publishing to Azure. I discarded the changes in my Git version control in VSCode. I made sure I had the first option connection string for ADO.NET (Microsoft Entra passwordless authentication) I made sure I created an admin in the Microsoft Entra Id following these instructions: Microsoft Entra Id Instructions Then I gave the DB access to it.
I then published that and it worked!