Member Avatar for ansari.wajid

I am getting "The connection was reset" error on my live server but its working okay on my local server. The thing is that I am having a drop down on a page, When the page is loaded drop down is filled with 2 values in it, I am able to select a value in the drop down and it is loading the content in all the other controls on the page based on the selected value of the drop down, Until here every thing seems okay. The problem erupts when I try to select a different value from the drop down, It is unable to connect to the server and showing "The connection was reset" error.
Please let me know what might have making this happen.

Thanks in advance.

  • 3 Contributors
  • 5 Replies
  • 129 Views
  • 4 Days Discussion Span
  • Latest Post Latest Post by finito

Dani AI

Generated

Brief diagnostic checklist for "The connection was reset" when a postback works locally but fails on the live server. That browser message means the TCP connection was closed before the browser received a full HTTP response. Because the failure only happens when selecting the second dropdown value, focus on differences in the code path triggered by that value and on production-only factors (IIS, network appliances, DB load). , a minimal repro will save time; is right to ask for a smaller example.

Start here (quick, prioritized steps):

  • Check IIS logs (%SystemDrive%\inetpub\logs\LogFiles) for the exact request time, sc-status, sc-substatus and sc-win32-status. Non-200 status or a win32-status like 64/121/123 can point to connection/socket problems or timeouts.
  • Turn on IIS Failed Request Tracing (FREB) for that URL and reproduce the error to capture a detailed trace.
  • Inspect Windows Event Viewer (Application/System) for w3wp crashes, .NET runtime errors, or app-pool recycles at the same timestamp.
  • Use browser devtools or Fiddler to capture the POST: note whether the request is sent, how long it runs, and whether the server sends headers before the reset.
  • Temporarily add try/catch around the dropdown handler to log exceptions and progress to a safe file in App_Data or to EventLog (remove/secure logging after diagnosis). Example:
    protected void DropDownList1_SelectedIndexChanged(object s, EventArgs e)
{
  try
  {
      // existing logic
  }
  catch (Exception ex)
  {
      System.IO.File.AppendAllText(Server.MapPath("~/App_Data/errors.txt"),
          DateTime.UtcNow + " - " + ex.ToString() + Environment.NewLine);
      throw;
  }
}

    Also check long-running DB queries with SQL Profiler, viewstate/response size in the browser, and front-end timeouts (load balancer, proxy, antivirus). If a tiny test page that mimics the failing path works on live, add back logic incrementally until it breaks; then post the IIS log line, event-log entry, and any stack trace for targeted help.

Recommended Answers

All 5 Replies

Member Avatar for finito

It would be nice If I was telepathic then I could magically see your code and tell you the problem. But Alas, I am not one so I will need you to show me your code. ;)

Member Avatar for ansari.wajid

It would be nice If I was telepathic then I could magically see your code and tell you the problem. But Alas, I am not one so I will need you to show me your code. ;)

Unfortunately you must have to use telepathy to see my code because its of 1500 lines in code behind and 800 lines of code in design view... ;)

Member Avatar for finito

Well As I said I am not one so I can't help you.

Member Avatar for guest12

What a useless piece of exchange.

Member Avatar for finito

Tell me about it.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.