After the upgrade from v5.4.x to v6.1.3 on a production site, I've started seeing numerous "Could not load type" errors. They're always one of two classes, and those classes are in house modules.
The confusion is, that the URL in question never has the module on it; there's never an error shown to the end user; and the modules listed as unable to load work fine on the pages they're in use on.
Any assistance tracking this down would be awesome!
AssemblyVersion: 6.1.3
PortalID: 0
PortalName: Contact Automation Portal
UserID: 243
UserName: mlibengood
ActiveTabID: 522
ActiveTabName: Lead Gen Transcriptions
RawURL: /Tools/LeadGenTranscriptions.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: https://portal.contactautomation.com/Tools/LeadGenTranscriptions.aspx
UserAgent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 4168d41f-4740-4a21-90af-a9b7a711ee97
InnerException: Could not load type 'ContactAutomation.Dnn.StandardOil'.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.Compilation.BuildManager.GetType
StackTrace:
Message: System.Web.HttpException: Could not load type 'ContactAutomation.Dnn.StandardOil'. at System.Web.Compilation.BuildManager.GetType(String typeName, Boolean throw , Boolean ignoreCase) at DotNetNuke.Framework.Reflection.CreateType(String TypeName, String CacheKey, Boolean UseCache, Boolean IgnoreErrors)
Source:
Server Name: w06