I've recently been getting the following error on several portals hosted at 3Essentials (never on any of the dedicated hosting portals I have).

Unhandled error loading module.
DotNetNuke.Services.Exceptions.ModuleLoadException: Unhandled Error Adding Module to ContentPane ---> System.Web.HttpCompileException: External component has thrown an exception. at System.Web.Compilation.BuildManager.PostProcessFoundBuildResult(BuildResult result, Boolean keyFromVPP, VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetBuildResultFromCacheInternal(String cacheKey, Boolean keyFromVPP, VirtualPath virtualPath, Int64 hashCode) at System.Web.Compilation.BuildManager.GetVPathBuildResultFromCacheInternal(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace ---

I can't help but wonder if it is the temporary ASP.NET files or something else (in the app pool) that is totally fussing with it.  The interesting thing is that eventually it "recovers" and works but then at a later date it randomly starts doing this again.

I'm at a complete loss as to the actual cause and solution to fix this bugger.

How unfortunate then... this is happening on sites I have hosted on a shared hosting provider not a dedicated hosting so I have no control over IIS or the file system (ASP.NET temporary files).  I've never had it happen on any of my dedicated sites so I wonder if it is more to do with the nature of shared hosting (ie., competing for resources on the system, etc).

Thanks for the info though -- it was along the lines I thought would likely be necessary to fix it, just have no power to do so on shared hosting.  By the time I'd submit a ticket and have them fix it, it would have already fixed itself through recycling the app pool and what not.