I can force the error to occure by clicking fast to create postback before the previous ones have finished but I also get the error when use the UI normaly.
I can force the error to occure by clicking fast to create postback before the previous ones have finished but I also get the error when use the UI normaly.
Either way it needs to be fixed.
I too can replicate this behaviour in the same way. Microsoft people... any ideas??
"If you can keep you head while all around you have lost theirs, you clearly haven't understood the seriousness of the situation."
I'm not sure if this will help. I just ran into the same problem. I was able to work around it by placing the updateprogress control outside the updatepanel.
I've found this tends to be the solution with some of the ajax controls. The problem it seems is that the scripts and controls don't always get written at the appropriate times, especially when they are within an updatepanel.
I too had this same problem and even moving the UpdateProgress outside the UpdatePanel did not solve the problem. Only after moving the UpdateProgress outside the UpdatePanel AND setting the AssociatedUpdatePanelID property on the UpdateProgress did the
problem actually go away completely.
My previous post doesn't have all the information about my solution because I didn't realize what exactly was going on. In my situation I had a master page with and UpdateProgress control on it and then on a page based on the master I had another UpdateProgress
control. My previous solution worked because on my master page my UpdateProgress did not have the UpdatePanelID property set and so would fire on every async postback, not just those from the update panel in the master page. So when I changed that and the
UpdateProgress in the child page was already set to watch the UpdatePanel on the child, everything works.
So basically, my problem was that I had two UpdateProgress controls on one page and if you have that, you must specify which UpdatePanel each of the UpdateProgress controls should watch. The UpdateProgress controls will watch all the UpdatePanels and try
to fire at the same time and it seems that the javascript that actually makes them work isn't expecting that.
we need to specify the AssociatedUpdatePanelID="UpdatePanel1" and also UpdateMode="Conditional" if this updatepanel is not refreshed with other updatepanel triggers
Figure this one out then.... I got this error on the first reload event (either clicking a button or checking a box with postback) - when I commented out a response.redirect line (that was in another block of code and not even run) the problem vanished!
TheInternet
Member
119 Points
46 Posts
Re: 'this.get_element().style' is null or not an object
Feb 16, 2007 03:49 PM|LINK
As far as i can see, the error happens because another async postback is starting before the last has finished.
Did anyone find a proper solution to this?
AndrewSeven
Contributor
2184 Points
437 Posts
Re: 'this.get_element().style' is null or not an object
Feb 16, 2007 04:17 PM|LINK
I can force the error to occure by clicking fast to create postback before the previous ones have finished but I also get the error when use the UI normaly.
Either way it needs to be fixed.
TheInternet
Member
119 Points
46 Posts
Re: 'this.get_element().style' is null or not an object
Feb 19, 2007 10:34 AM|LINK
okulair
Member
4 Points
2 Posts
Re: 'this.get_element().style' is null or not an object
May 16, 2007 07:57 PM|LINK
I had the same problem.
I tried this solution and it worked perfectly.
Thanks.
edit: added quote
jjepen
Member
81 Points
61 Posts
Re: 'this.get_element().style' is null or not an object
May 27, 2007 09:57 PM|LINK
I too had this same problem and even moving the UpdateProgress outside the UpdatePanel did not solve the problem. Only after moving the UpdateProgress outside the UpdatePanel AND setting the AssociatedUpdatePanelID property on the UpdateProgress did the problem actually go away completely.
jjepen
Member
81 Points
61 Posts
Re: 'this.get_element().style' is null or not an object
May 30, 2007 01:00 AM|LINK
My previous post doesn't have all the information about my solution because I didn't realize what exactly was going on. In my situation I had a master page with and UpdateProgress control on it and then on a page based on the master I had another UpdateProgress control. My previous solution worked because on my master page my UpdateProgress did not have the UpdatePanelID property set and so would fire on every async postback, not just those from the update panel in the master page. So when I changed that and the UpdateProgress in the child page was already set to watch the UpdatePanel on the child, everything works.
So basically, my problem was that I had two UpdateProgress controls on one page and if you have that, you must specify which UpdatePanel each of the UpdateProgress controls should watch. The UpdateProgress controls will watch all the UpdatePanels and try to fire at the same time and it seems that the javascript that actually makes them work isn't expecting that.
chetan.sarod...
All-Star
66589 Points
11270 Posts
Re: 'this.get_element().style' is null or not an object
May 30, 2007 03:27 AM|LINK
I am also facing the same problem...Here I tried the solution as,
Try to set UpdateProgress outside the UpdatePanel .
then set the AssociatedUpdatePanelID property on the UpdateProgress
Hope this will solve your problem..[:)]
Senior Software Engineer,
Approva Systems Pvt Ltd, Pune, India.
vivekak
Member
6 Points
3 Posts
Re: 'this.get_element().style' is null or not an object
Jun 14, 2007 06:45 AM|LINK
we need to specify the AssociatedUpdatePanelID="UpdatePanel1" and also UpdateMode="Conditional" if this updatepanel is not refreshed with other updatepanel triggers
this has solved the issue for me
jfierst
Member
137 Points
261 Posts
Re: 'this.get_element().style' is null or not an object
Dec 14, 2007 02:52 PM|LINK
This solved my issue as well. I had placed the UpdateProgress within the UpdatePanel, just take it outside of that and you're golden.
gchq
Member
119 Points
126 Posts
Re: 'this.get_element().style' is null or not an object
Jan 02, 2008 03:38 PM|LINK
Figure this one out then.... I got this error on the first reload event (either clicking a button or checking a box with postback) - when I commented out a response.redirect line (that was in another block of code and not even run) the problem vanished!