DevelopMENTAL Madness

# 

Hi,

I am suffering from the same issue, rendering testing in IE6 troublesome.

Did you manage to fully fix this issue?

Could you please confirm if this behaviour is unique to 'Multiple IE - ie6' or if the update panel also fails in ie6.

Many thanks. 5/6/2008 6:05 AM | noreply@blogger.com (Gavin)

# 

From everything I've read online this is most definately an issue unique to MultipleIE. My client is a very large multi-national cooporation which is standardized on IE6. They have no complaints with the update panel, just me because I don't have IE6 installed on any machine.

Unfortunatly, there is no fix for this AFAIK. But if I do find anything I'll certainly post it here. 5/6/2008 7:37 AM | noreply@blogger.com (Mark J. Miller)

# 

I found a possible fix for this error while using MultipleIE - IE6. If I execute the request first from IE7, then execute the same request from IE6, it seems to work. 5/27/2008 11:43 AM | noreply@blogger.com (Anonymous)

# 

Anonymous,

Thanks, I tried that and it seems to work. I appreciate you passing on the workaround. 5/28/2008 8:04 AM | noreply@blogger.com (Mark J. Miller)

# 

Your reasoning seems convoluted and backwards to me: "But then I started working on a project which had been developed using the ASP.NET UpdatePanel and IE6 became worthless. "

So the problem is with IE6?? Please consider that the problem lies in Asp.net Ajax/The UpdatePanel and NOT IE6. 8/20/2008 8:59 AM | noreply@blogger.com (Chris M.)

# 

Under normal circumstances, when IE6 is the only version of Internet Explorer installed UpdatePanel works correctly. So the problem is not with UpdatePanel at all. The problem is with how MultipleIEs installs IE6 side-by-side with IE7 (the configuration on my machine).

If you want to split hairs, you are correct to say problem is not with IE6 either. The problem is with MultipleIEs because it is doing something which is not supported by installing multiple versions of IE side-by-side. However, because the problem created by MultipleIEs is due to the inability of Microsoft to meet a real, valid need of developers (browser compatibility testing) I lay the blame with IE and I'll leave my wording as is.

That said, for those who might be confused by my comments I appreciate your clarification on that point.

(Begin Rant) As an aside, do not confuse my comments as an opinion in favor of UpdatePanel. IMHO, it is an aberration. Someone needs to be taken out behind the barn and shot for trying to cram AJAX into the postback model the way it does. AFAIK, its sole purpose is to update the page without the user having to see the page refresh, when in reality that is exactly what is happening anyway. This is not AJAX, this is not even an excuse for AJAX it is bad design and lulls the developer and the user into a false sense of ajaxifying a page. (End Rant). 8/20/2008 9:25 AM | noreply@blogger.com (Mark J. Miller)

# 

I am facing very strange problem. I have web page [http://wms.tlpk.com/pilot].

There is a link button [Get Data] when user set criteria [To selected criteria please select customer NSN(Telenor) and leave all other as it is] and click get data. An update panel post back the page and shows the progress [Receiving Data...] and calls a very complex stored procedure which take about 3 minutes to complete and it cached the data at server in cache bag and in a temporary file. Then it alerts the user to [Refresh Grid] for latest data.

Now the problem is when query take more than 2 minute I got below mentioned message ON SOME CLIENTS [NOT ALL] exactly after 2 minutes. I have set the ServerScriptTimeout/SessionTimeout etc.

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

---------------------------
Microsoft Internet Explorer
---------------------------
Sys.WebForms.PageRequestManagerServerErrorException: An unknown error occurred while processing the request on the server. The status code returned from the server was: 12152
---------------------------
OK
---------------------------

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////




Please follow the steps to produce this error [this might not appear at ur end as i m getting this error on my machine but not at my colleague's]

1) Set Criteria [Select Customer NSN Telenor, nothing else]
2) Click [Get Data] link button
3) Now wait for error or Succuss message

If you have any idea about it please respond I have spend a lot of time to fix it but ................... 10/27/2008 11:49 PM | noreply@blogger.com (Muhammad Amir)

# 

