I have created an ASP.Net Core API following exact steps as the document below and published to Azure. The WeatherForcast function works fine as expected, but none of the other methods working.in the link https://docs.microsoft.com/en-us/aspnet/core/tutorials/publish-to-azure-api-management-using-vs?view=aspnetcore-5.0
Errore messge is this:
HTTP/1.1 500 Internal Server Error
I get the same erroer when tested with Postman with or without Ocp-Apim-Subscription-Key. But it's not giving any extra details of the error.
The same API when I published to one of our internal servers with IIS works fine and we can retrieve data. Only difference is we are not using the version part "v1" added by Swagger.
We are using an on-prem SQL server for the API. Connection String is added in the Databases section in the Web Publish/Deploy and checked to "Use this connection string at runtime".
I have posted some screenshots here, but please ask if you need any more details.
My startup.cs having below added:
ConfigureServices:
services.AddSwaggerGen(c => { c.SwaggerDoc("xxxxxapi", new OpenApiInfo { Title = "XXXXX API", Version = "v1" }); });
Configure:
app.UseSwagger();
I am not sure if this is an error with either of these: Azure Configuration, Database Connection (same works fine when hosted on-prem IIS), Swagger or anything else. Can someone please direct me with troubleshooting options at least. Screenshots:
Azure Response
Azure Publish Profile of VS 2019
VS Publish Output
WeatherForcast response - Works fine
1.4m articles
1.4m replys
5 comments
56.9k users