Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Unable to edit pages after upgrading to 9.1.1Unable to edit pages after upgrading to 9.1.1
Previous
 
Next
New Post
1/19/2018 4:00 PM
 

We have a historic DNN solution with a few custom modules that was running on v7.3.4.

We've upgraded it in line with the documentation > v7.3.4 > v8.0.3 > v8.0.4.226 > v9.0.0.1002 > v9.0.1.142 > v9.0.2 > v9.1.0.367 > v9.1.1.129-232

Since upgrading we are presented with an error message when on a page containing one of our module:

Server Error in '/' Application.

Cannot unregister UpdatePanel with ID 'DocMap' 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 'DocMap' 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

Source Error: 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace: 

[ArgumentException: Cannot unregister UpdatePanel with ID 'DocMap' 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]

   System.Web.UI.PageRequestManager.UnregisterUpdatePanel(UpdatePanel updatePanel) +222

   System.Web.UI.UpdatePanel.OnUnload(EventArgs e) +121

   System.Web.UI.Control.UnloadRecursive(Boolean dispose) +141

   System.Web.UI.Control.UnloadRecursive(Boolean dispose) +355

   System.Web.UI.Control.UnloadRecursive(Boolean dispose) +355

   System.Web.UI.Control.UnloadRecursive(Boolean dispose) +355

   System.Web.UI.Control.UnloadRecursive(Boolean dispose) +355

   System.Web.UI.Control.UnloadRecursive(Boolean dispose) +355

   System.Web.UI.Control.UnloadRecursive(Boolean dispose) +355

   System.Web.UI.Control.UnloadRecursive(Boolean dispose) +355

   System.Web.UI.Control.UnloadRecursive(Boolean dispose) +355

   System.Web.UI.Control.UnloadRecursive(Boolean dispose) +355

   System.Web.UI.Control.UnloadRecursive(Boolean dispose) +355

   System.Web.UI.Control.UnloadRecursive(Boolean dispose) +355

   System.Web.UI.Control.UnloadRecursive(Boolean dispose) +355

   System.Web.UI.Control.UnloadRecursive(Boolean dispose) +355

   System.Web.UI.Control.UnloadRecursive(Boolean dispose) +355

   System.Web.UI.Control.UnloadRecursive(Boolean dispose) +355

   System.Web.UI.Control.UnloadRecursive(Boolean dispose) +355

   System.Web.UI.Control.UnloadRecursive(Boolean dispose) +355

   System.Web.UI.Control.UnloadRecursive(Boolean dispose) +355

   System.Web.UI.Control.UnloadRecursive(Boolean dispose) +355

   System.Web.UI.Page.UnloadRecursive(Boolean dispose) +24

   System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +12361809

   System.Web.UI.Page.ProcessRequest() +119

   System.Web.UI.Page.ProcessRequest(HttpContext context) +99

   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +913

   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +165

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.36415

Checking online indicates - http://www.dnnsoftware.com/forums/threadid/539307/scope/posts/problems-by-using-of-updatepanel-in-dnn9

Directing you to register the UpdatePanel with ScriptManager prior to it unloading it:

protected void UpdatePanel_Unload(object sender, EventArgs e) {
    MethodInfo methodInfo = typeof(ScriptManager).GetMethods(BindingFlags.NonPublic | BindingFlags.Instance)
        .Where(i => i.Name.Equals("System.Web.UI.IScriptManagerInternal.RegisterUpdatePanel")).First();
    methodInfo.Invoke(ScriptManager.GetCurrent(Page),
        new object[] { sender as UpdatePanel });
}

How ever this would require changing the DNN source files and building the solution myself which doesn't seem the correct approach to take considering that this change would need to be edited into each new revision of the DNN framework.

 

Has anyone experienced this issue themselves? If so how did you correct it?

 
New Post
1/21/2018 12:50 AM
 
This may be related to the fact that the Telerik editor is removed in DNN 9.1.1 and you may need to specify the new editor.

To do this, in the Persona Bar, go to the Settings (gear icon) page and click Site Settings. Go to the More tab and click "Open HTML Editor Manager" and select DNNConnect.CKE as the editor.



Joe Craig
Patapsco Research Group, Ellicott City, MD
DotNetNuke Development and Services (http://patapscorg.com)
 
New Post
1/26/2018 11:20 AM
 
Progress! Unfortunately it wasn't as easy as changing the HTML editor.
I've narrowed down the issue to the inclusion of the following on a control:
ID="ReportViewer1"
runat="server"
ProcessingMode="Remote"
height="100%"
Width="100%"
SizeToReportContent="true"
BackColor="White"
InternalBorderStyle="Solid">


If I comment out all the C# code and just leave the above it still produces the error when any page including the module is loaded.
I'm going to try updating the .dll files to the 2016 and see if that alleviates the issue.
 
New Post
1/26/2018 11:29 AM
 

Further to your suggestion I've changed the HTML editor for the site to DNNConnect.CKE, however the issue persists.

I've narrowed the issue down to one module and a control on a single page:

<rsweb:ReportViewer ID="ReportViewer1" runat="server" ProcessingMode="Remote" height="100%" Width="100%"  SizeToReportContent="true" BackColor="White" InternalBorderStyle="Solid"> </rsweb:ReportViewer>

 

I've commented out this and the referencing code and the pages including the module are now editable.

Just by uncommenting the above control on the .aspx the error returns so it looks to be a compatibility between the ReportViewer and DNN v9.0.0 upwards.

I'm going to try updating the version of ReportViewer we are using to 2016 and see if this corrects the issue.

 
New Post
1/30/2018 3:14 PM
 
Unfortunately the updated ReportViewer did not correct the issue.
I have tried adding removing the ReportViewer from the page and adding an iFrame to the bbc website, this worked correctly.
I have updated the src of the iFrame to point directly to the report URL and again this produces the same error message when trying to edit the page in admin mode.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Unable to edit pages after upgrading to 9.1.1Unable to edit pages after upgrading to 9.1.1


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out