We have a DNN 8.00.04 site that has been running smoothly since last fall. The latest versions of the Security Analyzer is on there and the patch from last fall. The Security Analyzer says the Telerik issue is patched.
| CheckTelerikVulnerability : Check if Telerik component has vulnerability. |
|
Telerik Component already patched.
|
Unfortunately, any Admin or Host page (e.g. File Management, User or Role Management, etc.) that uses Telerik's grid now doesn't work and throws a critical error, "A critical error has occurred. Please check the Event Viewer for further details." This is just the module, not the page. If we add another module to the page it loads and works fine.
In the Event Viewer for the above error (on Admin / User Management), we see:
AbsoluteURL:/Default.aspx
DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke
AssemblyVersion:8.0.4
PortalId:0
UserId:2
TabId:52
RawUrl:/Admin/User-Accounts
Referrer:https://www.bigorganization.org/Admin/LogViewer
UserAgent:Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36
ExceptionHash:LVSQdr4WIDqH0qgm9hHdJA==
Message:Unable to cast object of type 'Telerik.Web.UI.GridTableRow' to type 'Telerik.Web.UI.GridItem'.
StackTrace:
InnerMessage:Unable to cast object of type 'Telerik.Web.UI.GridTableRow' to type 'Telerik.Web.UI.GridItem'.
InnerStackTrace:
at Telerik.Web.UI.GridTableRow.get_ClientID()
at CookieConsent.View.FindControlIterative(Control root, String id)
at CookieConsent.View.FillData()
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.Control.OnPreRender(EventArgs e)
at DotNetNuke.Framework.PageBase.OnPreRender(EventArgs e)
at DotNetNuke.Framework.DefaultPage.OnPreRender(EventArgs evt)
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Source:
FileName:
FileLineNumber:0
FileColumnNumber:0
Method:
Server Name: peach
Experience tells me this is likely one of those issues where a Binding Redirect in the web.config might be the solution, but I have not been able to narrow down the correct DLLs and versions. And I could be wrong about that guess.
We do not have a backup BECAUSE this happened more than 3 to 4 weeks ago and was not discovered until recently. We believe it may have been caused by a module install, however, the only record we have of a module install close to that timeframe was about 6 weeks ago... The GDPR Cookie Consent module by Seavus.
So... anyone know a fix or spot the problem above? Or have questions that could help lead to the right clues+solution? Thanks - Jeremy