By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,199 Members | 1,440 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,199 IT Pros & Developers. It's quick & easy.

Internet Explorer cannot display the web page

P: 2
I have three dropdownlists on a webpage which I am loading on the pageload under !Ispostback.
After the page is loaded, when I am selecting a value from the first dropdown I am getting an error saying that Internet Explorer cannot display the web page.
When I am debugging through the code, I found out that it is not hitting the page load event at all after selecting the value from the dropdown.
Can someone tell what is the problem.
It is very urgent for me.

Thanks in advance.
Nov 18 '09 #1
Share this Question
Share on Google+
6 Replies

Expert Mod 5K+
P: 9,731
Wow, the page load event is part of the ASP.NET page life cycle.

I don't know how it is not hitting the page load event...unless your page is not valid.
Could you post the code that you are using to populate your DropDownLists?

Nov 19 '09 #2

P: 2
Hi Frinavale,
Thanks for the reply.
Actually what happened was, I have thousands of records that I was trying to populate in the dropdownlist. I guess it has cross the size limit of the dropdown and that's why it was breaking.
I did it in a different way and it is working now.
Anyway do you know what is the size limit of the Dropdownlist. I mean maximum how many rows we can show in a dropdownlist.

Thanks for the reply.

Nov 20 '09 #3

Expert Mod 5K+
P: 9,731
I didn't think there was a limitation on the number of items but that doesn't mean there isn't one.

If you have thousands of items to select from you may want to consider using a different control. I mean, how are people going to find the one thing that they want to select? The DropDownList would be HUGE!
Nov 20 '09 #4

Expert 5K+
P: 7,435
It may be a simple matter, too, of the download time for those thousands of items but there is no limit in the standard and I'm not aware of one in browsers though I wouldn't be surprised if one is set. The error is more indicative of a download timeout.
Nov 20 '09 #5

Expert Mod 5K+
P: 9,731
It's not the download time actually.

The OP was saying that the page is properly loaded in IE the first time the page is sent to the browser. They were complaining that the page wouldn't load upon returning the second round-trip (after the page was submitted when the user selected a value in the first DropDownList...aka HTML <select>).

Actually, you may be right about loading the time it takes to load all of the items though...if the OP had implemented code that added items to the DropDownList that was executed every time the page loads...then it could be that they are loading double the items the second trip.

This may take too much time and/or resources for the server to create the lists and it may never get sent to the browser.

But this doesn't explain why it never hit the Page Load event.

That doesn't make sense...unless the page was not valid and ASP.NET stopped the request before it hit the code. This would mean that the items in the DropDownList were changed somehow client side (or something else is going on to make the page invalid).

Nov 20 '09 #6

Expert Mod 5K+
P: 9,731
I think I might know of another reason this isn't working.

If the worker process for the web application grows to big it will be recycled...
Nov 20 '09 #7

Post your reply

Sign in to post your reply or Sign up for a free account.