Introduction

Today we will show you about Managing 'Couldn't load type "Dotnetnuke.common.global".There are a thousand reasons this feared message can show up, yet suppose it is possible that it shows up on a site that you are 100% certain no one has messed with in any capacity other than transferring documents for a long while.

The problem

The error itself is as follows:
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Could not load type 'DotNetNuke.Common.Global'.

Source Error:

Line 1:  <%@ Application Inherits="DotNetNuke.Common.Global" Language="VB" %>
Source File: /global.asax    Line: 1

The setting

That was precisely the case I confronted today when a customer called me and reported the lapse. The customer was totally certain that no progressions had been performed other than transferring a few records, both to the application and the server itself (no redesigns, no apppool changes, no iis design changes). Just to be protected, I checked the dates of the records in the container envelope and additionally the date of the global.asax record and all had not been changed amid the recent months.

Conceivable reasons

Seeking the Web, I was panicked to see that there were in any event a couple of dozen conceivable reasons for this lapse. Case in point, there's a multi-page string in the Dotnetnuke discussions dicussing this blunder. Unfortunately, the greater part of the cases respected moves up to the center stage, recompiling or other stuff that had been changed.

So what else could not be right? All things considered, I again found than when something appears incomprehensible, it doesn't generally must be some amazingly confounded specialized issue.

Solution

The customer had admittance to the full site root by means of a FTP client. After attempting to transfer stuff, the customer coincidentally moved the App_data organizer inside an alternate envelope. That was it! I moved the App_data organizer once more to the root and everything was fine once more.

What I realized from this occurrence: Always search for the least difficult conceivable reason for a blunder first. Trust it bails some of you out there.

Best Recommendation for DotNetNuke Hosting

ASPHostPortal.com is The Leader of Best DotNetNuke Hosting Provider. They provide DotNetNuke Hosting with Affordable Price, Fast & Stable Network, and Structured Recovery System. They start their hosting plan from $1/month. With that price, your data will be safe and always properly backed up. Moreover, they also provide uptime and 30 days money back guarantees for all hosting plan. They have 5 different data centers in the world that can give best support for your DotNetNuke site. With their complete features and cheap price, your DotNetNuke site will be turn into great performance.