393
Views
7
Comments
Connection to the error was reset. Server returned status error.
Question
Hi All,

Can someone help me on what causes this kind of error??



Thanks and Regards,

Regie
2024-06-12 10-07-10
Daniel Martins
Hi, Regie.

Where do you get this error?
You can trace the error using FireBug (Firefox plug in). Should be enough at least to understand from where this error it's trigged.

Hope it helps you.

Kind regards.

Daniel Martins.



UserImage.jpg
Diana Mae Benitez
Hi Daniel,

Im in the same team as regie, can you further explain this error or the probable cause, and what can we do to fix this error.




thanks,
diana
2024-06-12 10-07-10
Daniel Martins

It looks like a networking issue, nevertheless you can get some feedback from OS support.

Do you notice other network communication problems in other applications on the same server?

Kind regards
2019-11-12 17-31-26
Justin James
 
MVP
This is NOT a networking error. I can CONSISTENTLY produce this error while running on one of my production servers addressing 127.0.0.1. When I got it on my client, I had Chrome tools and Fiddler open, and all requests made by the client came back with a proper 200 status.

J.Ja
2024-06-12 10-07-10
Daniel Martins

Hi Diane, Regie and Justin.


I heard it through the grapevine, but this issue might be related with this bug fix, avaialable on version 8.0.0.24
  • Fixed Feedback Message error when navigating to a different URL while a AJAX request is being processed (#590137)

You should consider upgrade to the latest revison available. It would be great to have your feedback.


2015-09-28 00-04-44
Pedro Coelho
Hi,

I had the same error after updating to version 8.0.1.7, then I made the update to 8.0.1.8 and still had the same problem.
In my case I verified that the url was being poorly detected, the webscreen was detected "/page" instead of "/page.aspx", after changing the name of the webscreen the situation was resolved

Pedro C.
 
2021-07-07 13-36-32
Hans Dollen
Hi,

I haven't seen it in our own applications since the 8.0.1.7 upgrade. 
I had the error last Friday in the outsystems support portal. But I forgot to inspect the chrome dev-kit.


Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.