I have service running on IIS server written in .net compiled on 32 bit.
After processing few apis I start getting below log on my java application
org.springframework.web.client.ResourceAccessException: I/O error on POST request for "http://* Connection reset; nested exception is java.net.SocketException: Connection reset
and IIS server throws exception as below image
Apart from this I am also getting at some other point of time
400 Bad Request
without any exception on IIS server.
You shouldn't have Visual Studio installed on a production WebServer. I would first uninstall Visual Studio and if that popup remains, remove Just-In-Time debugging. This will allow the exceptions in your application to flow as they should. Once that happens, verify you are still getting the same error messages and check the Windows Application Event Log for additional information.
Related
I have an issue with a web service I call from my .NET application.
The web service is on two different servers, one for testing and one for development. On test environment it works fine, but on development I get empty response.
When I call the service on the development server from Postman I get the correct response.
I checked the config file, is correct, I even copy/paste the Postman code as is and run it but I still get empty response. The code is correct because it works ok on testing environment.
I use the framework 4.7.2 but on the server's event viewer I get this message "A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 70."
Any idea what might be wrong and how to fix it?
Thank you in advance
I am trying to run Chrome lighthouse on my production server. It stops returning error saying Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403).
It is working fine in my local and staging setup servers. Servers hosted on AWS and cloudflare as firewall
As stated on this page
A common cause of failures is Lighthouse being blocked by bot detection or DDOS protection software, resulting in a 403 error. This can be resolved by allowing web traffic with the "Chrome-Lighthouse" user-agent string.
This is kind of frequent problem developers faces during production on a server with higher loading time, to summarize:
It occurs because of the following issues:
Unresponsive server
Unstable/Slow internet connection.
Please try to rerun the test then it will work.
i have a problem with the the vsphere web client when i open it it shows me this error.
"[400] An error occurred while sending an authentication request to the vCenter Single Sign-On server - An error occurred when processing the metadata during vCenter Single Sign-On setup - AFD Native Error Occured: 9127."
i dont understand what is happening can any one explain to me the reason behind this error and how to fix it
thank you
For deploying my website in server by using IIS 5.1,,i created virtual directory,,i browsed in to my application and selected
asp.net 2.0 tab(application is framework3.5)..I reset framwork configuratio 2,0 Runtime security Policy Enterprise,Machine,User
tab,,What ever things i can do i did
Still also application is working properly,,but i am not able to deploy it in IIS
i am getting this error
If i browse Login.aspx i am getting
**
Server Application Unavailable
The web application you are attempting to access on this web server is currently unavailable. Please hit the "Refresh" button in your web browser to retry your request.
Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.
**
Is it with IIS 5.1??
Here my machine is acting as server ,It has xp professional 2002 service pack 2 and IIS 5.1
Any body knows how to create application pool in IIS 5.1
I don't think you can ... Creating Application Pools in IIS
IIS 5.1 and earlier: The AppCreate3
method, the IIS WMI provider, and
Application pools are not available,
and therefore this topic does not
apply.
I'm maintaining web server software on which users can deploy web applications. Web applications run as separate processes: the web server launches a web application process, forwards the HTTP request to the web application, and forwards the web application's response back to the HTTP client. The communication between the web server and the web application happens through sockets.
Some users (= web application developers) report that they occasionally get mysterious EIO errors when they write to the socket that connects their web application to the web server (at least, they think it's writing to the socket that causes the error). Some others report that they get this error as well when writing something to STDERR (which is redirected to a log file). Restarting the web server and the web application "fixes" this problem for a short period of time.
What does EIO mean? I know the manual says "Input/output error" but this description is as vague as it can get. Under what circumstances can it occur and how is it different from ECONNREFUSED/EPIPE/ENOTCONN/etc?
Well, apparently EIO can occur when trying to write to a disconnected console device.