Last post Sep 20, 2009 09:29 PM by rmdw
Sep 18, 2009 06:53 PM|rmdw|LINK
I've deployed a few simple AJAX-enabled web page to a local server that is accessed through the Internet by just two people: Me & one client.
When running in VS2008 it works perfectly fine but when accessed through this server there are frequent and mysterious timeouts. There appears to be no pattern to when & why they occur. Sometimes I get strange errors with codes in the 40000 & 50000 range.
Other times it just hangs. There is so little load on this server that I do not understand why this is occurring.
I'm wondering if anyone else has experienced something similar and might have some tips for me about how to resolve it?
Sep 18, 2009 07:32 PM|kwanann|LINK
There can be many reasons for the timeout, what i suggest is to install fiddler, then browse the site via IE as per normal with fiddler acting as the proxy in between. then attach the fiddler results along with the iis log for us to help you with the troubleshooting
Sep 18, 2009 09:11 PM|rmdw|LINK
I just did what you requested. It took just a few clicks before I received this error: Sys.WebForms.PageRequestManagerServerErrorException: An unknown error occurred while processing the request on the server. The status code returned from the server was:
I'm not sure what info from Fiddler you'd like. Could you be more specific?
Sep 19, 2009 02:24 AM|kwanann|LINK
Based on http://support.microsoft.com/default.aspx/kb/193625, you seem to be having a
The server response could not be parsed issue.
Common causes of this includes you doing a response.write somewhere inside the code behind.
Take a look at the fiddler trace, and find the entry which has the partial postback. Click on Inspectors -> and then textview for the bottom section, see if there's any wierd text there.
if you can't tell, kindly paste the whole textview content here for so that we can assist you
Sep 19, 2009 05:47 PM|rmdw|LINK
I did what you said. I had to click on a few nodes of the treeview that's the main navigational component on the page. But sure enough the same Error 12152 soon occurred. As per your instructions,
here is the Textview data in Fiddler.
Does it reveal anything to you?
Sep 19, 2009 08:48 PM|kwanann|LINK
hmm so it never happens on the first postback, but rather on subsequent postbacks?
possible to post the code up to see? i'm suspecting its something to do with your viewstate or treeview event handling
Sep 19, 2009 08:55 PM|rmdw|LINK
The code is way too involved for the intended scope here. The biggest mystery to me is why this only occurs in the deployed version and not when running the VS2008 version? Also, why does it only occur once in a while?
Thank you for trying to help. I think what I'm gong to do now is advertise on the Craigslist Gigs section of the Vancouver forum (where I live) to find an ASP.Net guru to hire to help out with this problem and several others that stump me from time to time.
Once again, thank you for your efforts!
Sep 19, 2009 09:36 PM|kwanann|LINK
hmm i've been meaning to ask you, what exactly do you mean when you say running the vs2008 version?
is there any differences between the deployed server as compared to the "vs2008" server?
one thing you can try is to store your viewstate in session state and see how it goes :)
Sep 19, 2009 11:11 PM|rmdw|LINK
I meant that when I'm running the code locally within the Visual Studio 2008 environment (ie. in Debug mode) that I never have such problems. It's only when I deploy the application to my test server that such problems arise.
FYI my test server is running Windows XP and IIS is version 5.1.
Incidentally, I just tried something new: I went onto my test server, brought a browser, and ran the app directly from there. This means that I was not going out to the Internet and the coming back in again. Doing this, I had NO problems. Does this indicate
to you what the problem might be?
Sep 20, 2009 08:07 AM|kwanann|LINK
hmm Windows XP?
any chance of running it of windows server or vista and above? because windows XP has a 10 connection limit, not sure if that's what's causing the problem.
nb: if its the 10 connection limit, assuming you are the only person connecting to the system, you should get it in about 4 to 5 clicks
Sep 20, 2009 12:21 PM|rmdw|LINK
Can't upgrade right now but WOW, I think you've hit the nail on the head! I investigated this somewhat and found this: http://www.tomshardware.com/forum/4956-45-connection-limit
I bumped up the connection limit to 39 and now the problem *seems* to have disappeared. More testing is clearly necessary but so far, so good.
Thank you SO MUCH!!!
Sep 20, 2009 08:35 PM|kwanann|LINK
Well when you mentioned XP that pretty much came to mind as the 10 connection limit was what got alot of people into trouble back then, that's why Vista and Win7 removed the connection limit :)
hmm that also means the fiddler trace you gave me initial is the one which was working rather than the one which had error, that's why i was unable to troubleshoot it correctly.
in this case, if you want to replicate the problem, put in the 10 connection limit, run fiddler and when you get the error, look at the last fiddler record, instead of the whole bunch of updatepanel postback, you should see a http error page, that's why
ajax said there was a problem with the postback
moving on, you may want to use Win Server, Vista or Win7 as the dev server instead, because these are closer to actual prod systems, otherwise you may end up spending time running around fixing unneccessary problems !
Sep 20, 2009 09:29 PM|rmdw|LINK
No, what I gave you was indeed the Fiddler trace from the event where everything hung up.
FYI the "test server" I have is just an old P4 machine I had lying around. I use it mostly to test this one client app, and let him do the same. Having a slower machine on a slower connection perhaps better simulates what will occur on the client's site
in Northern Canada with a faster machine but a not so fast network. And now that the connection problem *appears* to be resolved, it should work just perfectly for my [very limited] needs.
Thank you again!