Developer forum

Forum » Ecommerce - Standard features » Viewing Users in backend

Viewing Users in backend

E-mail notifications
Terri Donahue
Terri Donahue
Reply
Posted on 15/06/2020 17:08:58

Hi guys,

We are getting this error when trying to view any user in the backend.This site was upgraded to Dw 9.8.7 then rolled back to 9.8.6.

Server Error in '/' Application.

Method not found: 'System.String Dynamicweb.SystemTools.Gui.LinkManager(System.String, System.String, System.String, System.String ByRef, System.String ByRef, Boolean ByRef, Boolean ByRef, Boolean, System.String ByRef, Boolean ByRef, Boolean ByRef, Boolean, LinkManagerSettings, System.String, System.Web.UI.AttributeCollection, Boolean, System.String)'.

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.MissingMethodException: Method not found: 'System.String Dynamicweb.SystemTools.Gui.LinkManager(System.String, System.String, System.String, System.String ByRef, System.String ByRef, Boolean ByRef, Boolean ByRef, Boolean, System.String ByRef, Boolean ByRef, Boolean ByRef, Boolean, LinkManagerSettings, System.String, System.Web.UI.AttributeCollection, Boolean, System.String)'.

Source Error:
 

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

  <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.


Stack Trace:
 

[MissingMethodException: Method not found: 'System.String Dynamicweb.SystemTools.Gui.LinkManager(System.String, System.String, System.String, System.String ByRef, System.String ByRef, Boolean ByRef, Boolean ByRef, Boolean, System.String ByRef, Boolean ByRef, Boolean ByRef, Boolean, LinkManagerSettings, System.String, System.Web.UI.AttributeCollection, Boolean, System.String)'.]
   Dynamicweb.Controls.LinkManager.Render(HtmlTextWriter writer) +0
   System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +79
   System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +250
   Dynamicweb.Controls.GroupBox.Render(HtmlTextWriter writer) +271
   System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +79
   ASP.admin_module_usermanagement_edituser_aspx.__RenderEditUserDiv(HtmlTextWriter __w, Control parameterContainer) +1423
   System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +117
   System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer) +47
   System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +79
   System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +250
   System.Web.UI.HtmlControls.HtmlForm.RenderChildren(HtmlTextWriter writer) +11831937
   System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer) +47
   System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +79
   System.Web.UI.HtmlControls.HtmlForm.RenderControl(HtmlTextWriter writer) +50
   ASP.admin_module_usermanagement_edituser_aspx.__Render__control1(HtmlTextWriter __w, Control parameterContainer) +269
   System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +117
   System.Web.UI.Page.Render(HtmlTextWriter writer) +39
   System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +79
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +8753

Replies

 
Imar Spaanjaars Dynamicweb Employee
Imar Spaanjaars
Posted on 15/06/2020 21:15:31
Reply
This post has been marked as an answer

Hi Terri,

You probably still have newer ASPX files in /Admin that target 9.8.7 instead of 9.8.6. You get this error when code assumes some method exists on some class in some DLL but then at runtime realizes it's not there. So, the ASPX page thinks that the method LinkManager with the specified parameters exists in some DLL, but it doesn't. This can be because the ASPX is newer than the DLL and targets a method that doesn't exist yet, or it's because the DLL is newer and the method was removed.

Either way, you need to get your DLLs in sync with your aspx pages, so maybe overwriting everything in /Admin from a 9.8.6 copy will do the trick.

Cheers,

Imar

Votes for this answer: 1
 
Terri Donahue
Terri Donahue
Posted on 15/06/2020 21:29:56
Reply

Thanks Imar. We are using a virtual directory for admin so the files should be 9.8.6. I also copied all dlls from the dev bin to qa and error still happens. I'll keep digging and comparing the .aspx files. Thanks for the suggestions.

 
Terri Donahue
Terri Donahue
Posted on 15/06/2020 21:33:05
Reply

That was it Imar. Somehow the admin files were changed.

 

You must be logged in to post in the forum