"Unexpected error" when running a pop up on the Enterprise Portal for the first time


While opening pop up you can get error after running AXUpdatePortal:

Server Error in ””/”” Application.——————————————————————————–
Cannot unregister UpdatePanel with ID ”g_04b24860_ce58_4786_a03e_277a946e8eb1_content” 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
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ArgumentException: Cannot unregister UpdatePanel with ID ”g_04b24860_ce58_4786_a03e_277a946e8eb1_content” 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

The problem happens when the page which comes as pop up does not include AxInfolog web part. Then Enterprise Portal framework adds the web part to the page definition in a default zone. It happens that then web part is added to a zone which is not supported by page template and then we get error. Somehow the second time when you open pop up the page behaves better and the error is not shown anymore. To work around this problem you can add AxInfolog to page definition of your pop up.

image

–author: Czesława Langowska
–editor: Czesława Langowska
–date:

6/July/2011


Comments (2)

  1. John Francis Burke says:

    Hello,

    I have an open support call with Microsoft for exactly this error.

    Unfortunately my web page already includes a Dynamics Infolog WebPart in the header.

    What else could cause this problem?

    Thanks,

    John.

  2. EMEAAXTec says:

    Hello John,

    The support call is very good approach. Our support team will work with you to find the best solution here.

    I think we would need to go much more deeper into the issue and maybe even debug it. The support engineer will walk you trough the problem.

    Kind regards

    Czesława Langowska