I have created a simple WebAPI application, I am able to "GET", "POST" without any problems.
Whenever I use a "PUT" I keep getting "IIS 7.5 Detailed Error - 500.0 - Internal Server Error".
This works OK on my local machine but not on our hosted web site (through an external provider).
This is the error that i am getting :
Server Error in Application "PORTAL.XXXXX.COM"
Internet Information Services 7.5
Error Summary
HTTP Error 500.0 - Internal Server Error
The page cannot be displayed because an internal server error has occurred
Detailed Error Information
Module LiveStreamingHandler
Notification MapRequestHandler
Handler ExtensionlessUrlHandler-Integrated-4.0
Error Code 0x80070585
Requested URL http://portal.XXXXXXXX.com:80/api/Organisation/4/
Physical Path C:\Inetpub\vhosts\hostingsite\httpdocs\Portal\api\Organisation\4\
Logon Method Bearer
Logon User Administrator
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 http://go.microsoft.com/fwlink/?LinkID=66439
Links and 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.
Related
I have deployed few .net APIs and applications as app service to Azure which is being used internally and also some of them can be called externally. Also have set up an Azure Alert for one of the major app services (let's call it Service A) which sends email notification in case of 404 error.
Looking into AppInsights, I can see some requests that result in 404 error when calling one the services without any endpoint included in the url (service B https://serviceB.mydomain.com/) and of course Service B returns 404 however AppInsights doesn't display the request caller (request referer). To investigate the 404 error I need to know about the caller url.
I'm aware that programmatically I can read request referer but how it can be done for 404 error which caused by a request to an endpoint which doesn't exist moreover some requests may not have referer. How can I log the caller url [preferably in Azure app services/appInsights]?
So far I was not able to find any facility in Azure portal to configure the AppInsights however it can be configured programmatically to track the referer and of course if the request doesn't have referer in the header for some reason, it can not be captured.
This link explains how AppInsight configuration can be done in codes to track the Referer.
UPDATE - And the root of issue:
Turned out "ALWAYS ON" feature in Azure Application Settings was ON for the Service B which means it sends request to the base url to keep it active and avoid recycling. For more info about Always On you can refer to here
One of the main reason for this would be that you might configure the availability test in App Insights
To be particularly this will be a URL ping test
This will hit the configured URL frequently at the location you configured
I have an WAF application gateway in Azure with a backend pool that points to my application. If I visit the gateway address it works and I get the application homepage.
However, if I go to that application and enable PaaS AAD Authentication, which should prompt me with an org login page before getting to my application home page, the gateway stops working and returns message:
502 - Web server received an invalid response while acting as a gateway or proxy server.
There is a problem with the page you are looking for, and it cannot be displayed. When the Web server (while acting as a gateway or proxy) contacted the upstream content server, it received an invalid response from the content server.
When checking backend health I can now see that it is unhealthy, and gives me message:
Probe status code mismatch. Received status code is different from
expected 100-999.
Note that I even changed the range to 100-999, just for testing this out. No idea what could be causing this or how to fix it.
I guess you can try disabling WAF as specified in the comments. Also, I would suggest you to go through this article. https://serverfault.com/questions/882931/azure-ssl-application-gateway-with-web-apps?rq=1
I have implemented azure keyvault in my application and when I disable the Anonymous authentication and Enable te windows authentication in IIS I get the following error.
Server Error in '/' Application. Keyset does not exist 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.Security.Cryptography.CryptographicException: Keyset does not
exist 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.
Please help me to solve this.I am trying this in IIS express and published my application as a new website in IIS.
We are deploying a NodeJS application to production via IISnode. Every time a user tries to log in, they are greeted with a additional login prompt after logging in to the app, which always lead to a nice 401 access denied error.
The response headers for this page are as follows:
Server:Microsoft-IIS/7.5
WWW-Authenticate:Negotiate
WWW-Authenticate:NTLM
X-Powered-By:ASP.NET
Clearly there's some additional windows/iis authentication mechanism, preventing our users from accessing the application. How can I disable this?
I have to find out all logs from IIS log files where we have Authentication Successful messages.
Now I know that status code 200 is for a success message but this code can be returned for any request raised by client.
How can I identify Authentication successful (in my case Windows Authentication to be more specific) events from log files?
IIS access logs won't have successful authentication events, it only logs URL requests, and the account that did the request (if authenticated).
For authentication events for windows authentication, you need to open the "Local Security Policy" snap-in (secpol.msc) on the local computer or by using Group Policy.
Then, go to the Security Settings\Advanced Audit Policy Configuration tree, and in the Logon/Logoff section, configure the Success audit event of "Audit Logon".
More information in Microsoft docs.
Once done, you'll start receiving events in the Windows event viewer, under Windows Logs\Security. They'll appear as event id 4624. Note that this event will appear only when the user is accessing the web application from a different computer. Opening the browser on localhost won't generate that event if the user is logged-in already, which happens when using Internet Explorer.
For Windows authentication, you have to correlate Windows logon audit in system event log and IIS log files. No easy way to get what you want.
https://technet.microsoft.com/en-us/library/cc787567%28v=ws.10%29.aspx