Troubleshooting: Missing Persona Bar

Platform    Evoq Content    Evoq Engage

Issue

The Persona Bar does not load nor display on a recent DNN installation.

Root Cause

This issue has two probable root causes:

Step-By-Step Guide

The website files are located on a Root Drive rather than inside a Folder

  1. Create a new folder within the drive. The directory for websites is usually located in the following path on your server:
    C:\inetpub\wwwroot\Your_Website_Folder
  2. Apply the correct IIS permissions to the new folder by following the steps in our Set Up the DNN Folder article.
  3. Move the DNN website files to the newly created folder.
  4. Change the website's physical path to point to this new folder on IIS by following the steps in our Set Up IIS article.
  5. Go to Control Panel > Administrative Tools > Internet Information Services (IIS) Manager.
  6. Click on Manage Server > Restart to restart IIS and reload your website.
    IIS Manager - Restart

The web.config file is missing the correct assembly binding

If the error message [ERROR] DotNet.Nuke.Common.Internal.ServicesRoutingManager - Unable to register service routes below is displayed after an upgrade; this means no API routing is getting registered. The solution is to add the correct assembly binding into the assemblyBinding section of the web.config file.

[ERROR] DotNetNuke.Common.Internal.ServicesRoutingManager - Unable to register service routes

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. --->
System.IO.FileLoadException: Could not load file or assembly 'Newtonsoft.Json, Version=6.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies.
The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
  1. Access the web.config file by following the steps in our article Access web.config article.
  2. Identify the assemblyIdentity node causing the problem or throwing an exception (in this example, the Newtonsoft.Json assembly):
    <dependentAssembly>
    <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" />
    <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="4.0.0.0" />
    </dependentAssembly>
  3. Replace the bindingRedirect tag with the correct routing information for the assemblyIdentity:
    <dependentAssembly>
    <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" />
    <bindingRedirect oldVersion="0.0.0.0-32767.32767.32767.32767" newVersion="7.0.0.0" />
    </dependentAssembly>
  4. Go to Control Panel > Administrative Tools > Internet Information Services (IIS) Manager.
  5. Click on Manager Server > Restart to restart IIS and reload your website.
    IIS Manager - Restart

Comments

0 comments

Please sign in to leave a comment.