What causes the 'Cannot unregister UpdatePanel' error?

Question

I've got a UserControl that contains an UpdatePanel. When I put that on a page, it throws the following error:

Cannot unregister UpdatePanel with ID 'ReviewContentUpdatePanel' since it was not registered with the ScriptManager. This might occur if the UpdatePanel was removed from the control tree and later added again, which is not supported. Parameter name: updatePanel

ReviewContentUpdatePanel is the name of the update panel & it's not being removed or added in code, it exists in the aspx page and isn't removed. Has anyone come across this before?

Have you got a ScriptManager on the page containing the UserControl? — tvanfosson, Oct 27 '08 at 02:31
Can you post code? Most of the references to this error deal with adding updatepanels/controls dynamically. Is the user control being added dynamically? — tvanfosson, Oct 27 '08 at 03:06
No it's not, it's just sitting on the control in code in front — Glenn Slaven, Oct 27 '08 at 03:10
Yeah but it doesn't change the error if I turn off output caching — Glenn Slaven, Feb 12 '09 at 23:50

score 5 · Answer 1 · answered Feb 24 '09 at 03:02

This error occurs when the Controls collection in which the UpdatePanel is resided is cleared using the Clear method, or when the specific UpdatePanel is removed using the Remove method.

A trigger for these methods could be the implementation of the CreateChildControls method for the control contains the UpdatePanel. Usually, you call Controls.Clear() in the top of this method, to start with a clean slate if this method is called repeatedly.

score 4 · Answer 2 · answered Oct 27 '08 at 15:10

4

Are you moving controls about in code? If so take a look here and see if this solves your problem.

answered Oct 27 '08 at 15:10

DilbertDave

3,406
3
33
42

I'm not moving *anything* around in code, nothing is interacting with the update panel or its containg usercontrol in code – Glenn Slaven Oct 27 '08 at 20:19
Can you post some sample code (if it is not sensitive that is) – DilbertDave Oct 27 '08 at 20:23
Ignore that - i've just seen the comments in the other post. New to SO! – DilbertDave Oct 27 '08 at 20:25

score 3 · Answer 3 · answered Sep 25 '13 at 13:27

I hope this helps someone else as it drove me nuts. After finding various tidbits of info here and there on here and elsewhere, I finally came up with the following fix. Note, I am not dynamically creating this update panel here or anywhere else and most info out there was related to creating this control dynamically, which I was not.

I was using an update panel inside a web user control used on a page inherited by a master page with the script manager. I don't know if this combo was what was causing it, but this is how I fixed it (inside the web user control where the update panel is utilized):

protected override void OnInit(EventArgs e)
{
    ScriptManager sm = ScriptManager.GetCurrent(this.Page);
    MethodInfo m = (
    from methods in typeof(ScriptManager).GetMethods(
        BindingFlags.NonPublic | BindingFlags.Instance
        )
    where methods.Name.Equals("System.Web.UI.IScriptManagerInternal.RegisterUpdatePanel")
    select methods).First<MethodInfo>();

    m.Invoke(sm, new object[] { updatePanel });
    base.OnInit(e);
}

I needed to remove and re-add a user control containing an update panel in some cases. I re-jiggered my code to call something like this method only after re-adding the user control, and it worked. Thanks a million! — user12861, Feb 06 '14 at 20:06

score 3 · Answer 4 · answered Feb 24 '09 at 15:47

3

I had this happen once before. To fix it, I just deleted it and then re-created it and the problem went away.

answered Feb 24 '09 at 15:47

Eppz

3,178
2
19
26

score 2 · Answer 5 · answered Feb 10 '09 at 15:42

2

In your markup, make sure you've specified an ID for both UpdatePanels and for every runat="server" control in their parent hierarchies.

answered Feb 10 '09 at 15:42

teedyay

23,293
19
66
73

score 0 · Answer 6 · answered Feb 27 '09 at 21:21

0

Have you tried including a ScriptManagerProxy in the user control?

answered Feb 27 '09 at 21:21

Dan Monego

9,637
6
37
72

score 0 · Answer 7 · answered May 19 '09 at 19:00

0

Try to remove the scriptproxy of UserControl. In this case you only have a ScriptManager on your page.

answered May 19 '09 at 19:00

Calebe Santos

479
3
7

score 0 · Answer 8 · answered Jun 05 '09 at 19:33

This is a bit of a long shot, but I've had experiences with the AJAX extensions, specifically with the update panel, in which errors thrown by child controls were manifesting themselves as a different error thrown by the update panel. I did see a reference to this specific error being thrown due to an error in a child control:

http://msmvps.com/blogs/shareblog/archive/2009/03/11/cannot-unregister-updatepanel-with-id-since-it-was-not-registered-with-the-scriptmanager-and-moss.aspx

Not sure if this is the case for you or not, but I've spent many hours chasing down the wrong errors because of this.

What causes the 'Cannot unregister UpdatePanel' error?

8 Answers8

Linked