views:

24

answers:

1

Hello,

I got a strange issue after hosting the my site in IIS 7.5, Windows server 2008 64 bit

The applicaion is created in ASP.Net 2.0

The page with issue has following workflow:

  1. Upload a file from browser (may be very large size ~50 MB)
  2. Perform some process (May take very long time: up to 30 minuits)
  3. Notifies the client that process is done.
  4. During the process client uses something like http://www.codeproject.com/KB/session/Session_Defibrillator.aspx to keep the session alive.

The Issue: The client does not get any response sent by my code after the process is over. It should refresh the page with the response provided by my code. But instead it only shows waiting for... in the status bar.

I have tried this on IE and firefox.

To veryfy the process is over

  • I have added some trance message in my code to check when the process gets finished.
  • I have also checked the Log from IIS, it also shows that response sent with Code 200.

Please help me solving this issue:

  • What could be the issue?
  • How can I diagnose and fix this problem?
  • In what cases connection between browser and IIS server gets lost?

Please let me know if I need to provide some more information

Thanks in advance

A: 

Hello Peter,

Thanks for analyzing the issue.

There is a Label () in the page which is used to show messages/errors.

I am just setting the Text property to the success message when the process gets finished.

Full postback is happening during this type of request so any change in the page controls on the server side is reflected to client browser when server sends response back to client. But the issue is the response is not reaching back to client browser.

Regards

HBA
In above comment Label () means ASP:Label control where I am setting lblMessage.Text = "Process finished Successfully";
HBA
Hello, I tried this from the server and used http://localhost/.. and I found that it has worked properly, It shows the message to client. After that I checked IIS event log again and found that when I try locally it gives "sc-win32-status = 0" and when I try remotely it gives "sc-win32-status = 121". Is this can be an issue?
HBA
What causes "error code 121:The semaphore timeout period has expired" ? I found error code 121 in IIS logs.
HBA