In my experience the error is usually a side effect of another problem. I followed the steps you outlined, but there was no error. I'm using IE7. The query completed in less than 30 seconds. You mentioned setting timeout limits, have you tried the CommandTimeout setting for your stored procedure? 10/28/2008 6:57 AM | noreply@blogger.com (Mark J. Miller)

# 

i found out the actual problem. Whenever any method take more than 60 seconds at server iis returns error.

for example create a web page containing a button a textbox and a label in an update panel
on button click just call a Thread.Sleep with more than 60 seconds it will return an error on some systems

1) run the project
2) enter any number under 60[Seconds] in textbox and call Sleep for this much time it will work fine
3) now enter any number above 70[Seconds] it will give u an error

try with/without update panel 10/28/2008 9:00 PM | noreply@blogger.com (Muhammad Amir)

# 

Have you tried this?

developmentalmadness.blogspot.com/.../...eout.html 10/29/2008 3:41 AM | noreply@blogger.com (Mark J. Miller)

# 

yes i ve tried all the timeouts i ve found this

_____________________________________________________________________________________
Solutions to the problem

first read below
Link to Below Article forums.asp.net/.../>Solutions to the problem
forums.asp.net/.../>First thing, I should mention the fact that I'm running Client Certificates on my server and I never once thought to take those into account. Oops, my mistake.

If the client sends a long HTTP request to the server, the worker process might not get all the information it needs. The process tries to renegotiate the certificates with the client, but the client can't renegotiate because it's still trying to send the rest of the request data. More details are outlined in this article:

technet2.microsoft.com/.../>So I had to go into the IIS Metabase and add two properties under the "LM/W3SVC/" key.

ID NAME DATA TYPE DATA ATTRIBUTES BYTES USER TYPE
6045 UploadReadAheadSize DWORD 65536 IABLE 4 FILE
5521 SSLAlwaysNegoClientCert String true IABLE 8 SERVER

Here's info on UploadReadAheadSize:
technet2.microsoft.com/.../>Here's info on SSLAlwaysNegoClientCert:
www.microsoft.com/.../>Hopefully someone else will find this useful. In the meantime, I'm so glad to put this behind me.
______________________________________________________________________________
______________________________________________________________________________

now the problem is how to do this in IIS 5.0 with Windows 2003 Server and with Windows XP


______________________________________________________________________________
______________________________________________________________________________ 10/29/2008 9:23 PM | noreply@blogger.com (Muhammad Amir)

# 

Thanks for posting the solution 10/30/2008 8:05 AM | noreply@blogger.com (Mark J. Miller)

# 

but for me a problem is still there

______________________________________________________________________________
______________________________________________________________________________

now the problem is how to do this [edit metabase is explained before] in IIS 5.0 with Windows 2003 Server and with Windows XP


______________________________________________________________________________
__________________________________________________ 10/30/2008 9:09 PM | noreply@blogger.com (Muhammad Amir)

# 

I guess I didn't read you post closely enough. Are you using client certificates on the server? Because it didn't seem like it when I visited the site. So I doubt this is the solution for you.

What you need to do is look into the logs on your machine or the server where this is happening and look for any indications of what may be causing this. As I said before this is most likely a server-side problem.

So crack open event viewer and look at the server logs for a clue. Also have you tried debugging the method being called on the server to see what might be happening. Try commenting out the logic of the method and replacing it with System.Threading.Thread.Current.Sleep() and set the timeout to more than 2 minutes. See if that forces the problem to show up consistantly on the client. If not try experimenting with calling the method without using AJAX and see if you can get an error.

Also, if you're using IE you can't see the server error being returned. The error message you're reciveing is a generic client-side error and it doesn't display the actual error response from the server. Try using firefox to see if you can duplicate the problem. If you can you can istall the firebug extension and with the net monitoring enabled you can view the actual server response. If you can't duplicate the problem with firefox you're going to need some tool to monitor the browser's requests/responses. Here's one I googled: www.aptana.com/.../>Either way, you need to find out what the actual error message from the server is. Then you'll be able to track down the problem 11/1/2008 6:53 AM | noreply@blogger.com (Mark J. Miller)