How to resolve " a control with id X could not be located or a different control is assigned to the same ID after post back" in asp.net?

Question

Please help me to rectify this error.

An error has occurred because a control with id 'ctl81' could not be located or a different control is assigned to the same ID after post back. If the ID is not assigned, explicitly set the ID property of controls that raise post back events to avoid this error

This error occurred on a post back by an asp button click. All the controls in the page were dynamically generated. I tried to find this control in the page source but in vain.

    HtmlGenericControl td1 = new HtmlGenericControl("td");
    TextBox txt1 = new TextBox();
    txt1.ID = "toqty"+i.Tostring();
    td.controls.add(txt1);
    placeholder.controls.add(td);

How are you selecting them after they're dynamically generated? Code would help :) — tymeJV, Mar 14 '13 at 13:35
dynamically added controls need to be added on each roundtrip (whether on postback or not) and BEFORE event handling if you want them to handle events (best moment for adding dynamically being on init) — jbl, Mar 14 '13 at 13:35

score 3 · Accepted Answer · answered Mar 14 '13 at 13:48

3

Since the error has occured due to a button click, the controls that where generated before the button click might have been cleared from your corresponding form. So i recommend you to check out the methods or codes that were written after the button click by pinning a breakpoint on the button_click() method. Try this and please leave a reply.

answered Mar 14 '13 at 13:48

Rohit Kiran

436
1
5
17

You have another option of using the 'Inspect Element' tool of the browser on which you view the application after debugging. Find the so called 'ctl81' by right clicking on your controls on the web page. – Rohit Kiran Mar 15 '13 at 06:53

score 1 · Answer 2 · answered Mar 14 '13 at 14:15

1

The error itself mentioned the solution. First check whether the ID is still assigned to the control after postback. If not, explicitly set the ID property to avoid this error

answered Mar 14 '13 at 14:15

Microsoft DN

9,706
10
51
71

score 0 · Answer 3 · answered Dec 29 '17 at 10:21

In my case similar exception was caused by a control which had id attribute set up forcibly in Render method, without setting its ID property to the same value.

Apparently, AutoID mode has problems where ID from code behind does not match rendered id attribute.

I preferred not to change Render stage because the control is widely used in a huge project and many functionalities rely on it working as it is. Instead I have set ID explicitly to ensure that it is unique and different from anything that can be set automatically. It helped.

How to resolve " a control with id X could not be located or a different control is assigned to the same ID after post back" in asp.net?

3 Answers3