Call Us! 1-800-383-5193
Call Us! 1-800-383-5193

Need Help?

Our experts will login to your server within 30 minutes to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price.

DNN SolPart error – Easy resolution

Are you stuck with DNN SolPart Error?  We can help you fix it!

DNN uses SolPartMenu settings to change the look and feel of the website menu systems.

However, DNN version 8 eliminated the SolPart concept, leading to DNN upgrade errors.

At Bobcares, we often get requests regarding DNN SolPart errors, as a part of our Server Management Services.

Today, let’s see how our Support Engineers fix this for our customers.


Cause of DNN SolPart Error

Before discussing the fix, let’s have a detailed look at the cause of the SolPart error.

Solpart is a Navigation Provider for altering the menu on the DNN website. It uses the web.config file.

As we already saw, the upgraded versions of DNN no longer support SolPart references. Therefore, when upgrading the version to DNN 8, these SolPart references often creates conflict.

Recently, one of our customers approached us with the following error. He was upgrading his site from DNN 7.3.2 to 8.0.0 but got the below error.

DNN SolPart error


How we fix SolPart Error?

It’s now time to see how our Support Engineers checked and fixed the error.

To avoid the SolPart error, we deleted all the references of SolPart from the upgraded version. We did it in 2 steps.

1. Find the references of SolPart in the DNN containers. And, SolPartActions types are generally referenced in DNN Containers. These DNN Containers helps to add style and markup to the modules independently.

Therefore, we accessed the Portals folder, and then we searched for SolPart reference using the below command.

cd Portal

findstr /s /i /m solpart *.ascx

This gave us the lists of files having SolPart references.

2. We removed the following two lines from the list of files where we found SolPart reference.

<%@ Register TagPrefix=”dnn” TagName=”ACTIONS” Src=”~/Admin/Containers/SolPartActions.ascx” %>

<dnn:ACTIONS runat=”server” id=”dnnACTIONS” />

Later, we checked if there were any custom codes that came along with custom modules. As we found a few more SolPart references in the custom modules, we removed them also.

Thus, we fixed the SolPart Error. And the DNN website started working correctly.


[Still having trouble in fixing the SolPart error?– We can fix it. ]



In short, DNN SolPart error can be fixed easily by removing the SolPart references from the upgraded version. In today’s article, we discussed how our Support Engineers do this and make DNN website working for our customers.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.



Submit a Comment

Your email address will not be published. Required fields are marked *