DotNetNuke Visualizer Instance 404 Error

Overview

A recurring error identified as System.Web.HttpException (0x80004005) with a status and code of 404 can occur in DotNetNuke due to a missing visualizer instance. This error, originating from DotNetNuke.Services.Exceptions.Exceptions, fills up the log and indicates a failure to find a visualizer instance with a specific ID. It is crucial to locate the page or component where this error is being thrown to resolve it.

AbsoluteURL:
DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke
ExceptionGUID:a22c209f-e2fe-403d-a557-6f46bdf8aa8f
AssemblyVersion:
PortalId:-1
UserId:-1
TabId:-1
RawUrl:
Referrer:
UserAgent:
ExceptionHash:chS8qAfkdt0pBtiZ+4kCTsI4lnI=
Message:Not Found - { "status": 404, "code": 404, "developerMessage": "Could not find visualizer instance 4eb64d46-30e1-4f62-8951-390fa69f2a01", "message": "error.404" }
StackTrace:
   at Evoq.StructuredContent.Visualizer.Components.Remote.VisualizerRemoteManager.CallRenderApi[T](Int32 portalId, String url)
   at Evoq.StructuredContent.Visualizer.Components.Remote.VisualizerRetryRemoteManager.<RenderDetailBatch>b__0()
   at Polly.Policy.<Execute>b__0()
   at Polly.Retry.RetryEngine.Implementation(Action action, IEnumerable`1 shouldRetryPredicates, Func`1 policyStateFactory)
   at Polly.Policy.Execute[TResult](Func`1 action, Context context)
   at Evoq.StructuredContent.Visualizer.Components.Remote.VisualizerRetryRemoteManager.RenderDetailBatch(String visualizerInstanceId, String language, Nullable`1 modifiedSince, String currentPageUrl, Int32 portalId)
   at Evoq.StructuredContent.Visualizer.Components.VisualizerManager.RenderDetailBatch(ModuleInfo moduleInfo, Int32 version, Settings settings, String language, Nullable`1 modifiedSince, String currentPageUrl)
   at Evoq.StructuredContent.Visualizer.Components.VisualizerSearchManager.IndexAllDetails(ModuleInfo moduleInfo, DateTime beginDateUtc, Int32 publishedVersion, Settings settings)
   at Evoq.StructuredContent.Visualizer.Components.VisualizerSearchManager.GetModifiedSearchDocuments(ModuleInfo moduleInfo, DateTime beginDateUtc)
InnerMessage:
InnerStackTrace:
Source:Evoq.StructuredContent.Visualizer
FileName:
FileLineNumber:0
FileColumnNumber:0
Method:

Solution

To resolve the recurring error related to a missing visualizer instance in DotNetNuke, follow these detailed steps:

1. Check Database for Visualizer Information:

   • Retrieve and examine the details of the visualizer instance.
   • Run the following SQL query to get the relevant information:
     SELECT * FROM StructuredContent_Visualizers WHERE ItemId = 'enter the visualizer instance ID';
   • Verify that the visualizer instance is still present in the system. The issue might be due to stale data if the visualizer is found.

2. Query TabModules for Module Information:

   • Use the ModuleId obtained from the visualizer data to query the TabModules table.
   • Run the following SQL query:
     SELECT * FROM TabModules WHERE ModuleId = (SELECT ModuleId FROM StructuredContent_Visualizers WHERE ItemId = 'enter the visualizer instance ID');
   • Identify the TabID associated with the visualizer module.

3. Determine the Page Using TabID:

   • Identify the page where the visualizer module is used by querying the Tabs table.
   • Run the following SQL query:
     SELECT * FROM Tabs WHERE TabID = (SELECT TabID FROM TabModules WHERE ModuleId = (SELECT ModuleId FROM StructuredContent_Visualizers WHERE ItemId = 'enter the visualizer instance ID'));
4. Locate the exact page loading the visualizer instance that is causing the error.

Additionally, review the Settings column in the StructuredContent_Visualizers_Versions table for any relevant configuration that might be causing the issue.

By following these steps, you should be able to pinpoint the exact page or component where the visualizer instance error is being thrown and take appropriate action to resolve it. If the issue persists, consider contacting DNN support for further assistance.