Activities of "ashjackson"

Hi, Thankyou, this resolved my issue.

AJ.

Thankyou, this will be very useful.

Hi There, A further question to this point, how do the values from appconfig.json get assigned to their partners in AppConsts.ts? If I wanted to add my a new value to AppConsts which is defined in appcondig.json, can I simple add to both files, or is there another class which reads in and assigned the values?

Kind Regards, AJ.

I've tried this approach too, but had the same issue too, I had assumed I'd not understood correctly the process and parked this for later investigation, so I would be interested to see the "correct" way to upload images in this way is.

AJ.

Hi There,

My post above is taken from the log.txt in verbose level. However, I have since re-deployed into a fresh net50 preview webapp and it has worked with the framework-dependant option set in the publish wizard.

I am starting to think this is not a problem in ASPZ, but a issue with the preview version of net50 in azure, so if you cannot duplicate the issue we should close this ticket for now I think.

Kind Regards, AJ.

Hi There,

I am having this issue as well, in dev imperonsation works, but in live i get a 500.

I've dug in the log and it appears to be a problem with CORS

2021-02-02 12:40:00.657 +00:00 [Information] Microsoft.AspNetCore.Hosting.Diagnostics: Request starting HTTP/1.1 OPTIONS https://my.api.url/api/TokenAuth/ImpersonatedAuthenticate?impersonationToken=adf9571e-2776-472f-a2dc-273e7842df87&d=1612269598634 - 0
2021-02-02 12:40:00.657 +00:00 [Debug] Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware: OPTIONS requests are not supported
2021-02-02 12:40:00.657 +00:00 [Debug] Microsoft.AspNetCore.Routing.Matching.DfaMatcher: 1 candidate(s) found for the request path '/api/TokenAuth/ImpersonatedAuthenticate'
2021-02-02 12:40:00.657 +00:00 [Debug] Microsoft.AspNetCore.Routing.EndpointRoutingMiddleware: Request matched endpoint '405 HTTP Method Not Supported'
2021-02-02 12:40:00.657 +00:00 [Debug] Microsoft.AspNetCore.Cors.Infrastructure.CorsService: The request has an origin header: 'https://my.angular.url'.
2021-02-02 12:40:00.657 +00:00 [Information] Microsoft.AspNetCore.Cors.Infrastructure.CorsService: CORS policy execution successful.
2021-02-02 12:40:00.657 +00:00 [Debug] Microsoft.AspNetCore.Cors.Infrastructure.CorsService: The request is a preflight request.
2021-02-02 12:40:00.657 +00:00 [Information] Microsoft.AspNetCore.Hosting.Diagnostics: Request finished HTTP/1.1 OPTIONS https://my.api.url/api/TokenAuth/ImpersonatedAuthenticate?impersonationToken=adf9571e-2776-472f-a2dc-273e7842df87&d=1612269598634 - 0 - 204 - - 0.3916ms
2021-02-02 12:40:00.694 +00:00 [Information] Microsoft.AspNetCore.Hosting.Diagnostics: Request starting HTTP/1.1 POST https://my.api.url/api/TokenAuth/ImpersonatedAuthenticate?impersonationToken=adf9571e-2776-472f-a2dc-273e7842df87&d=1612269598634 application/json 0
2021-02-02 12:40:00.694 +00:00 [Debug] Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware: POST requests are not supported
2021-02-02 12:40:00.694 +00:00 [Debug] Microsoft.AspNetCore.Routing.Matching.DfaMatcher: 1 candidate(s) found for the request path '/api/TokenAuth/ImpersonatedAuthenticate'
2021-02-02 12:40:00.694 +00:00 [Debug] Microsoft.AspNetCore.Routing.Matching.DfaMatcher: Endpoint 'MSystem.Web.Controllers.TokenAuthController.ImpersonatedAuthenticate (MSystem.Web.Core)' with route pattern 'api/TokenAuth/ImpersonatedAuthenticate' is valid for the request path '/api/TokenAuth/ImpersonatedAuthenticate'

Can this be enabled by editing the web.config?

Kind Regards, AJ.

Hi,

I've also updated to 10.2 and the same problem occurs. I've also downloaded a fresh 10.2 project and deployed that and the same error results.

Hi, Just to confirm, this has happened again when deploying to a new Azure app service with 10.1. I set the log streaming to verbose but get nothing more than the IIS error message

HTTP Error 500.30 - Internal Server Error The page cannot be displayed because an internal server error has occurred. Most likely causes:

• IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred.
• 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.
• IIS was not able to process configuration for the Web site or application.
• The authenticated user does not have permission to use this DLL.
• The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.

Things you can try:

• Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.
• Check the event logs to see if any additional information was logged.
• Verify the permissions for the DLL.
• Install the .NET Extensibility feature if the request is mapped to a managed handler.
• Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>.

More Information: This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.<p><a href="http://go.microsoft.com/fwlink/?LinkID=62293&amp;IIS70Error=500,30,0x8007023e,14393">

My other site when left overnight, just started working so I'm at a loss to point to what might be wrong here. I see others are reporting the same problem - have you been able to recreate the issue?

AJ.

Frustratingly, this error isn't happening today. The only thing that could have changed is that the app-service will have timed out and shutdown overnight (it's on the shared hosting for dev purposes, so spools down when not in use).

I see I'm not the only person who's seen this, so shall we leave this thread open for a bit as I'll be deploying a lot in the next week or so and I'll see if I can catch the cirumstances required to produce this issue and capture the log.

Kind Regards, AJ.

Hi There, The newest power tools version has resolved this problem. The additional module id field is no longer required.

Thanks.